Speed Insights
Grade A
98% performance
https://www.spendbuddy.co
From spendbuddy.co
LCP
1.5s
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
48
out of 100
38
out of 100
39/103 rule points
55
out of 100
42/76 rule points
55
out of 100
47/86 rule points
43
out of 100
47/110 rule points
Category point breakdown
Biggest score-losing checks
For your AI agent
Share this audit’s URL with ChatGPT, Claude, or your coding agent to turn findings into fixes. Your agent can open the saved evidence below when it needs more detail; these files never start a new scan.
Agent-readable files
Remove exposed sensitive files
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Fix Prompt
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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 78%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 13/20, sitemap freshness 0/10.
Priority
Priority 2: 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 controls. Present: none. Missing: strict-transport-security, content-security-policy, 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
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: color-contrast (1), heading-order (1), region (7).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
See how it works →
Heading levels should only increase by one
Fix any of the following: Heading order invalid
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 4 medium, 0 low. Coverage: 0 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 4 medium, 0 low. Coverage: 0 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
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. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 78%: discovery 45/45, index and snippet eligibility 20/25, synthetic reachability 13/20, sitemap freshness 0/10. Failed: earned 11 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
Meta description
Why this needs attention
The page does not expose a strong short summary for search and answer engines.
A missing description makes previews weaker when early users share or find the page.
Recommended correction
Evidence
No meta description was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: 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 0 H1 heading(s) and 0 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
Canonical tag
Why this needs attention
The page does not declare which public URL is the preferred version.
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Recommended correction
Evidence
No canonical link tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Sitemap 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
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: fix during launch polish.
Fix Prompt
Schema presence
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
Open Graph basics
Why this needs attention
The page is missing several social preview fields.
Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Recommended correction
Evidence
Detected 0 of 4 Open Graph basics. Failed: earned 0 of 5 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Internal link basics
Why this needs attention
The page has too few detectable links to other public pages on the same site.
Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Recommended correction
Evidence
Detected 0 internal link(s). Failed: earned 0 of 6 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: 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 controls. Present: none. Missing: strict-transport-security, content-security-policy, x-content-type-options, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. 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.
Fix Prompt
Sensitive file probes
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response. Failed: earned 0 of 16 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 1: 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: none. 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
Landmark presence
Why this needs attention
The page is missing common landmarks such as header, nav, main, or footer.
Landmarks make the page easier to navigate for assistive technology and keyboard users.
Recommended correction
Evidence
Detected 0 landmark element(s) or roles. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: 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: color-contrast (1), heading-order (1), region (7). 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
See how it works →
Heading levels should only increase by one
Fix any of the following: Heading order invalid
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: fix before sharing the page publicly.
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 0 H1 heading(s) and 0 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
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 1 visible word(s). General page range: 80-1800 words. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
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
Spacing consistency
Why this needs attention
The page exposes few consistent spacing signals in class or inline styles.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Detected 0 spacing class/style signal(s). Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 25: 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 0 hierarchy signal(s) from headings, CTA, and emphasized text. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
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
No canonical URL was detected.
Sitemap coverage and freshness
The exact scanned URL was not found in the fetched sitemap.
Structured data
Semantic schema score 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and types none. No primary schema type matched the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 20/100 for “SpendBuddy”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 0/100 from 0 main-content words, 0 concise answer block(s), 0 question heading(s), 0 definition(s), 0 list(s), and 0 table(s).
Authorship and accountability
Authorship is not a universal requirement for the detected home page role.
Published or updated date
Freshness metadata is contextual for the detected home page role.
Supporting-source links
Supporting sources are contextual for the detected home page role and do not affect readiness.
Rendered content availability
Rendered audit completed with 0 visible text element(s).
Synthetic search-agent reachability
6 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://www.spendbuddy.co/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
OpenAIOpenAI model trainingGPTBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by gptbot disallow: / · line 55
Synthetic probe: not applicable to this policy control
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AnthropicClaude model trainingClaudeBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by claudebot disallow: / · line 46
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by google-extended disallow: / · line 52
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
MetaMeta AI model and product datameta-externalagentOPTED OUT · Toggle crawler details
Model training
Robots: blocked by meta-externalagent disallow: / · line 58
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAmazon model trainingAmazonbotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by amazonbot disallow: / · line 34
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Common CrawlOpen web datasetsCCBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by ccbot disallow: / · line 43
Synthetic probe: not applicable to this policy control
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. 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.
