Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://lighthouse.build
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
86
out of 100
91
out of 100
104/114 rule points
96
out of 100
73/76 rule points
72
out of 100
68/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
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 3 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (1), nested-interactive (1), region (1).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Add a useful meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 256 characters.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
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 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Priority
Priority 5: fix before sharing the page publicly.
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: 26.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Improve rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 447ms. Load complete: 795ms. First contentful paint: 1104ms. Resources: 33. Scripts: 14. Images: 1. Third-party origins: 9. Transfer: not available.
Priority
Priority 14: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 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, 2 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.
Meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
Meta description is 256 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
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 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options. Failed: earned 15 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
Basic contrast
Why this needs attention
The scanner found text/background color pairs that may be hard to read, or could not verify contrast.
Low contrast makes a launch page feel less polished and can exclude users with low vision.
Recommended correction
Evidence
10 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.02. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
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 3 violation rule(s), including 2 serious or critical rule(s). Top rules: color-contrast (1), nested-interactive (1), region (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.
Fix Prompt
Rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 447ms. Load complete: 795ms. First contentful paint: 1104ms. Resources: 33. Scripts: 14. Images: 1. Third-party origins: 9. Transfer: not available. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
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: 26. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Fix Prompt
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed
Probe: not tested for this control
OpenAIOpenAI modelsGPTBotModel training
Robots: allowed
Probe: not tested for this control
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: allowed
Probe: not tested for this control
AnthropicClaude modelsClaudeBotModel training
Robots: allowed
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: not tested for this control
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: not tested for this control
GoogleGeminiGoogle-ExtendedModel training
Robots: allowed
Probe: not tested for this control
MicrosoftCopilot and BingBingbotSearch and discovery
Robots: allowed
Probe: not tested for this control
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
Probe: not tested for this control
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: allowed
Probe: not tested for this control
AppleApple IntelligenceApplebot-ExtendedModel training
Robots: allowed
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: not tested for this control
Mistral AILe Chat user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: not tested for this control
MetaMeta AImeta-externalagentModel training
Robots: allowed
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: not tested for this control
AmazonAmazon AI modelsAmazonbotModel training
Robots: allowed
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: not tested for this control
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: not tested for this control
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
Probe: not tested for this control
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.
