Speed Insights
Grade A
96% performance
https://www.capy.sc
From https://capy.sc
LCP
416ms
Largest paint
TBT
166ms
Blocking time
CLS
0.007
Layout shift
82
out of 100
93
out of 100
103/111 rule points
82
out of 100
62/76 rule points
69
out of 100
65/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Fix rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1), heading-order (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Copyright © 2026 by Incentv Technologies Inc. All r
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Fix Prompt
Use one clear H1 and ordered headings
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 4 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Fix heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 3, 3, 3.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Fix rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 0px. Small tap targets: 32.
Priority
Priority 13: fix during launch polish.
Affected elements
Interactive control
CLI
Keep
Docs
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 4 total headings. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 1 of 5 common public security controls. Present: strict-transport-security. Missing: content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 4 of 18 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Heading order
Why this needs attention
Heading levels appear to jump or start without a clear hierarchy.
A clean heading outline helps visitors scan the page and helps assistive technology navigate it.
Recommended correction
Evidence
Heading levels found: 1, 3, 3, 3. Failed: earned 0 of 11 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Fix Prompt
Rendered axe accessibility violations
Why this needs attention
The rendered page has accessibility rule violations detected by axe-core.
axe checks the actual browser-rendered page, so these issues can affect people using keyboards, screen readers, or other assistive technology.
Recommended correction
Evidence
axe found 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (1), heading-order (1). Failed: earned 0 of 18 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Copyright © 2026 by Incentv Technologies Inc. All r
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Fix Prompt
Trust signals
Why this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 trust-signal keyword occurrence(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Rendered layout ergonomics
Why this needs attention
The browser-rendered page has layout or tap-target issues.
Horizontal overflow and tiny tap targets make the page feel broken on real devices, especially for mobile visitors.
Recommended correction
Evidence
Horizontal overflow: 0px. Small tap targets: 32. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Affected elements
Interactive control
CLI
Keep
Docs
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
No general noindex directive was detected.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
The exact URL appears in the fetched sitemap with lastmod 2026-08-12T02:01:40.688Z.
Structured data
Detected 1 JSON-LD block(s), 0 parse error(s), and types Offer, Organization, SoftwareApplication, WebSite.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Detected 3 of 3 core identity signals across the title, description, and H1.
Answer-ready visible text
Detected 512 visible words and 13 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
No datePublished or dateModified value was detected in structured data.
Supporting-source links
Detected 11 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 10 visible text element(s).
Synthetic search-agent reachability
8 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://www.capy.sc/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GPTBotModel training
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ClaudeBotModel training
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
Claude-SearchBotAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow; Googlebot meta: index, follow, max-image-preview:large, max-snippet:-1
Google-ExtendedData-use policy control
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
BingbotSearch and discovery
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
PerplexityBotAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow
ApplebotSearch and discovery
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Applebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
meta-externalagentModel training
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AmazonbotModel training
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
CCBotModel training
Robots: allowed by * allow: / · line 5
Probe: not tested for this control
Controls: robots meta: index, follow
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.
The image refreshes from FreeScan after a completed rescan. Clicking it always opens the newest public report saved for this exact scanned URL.
Scan evidence is included as untrusted data. The implementation brief instructs agents to verify findings before editing and to avoid destructive or speculative changes.
