Speed Insights
Grade N/A
Not captured
https://andrewthake.com
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
63
out of 100
82
out of 100
94/114 rule points
76
out of 100
58/76 rule points
20
out of 100
19/94 rule points
74
out of 100
81/110 rule points
Category point breakdown
Biggest score-losing checks
Add common public security headers
-18 rule ptsWhy 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 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Fix rendered axe accessibility violations
-18 rule ptsWhy 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 1 serious or critical rule(s). Top rules: color-contrast (25), heading-order (4), region (7).
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Label public form fields
-14 rule ptsWhy this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 4 of 20 form control(s).
Priority
Priority 7: fix during launch polish.
Agent Prompt
Publish a valid sitemap.xml
-12 rule ptsWhy this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
Agent Prompt
Add meaningful image alt text
-14 rule ptsWhy this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 20 image(s) missing alt text out of 38.
Priority
Priority 11: fix during launch polish.
Agent 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.
Heading structure
0/8Why 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 67 total headings. Failed: earned 0 of 8 points.
Priority
Priority 9: fix during launch polish.
Agent Prompt
sitemap.xml validity
0/12Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root. Failed: earned 0 of 12 points.
Priority
Priority 7: fix during launch polish.
Agent Prompt
Common security headers
0/18Why 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 0 of 5 common public security headers. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, x-frame-options, referrer-policy. Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Image alt text
0/14Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 20 image(s) missing alt text out of 38. Failed: earned 0 of 14 points.
Priority
Priority 11: fix during launch polish.
Agent Prompt
Form labels
0/14Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 4 of 20 form control(s). Failed: earned 0 of 14 points.
Priority
Priority 7: fix during launch polish.
Agent Prompt
Heading order
0/11Why 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: 2, 2, 2, 2, 3, 1, 2, 2, 2, 5, 5, 5, 5, 5, 5, 5, 5, 2, 5, 5, 5, 5, 5, 5, 5, 5, 5, 5, 2, 2, 2, 2, 2, 2, 2, 5, 5, 5, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 2, 4, 4, 4, 4, 4, 4, 4, 4, 2, 4, 4, 4. Failed: earned 0 of 11 points.
Priority
Priority 13: fix during launch polish.
Agent Prompt
Semantic buttons and links
0/10Why this needs attention
Interactive controls are not consistently represented as semantic buttons or links.
Non-semantic controls can be hard to use with keyboards and screen readers.
Recommended correction
Evidence
Detected 7 semantic control(s) out of 9. Failed: earned 0 of 10 points.
Priority
Priority 17: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Basic contrast
0/8Why 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
31 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1. Failed: earned 0 of 8 points.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Rendered axe accessibility violations
0/18Why 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 1 serious or critical rule(s). Top rules: color-contrast (25), heading-order (4), region (7). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Text density
0/10Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 2913 visible word(s). Failed: earned 0 of 10 points.
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Rendered speed signals
0/10Why 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: 1098ms. Load complete: 1447ms. First contentful paint: 624ms. Resources: 82. Scripts: 65. Images: 1. Third-party origins: 5. Transfer: not available. Failed: earned 0 of 10 points.
Priority
Priority 14: fix during launch polish.
Agent Prompt
Rendered layout ergonomics
0/9Why 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: 63. Failed: earned 0 of 9 points.
Priority
Priority 13: fix during launch polish.
Agent Prompt
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.
