Speed Insights
Grade F
58% performance
https://minutecryptic.today
LCP
3.7s
Largest paint
TBT
915ms
Blocking time
CLS
0.01
Layout shift
74
out of 100
86
out of 100
130/150 rule points
91
out of 100
66/72 rule points
66
out of 100
53/80 rule points
74
out of 100
82/110 rule points
Category point breakdown
- Material high-impact failures span 3 categories.
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. Non-robots access or indexing restrictions affect Claude-SearchBot, Claude-User, PerplexityBot, and 1 more. Claude-SearchBot: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. Claude-User: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. PerplexityBot: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. MistralAI-User: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. AEO crawler readiness is 77%: discovery 34/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
Priority
Priority 2: fix before sharing the page publicly.
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 4 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: content-security-policy. Needs strengthening: none.
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); 2 non-contrast rule(s) are scored here, including 2 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 3 result(s) require review. Top rules: avoid-inline-spacing (33), color-contrast (29), nested-interactive (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Cryptic
Fix Prompt
Write a clear page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 78 characters.
Priority
Priority 8: fix during launch polish.
Fix Prompt
Strengthen 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 80/100, answer-ready text 90/100, semantic structured data 83/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 1 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 1 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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 1 review and 1 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. Non-robots access or indexing restrictions affect Claude-SearchBot, Claude-User, PerplexityBot, and 1 more. Claude-SearchBot: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. Claude-User: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. PerplexityBot: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. MistralAI-User: Allowed by * allow: / on line 2. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: index, follow. AEO crawler readiness is 77%: discovery 34/45, index and snippet eligibility 25/25, synthetic reachability 13/20, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. 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
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 80/100, answer-ready text 90/100, semantic structured data 83/100. Detected role: home (high confidence). Failed: earned 34 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
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 78 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 8: fix during launch polish.
Fix Prompt
Schema quality and validity
Why this needs attention
The JSON-LD may parse, but its required facts, page-role relevance, visible-content agreement, or graph connections are incomplete.
Invalid structured data can be ignored by search and answer systems, even when visible page content is strong.
Recommended correction
Evidence
3 of 3 JSON-LD block(s) parsed. Semantic quality is 83/100: completeness 92/100, graph connectivity 0/100, primary types FAQPage, Organization, WebSite, currently useful search-feature types Organization, WebSite, and limited-eligibility types FAQPage. Nested types do not count as separate schema coverage. Failed: earned 7 of 8 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 10: 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 4 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: content-security-policy. Needs strengthening: none. Failed: earned 12 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
Visible heading levels found: 1, 3, 2, 3, 3, 3, 3, 3, 2, 3, 3, 3, 3, 2, 2, 2, 2, 3, 3, 3, 3, 2, 3, 3, 3, 3, 3, 3 (rendered page). 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
24 of 306 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.02. Mobile 390px viewport: 11 of 193 failed; worst ratio 2.02: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
Start with the beginner-friendly guide, then use the archive to practise spottin
About the site
Open
Open
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); 2 non-contrast rule(s) are scored here, including 2 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 3 result(s) require review. Top rules: avoid-inline-spacing (33), color-contrast (29), nested-interactive (1). Failed: earned 10 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.
Affected elements
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Inline text spacing must be adjustable with custom stylesheets
Fix all of the following: letter-spacing in the style attribute must not use !important, or be at 0.12em (current 0em) word-spacing in the style attribute must not use !important, or be at 0.16em (current 0em)
Cryptic
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 0 source or methodology signal(s) for this home page. 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 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: 3 unique above-fold action(s), 2 body sample(s) below 14px, 0 cramped line-height sample(s), and 1 overlong line sample(s). Mobile 390px: 2 unique above-fold action(s), 2 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 60px/400 weight versus a 14px/400 median body style (4.29× size). Captured 23 supporting heading(s) and 12 action(s). The main heading has a clear rendered emphasis over body copy. 24 of 306 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
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: 1393ms. Load complete: 4355ms. First contentful paint: 880ms. Largest contentful paint: 3656ms. Total blocking time: 915ms. Cumulative layout shift: 0.014. Resources: 70. Scripts: 20. Images: 10. Third-party origins: 22. Transfer: 3126KB. Potential render-blocking resources: 4. Metrics outside the good range: Largest contentful paint 3656ms (good at or below 2500ms); Total blocking time 915ms (good at or below 200ms; poor range); Transfer size 3126KB (good at or below 2200KB); Third-party origins 22 origins (good at or below 8 origins). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
Load contributors
Asset timings are observed request durations. They are not added together because browsers can load requests in parallel.
Largest contentful paint
1156ms over the rendered audit threshold.
Total blocking time
715ms over the rendered audit threshold.
Transfer size
926KB over the rendered audit threshold.
Third-party origins
14 origins over the rendered audit threshold.
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
Semantic schema score 83/100. Detected 3 JSON-LD block(s), 0 parse error(s), 8 graph node(s), and primary types FAQPage, Organization, WebSite. Completeness: 92/100. Graph connectivity: 0/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 80/100 for “Minute CrypticAnswer Today”. Title/H1 token overlap is 33%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 90/100 from 473 main-content words, 7 concise answer block(s), 3 question heading(s), 8 definition(s), 0 list(s), and 1 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 193 visible text element(s).
Synthetic search-agent reachability
6 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
No llms.txt file was found; this is optional and does not reduce core AEO readiness.
OpenAIChatGPT searchOAI-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
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: index, follow
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow; Googlebot meta: index, follow, max-video-preview:-1, max-image-preview:large, max-snippet:-1
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
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: index, follow
AppleSiri, Spotlight, and Safari searchApplebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 98% sampled-content parity
Controls: robots meta: index, follow
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: blocked · HTTP 403
Controls: robots meta: index, follow
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
MetaMeta AI user fetchesmeta-externalfetcherPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
Controls: robots meta: index, follow
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.
