Evidence: landing page returned HTTP 403. Cloudflare header(s): cf-ray, server, cf-mitigated, content-security-policy. URL: https://starbattle.online
Review Cloudflare WAF, bot protection, rate-limit, and challenge rules for public marketing/content routes. Allow safe public scans and legitimate search or AI user-fetch crawlers to reach public pages while keeping admin, authenticated, preview, and private paths protected.
Speed Insights
Grade N/A
Not captured
https://starbattle.online
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
38
out of 100
36
out of 100
17/47 rule points
65
out of 100
34/52 rule points
0
out of 100
0/18 rule points
50
out of 100
19/38 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
page fetch returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. 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 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (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 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.
Fix Prompt
Add responsive viewport metadata
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Publish a valid sitemap.xml
Why 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
HTTP 403 returned for sitemap_xml.
Priority
Priority 7: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 1 low.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 low.
SEO / AEO
Severity mix: 1 critical, 2 high, 1 medium, 1 low.
Accessibility
Severity mix: 0 critical, 1 high, 0 medium, 0 low.
Security
Severity mix: 2 critical, 1 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 1 high, 2 medium, 1 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
page fetch returned HTTP 403 with Cloudflare signals, which can indicate crawler or bot-security blocking. 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
sitemap.xml validity
Why 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
HTTP 403 returned for sitemap_xml. Failed: earned 0 of 12 points.
Priority
Priority 7: 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 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.
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 1 violation rule(s), including 1 serious or critical rule(s). Top rules: meta-refresh (1). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Responsive viewport basics
Why this needs attention
The page is missing the viewport meta tag used for mobile layout.
Launch traffic often comes from phones; missing viewport metadata can make the page render poorly.
Recommended correction
Evidence
No viewport meta tag was detected. Failed: earned 0 of 12 points.
Priority
Priority 3: fix before sharing the page publicly.
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
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.
