Speed Insights
Grade A
97% performance
https://www.cafeato.com
LCP
1.5s
Largest paint
TBT
78ms
Blocking time
CLS
0.004
Layout shift
75
out of 100
97
out of 100
145/150 rule points
83
out of 100
60/72 rule points
32
out of 100
30/94 rule points
88
out of 100
97/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
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 Applebot for this page path. Applebot-Extended are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 94%: discovery 39/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/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 8 violation rule(s); 7 non-contrast rule(s) are scored here, including 4 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: image-alt (9), select-name (1), color-contrast (8), link-in-text-block (2), link-name (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Images must have alternative text
Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"
Select element must have an accessible name
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element's default semantics were not overridden with role="none" or role="presentation"
Fix Prompt
Add common public security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 2 of 5 common public security controls. Present: x-content-type-options, frame protection (x-frame-options). Missing: strict-transport-security, content-security-policy, referrer-policy. Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Label public form fields
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 0 of 2 eligible user-facing form control(s).
Priority
Priority 7: fix during launch polish.
Fix Prompt
Add meaningful image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 9 image(s) with no alt attribute and 0 image(s) with empty alt text that appear informative, out of 43. 0 empty-alt image(s) looked decorative and were not counted as failures.
Priority
Priority 11: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 0 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 0 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 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 Applebot for this page path. Applebot-Extended are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 94%: discovery 39/45, index and snippet eligibility 25/25, synthetic reachability 20/20, sitemap freshness 10/10. Failed: earned 13 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
Answer-engine content quality
Why this needs attention
The page is technically discoverable, but its entity clarity, answer-ready copy, structured data, evidence, authorship, or freshness is not yet complete.
Search and answer systems need clear, extractable, verifiable facts in addition to crawl access and metadata.
Recommended correction
Evidence
Role-aware AEO content components: entity clarity 78/100, answer-ready text 95/100, semantic structured data 100/100. Detected role: home (high confidence). Failed: earned 36 of 40 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
Fix Prompt
Common security headers
Why this needs attention
Several browser protection headers are missing or present only as weak, narrow policies.
These headers reduce avoidable browser-side risk and show a baseline of care before launch.
Recommended correction
Evidence
Detected 2 of 5 common public security controls. Present: x-content-type-options, frame protection (x-frame-options). Missing: strict-transport-security, content-security-policy, referrer-policy. Needs strengthening: none. 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
Image alt text
Why this needs attention
One or more images are missing alt text.
People using screen readers may miss product context, trust signals, or calls to action.
Recommended correction
Evidence
Detected 9 image(s) with no alt attribute and 0 image(s) with empty alt text that appear informative, out of 43. 0 empty-alt image(s) looked decorative and were not counted as failures. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 11: fix during launch polish.
Fix Prompt
Form labels
Why this needs attention
Some form controls do not have a detectable label or accessible name.
Unlabeled inputs make email capture, demo requests, and signups harder for assistive technology users.
Recommended correction
Evidence
Detected labels or accessible names for 0 of 2 eligible user-facing form control(s). Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: 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 visible main landmark(s) and 2 visible landmark element(s) or roles. A page should expose one main landmark. 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
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
15 of 234 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1.5. Mobile 390px viewport: 7 of 124 failed; worst ratio 1.5:1. 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
CHOOSE WHOLE BEANS
CHOOSE SPECIALTY CAPSULES
SUBSCRIBE NOW
SUBSCRIBE NOW
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); 7 non-contrast rule(s) are scored here, including 4 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: image-alt (9), select-name (1), color-contrast (8), link-in-text-block (2), link-name (1). 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
Images must have alternative text
Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"
Images must have alternative text
Fix any of the following: Element does not have an alt attribute 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 Element's default semantics were not overridden with role="none" or role="presentation"
Select element must have an accessible name
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> 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 Element's default semantics were not overridden with role="none" or role="presentation"
Fix Prompt
Credibility and proof
Why this needs attention
The page does not expose enough verifiable credibility for its detected role.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 commercial proof signal(s) and 1 source or methodology signal(s) for this home page. Failed: earned 5 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Rendered composition and spacing
Why this needs attention
Rendered geometry found cramped text, overly long lines, undersized body copy, or too many competing actions in the first viewport.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Desktop 1366px: 2 unique above-fold action(s), 3 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 2 unique above-fold action(s), 3 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Repeated CTA labels are deduplicated and do not earn extra credit. Failed: earned 2 of 7 points from partial coverage.
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
Rendered typography, geometry, and contrast show that the main heading is not distinct or legible enough, or that the hierarchy needs manual review.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
The rendered H1 is 51px/700 weight versus a 15.3px/400 median body style (3.33× size). Captured 24 supporting heading(s) and 11 action(s). The main heading has a clear rendered emphasis over body copy. 15 of 234 rendered text samples missed contrast targets, so hierarchy is not considered fully legible. Failed: earned 6 of 9 points from partial coverage.
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
The canonical resolves to the scanned public URL.
Sitemap coverage and freshness
The exact URL appears in the fetched sitemap with lastmod 2026-07-26.
Structured data
Semantic schema score 100/100. Detected 2 JSON-LD block(s), 0 parse error(s), 13 graph node(s), and primary types FAQPage, WebSite. Completeness: 100/100. Graph connectivity: 100/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content. Limited search eligibility: FAQPage.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 78/100 for “Running low on good coffee?”. Title/H1 token overlap is 25%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 95/100 from 669 main-content words, 7 concise answer block(s), 9 question heading(s), 5 definition(s), 2 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 114 visible text element(s).
Synthetic search-agent reachability
7 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://www.cafeato.com/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 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 4
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
OpenAIChatGPT user fetchesChatGPT-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: all
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 4
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 4
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
PerplexityPerplexity user fetchesPerplexity-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: not applicable to user-requested fetches
Synthetic probe: not tested · access is unverified
Controls: robots meta: all
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: blocked by applebot disallow: / · line 34
Synthetic probe: not tested · access is unverified
Controls: robots meta: all
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by applebot disallow: / · line 34
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 4
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 4
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 4
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: all
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 4
Synthetic probe: not applicable to this policy control
Controls: robots meta: all
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.
