Speed Insights
Grade N/A
Not captured
https://m3u8-player.net
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
78
out of 100
89
out of 100
102/114 rule points
87
out of 100
66/76 rule points
61
out of 100
57/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 8 violation rule(s), including 4 serious or critical rule(s). Top rules: button-name (1), color-contrast (21), link-name (1), nested-interactive (1), heading-order (1).
Priority
Priority 5: 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 3 of 5 common public security headers. Present: x-content-type-options, x-frame-options, referrer-policy. Missing: strict-transport-security, content-security-policy.
Priority
Priority 5: fix before sharing the page publicly.
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, 2, 2, 3, 3, 2, 2, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 2, 2, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3.
Priority
Priority 13: fix during launch polish.
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 44 total headings.
Priority
Priority 9: 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: 72.
Priority
Priority 13: 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.
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 44 total headings. Failed: earned 0 of 8 points.
Priority
Priority 9: fix during launch polish.
Fix Prompt
LLM-readable file
Why this needs attention
The scan did not find llms.txt or .well-known/llms.txt.
A short LLM-readable file can help answer engines and AI tools summarize your product accurately.
Recommended correction
Evidence
HTTP 404 returned for llms_txt. Failed: earned 0 of 4 points.
Priority
Priority 24: lower-risk cleanup after urgent launch blockers.
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 3 of 5 common public security headers. Present: x-content-type-options, x-frame-options, referrer-policy. Missing: strict-transport-security, content-security-policy. Failed: earned 8 of 18 points from partial coverage.
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, 2, 2, 3, 3, 2, 2, 3, 3, 3, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 2, 2, 2, 3, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3, 3, 3, 3. Failed: earned 0 of 11 points.
Priority
Priority 13: fix during launch polish.
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
8 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.14. 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 8 violation rule(s), including 4 serious or critical rule(s). Top rules: button-name (1), color-contrast (21), link-name (1), nested-interactive (1), heading-order (1). Failed: earned 0 of 18 points.
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: 741ms. Load complete: 1407ms. First contentful paint: 408ms. Resources: 66. Scripts: 42. Images: 9. Third-party origins: 11. Transfer: not available. Failed: earned 0 of 10 points.
Priority
Priority 14: fix during launch polish.
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: 72. 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.
