Speed Insights
Grade N/A
Not captured
https://www.t30journal.com
From T30Journal.com
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
65
out of 100
81
out of 100
92/114 rule points
74
out of 100
56/76 rule points
50
out of 100
47/94 rule points
53
out of 100
58/110 rule points
Category point breakdown
Biggest score-losing checks
Unblock public crawlers
Why this needs attention
The public page appears blocked for FreeScan.app or for important search and AI crawler user agents.
If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path.
Priority
Priority 2: 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 (8), heading-order (1).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Remove insecure page resources
Why this needs attention
The page references insecure HTTP assets or links from an HTTPS page.
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Recommended correction
Evidence
Detected 1 insecure asset or link reference(s).
Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Make the primary CTA obvious
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Detected 0 CTA candidate(s).
Priority
Priority 4: 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: strict-transport-security, x-content-type-options, x-frame-options. Missing: content-security-policy, referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
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.
Crawler access
Why this needs attention
The public page appears blocked for FreeScan.app or for important search and AI crawler user agents.
If crawlers cannot access the page, search engines and answer engines may not discover, index, or summarize the launch page correctly.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Googlebot, Bingbot, DuckDuckBot, and 9 more for this page path. Failed: earned 0 of 14 points.
Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
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.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Mixed content indicators
Why this needs attention
The page references insecure HTTP assets or links from an HTTPS page.
Mixed content can cause browser warnings, broken assets, and lower visitor trust.
Recommended correction
Evidence
Detected 1 insecure asset or link reference(s). Failed: earned 0 of 12 points.
Priority
Priority 4: 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 3 of 5 common public security headers. Present: strict-transport-security, x-content-type-options, x-frame-options. Missing: content-security-policy, referrer-policy. Failed: earned 10 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, 2, 2, 4. Failed: earned 0 of 11 points.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Semantic buttons and links
Why 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 2 semantic control(s) out of 4. Failed: earned 0 of 10 points.
Priority
Priority 17: lower-risk cleanup after urgent launch blockers.
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
18 of 41 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.19. 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 2 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (8), heading-order (1). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Visible primary CTA
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
Detected 0 CTA candidate(s). Failed: earned 0 of 14 points.
Priority
Priority 4: fix before sharing the page publicly.
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.
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Visual hierarchy
Why this needs attention
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
Detected 2 hierarchy signal(s) from headings, CTA, and emphasized text. Failed: earned 0 of 9 points.
Priority
Priority 12: fix during launch polish.
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: 1281ms. Load complete: 1573ms. First contentful paint: 464ms. Resources: 67. Scripts: 45. Images: 3. Third-party origins: 7. Transfer: not available. Failed: earned 0 of 10 points.
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: 8. 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.
