Speed Insights
Grade N/A
Not captured
https://seedaud.io
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
87
out of 100
100
out of 100
114/114 rule points
100
out of 100
76/76 rule points
72
out of 100
68/94 rule points
76
out of 100
84/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 1 serious or critical rule(s). Top rules: aria-prohibited-attr (2), landmark-unique (1), image-redundant-alt (11).
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: 52.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Improve detectable color 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
1 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Balance landing page copy
Why 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 2327 visible word(s).
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Fix runtime browser errors
Why this needs attention
The rendered page produced console or uncaught JavaScript errors.
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Recommended correction
Evidence
Detected 1 console error(s) and 0 uncaught page error(s) during render.
Priority
Priority 15: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 2 low.
No failed checks in this category.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
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.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
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
1 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.
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 1 serious or critical rule(s). Top rules: aria-prohibited-attr (2), landmark-unique (1), image-redundant-alt (11). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Text density
Why 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 2327 visible word(s). Failed: earned 0 of 10 points.
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Runtime console health
Why this needs attention
The rendered page produced console or uncaught JavaScript errors.
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Recommended correction
Evidence
Detected 1 console error(s) and 0 uncaught page error(s) during render. Failed: earned 0 of 7 points.
Priority
Priority 15: 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: 52. Failed: earned 0 of 9 points.
Priority
Priority 13: fix during launch polish.
Fix 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.
