Speed Insights
Grade A
98% performance
https://cashneversleeps.com
LCP
1.1s
Largest paint
TBT
51ms
Blocking time
CLS
0.002
Layout shift
75
out of 100
91
out of 100
101/111 rule points
84
out of 100
64/76 rule points
61
out of 100
57/94 rule points
62
out of 100
68/110 rule points
Category point breakdown
Biggest score-losing checks
Improve AI search and crawler readiness
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Claude-SearchBot, PerplexityBot from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User from user-requested fetches. AEO crawler readiness is 88%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 5/10.
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 5 violation rule(s), including 1 serious or critical rule(s). Top rules: link-name (3), heading-order (1), landmark-one-main (1), landmark-unique (1), region (25).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Heading levels should only increase by one
Fix any of the following: Heading order invalid
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 1 of 5 common public security controls. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Clarify the hero promise
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 5 H1 heading(s) and 142 meta-description characters.
Priority
Priority 6: 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 5 H1 heading(s) and 19 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 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, 1 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
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. robots.txt blocks Claude-SearchBot, PerplexityBot from AI search or discovery for this page path. Synthetic or robots checks block Claude-User, MistralAI-User from user-requested fetches. AEO crawler readiness is 88%: discovery 45/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 5/10. Failed: earned 12 of 14 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)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 5 H1 heading(s) and 19 total headings. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
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 1 of 5 common public security controls. Present: content-security-policy. Missing: strict-transport-security, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Failed: earned 6 of 18 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)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, 1, 1, 1, 2, 3, 2, 3, 3, 3, 2, 3, 3, 2, 4, 1, 4, 4. Failed: earned 0 of 11 points.
How FreeScan evaluates this check (opens in a new tab)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
1 of 19 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.82. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
🏆
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 5 violation rule(s), including 1 serious or critical rule(s). Top rules: link-name (3), heading-order (1), landmark-one-main (1), landmark-unique (1), region (25). Failed: earned 0 of 18 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Fix Prompt
Hero clarity signals
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 5 H1 heading(s) and 142 meta-description characters. Failed: earned 0 of 13 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
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.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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: 737ms. Load complete: 979ms. First contentful paint: 840ms. Resources: 33. Scripts: 5. Images: 15. Third-party origins: 11. Transfer: not available. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)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: 16. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: fix during launch polish.
Affected elements
Login/Create Account
Home
Playbooks
Tools
Fix Prompt
Page-level AEO readiness
Shared eligibility and content signals that affect every search and answer agent.
Index and citation eligibility
No general noindex directive was detected.
Snippet and answer controls
No general nosnippet or max-snippet:0 control was detected.
Canonical alignment
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Detected 1 JSON-LD block(s), 0 parse error(s), and types ContactPoint, ImageObject, Organization, SearchAction, WebPage, WebSite.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Detected 3 of 3 core identity signals across the title, description, and H1.
Answer-ready visible text
Detected 717 visible words and 18 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
Structured data reports dateModified 2026-07-30T19:46:33+00:00.
Supporting-source links
Detected 11 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 19 visible text element(s).
Synthetic search-agent reachability
6 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://cashneversleeps.com/llms.txt returned HTTP 301; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
GPTBotModel training
Robots: allowed by gptbot allow: / · line 7
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
ClaudeBotModel training
Robots: allowed by claudebot allow: / · line 13
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Claude-SearchBotAI search
Robots: allowed
Probe: blocked · HTTP 403
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Claude-UserUser-requested fetch
Robots: allowed
Probe: blocked · HTTP 403
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
GooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Google-ExtendedData-use policy control
Robots: allowed by google-extended allow: / · line 19
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
BingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
PerplexityBotAI search
Robots: allowed by perplexitybot allow: / · line 16
Probe: blocked · HTTP 403
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
ApplebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Applebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
MistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
MistralAI-UserUser-requested fetch
Robots: allowed
Probe: blocked · HTTP 403
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
meta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
meta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Amzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Amzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
CCBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple preference states are training or data-use choices and do not lower the AEO score.
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.
