Speed Insights
Grade A
98% performance
https://randomcountrygenerator.net
LCP
1.4s
Largest paint
TBT
0ms
Blocking time
CLS
0.000
Layout shift
85
out of 100
94
out of 100
141/150 rule points
84
out of 100
61/72 rule points
90
out of 100
86/94 rule points
80
out of 100
88/110 rule points
Category point breakdown
- Material high-impact failures span 2 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 OAI-SearchBot, Claude-SearchBot, Claude-User, and 4 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. Claude-User: No matching robots.txt rule blocks Claude-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. MistralAI-User: No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. meta-externalfetcher: No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. AEO crawler readiness is 54%: discovery 23/45, index and snippet eligibility 25/25, synthetic reachability 2/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 2 of 5 common public security controls. Present: strict-transport-security, x-content-type-options. Missing: content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
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 100/100, answer-ready text 85/100, semantic structured data 95/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Fix 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
Desktop horizontal overflow: 939px. Mobile horizontal overflow at 390px: 7px. WCAG 2.2 AA target-size failures: 0. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies.
Priority
Priority 13: fix during launch polish.
Affected elements
Search

Search

Fix Prompt
Add role-appropriate credibility
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.
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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: 2 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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 2 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. Non-robots access or indexing restrictions affect OAI-SearchBot, Claude-SearchBot, Claude-User, and 4 more. OAI-SearchBot: No matching robots.txt rule blocks OAI-SearchBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. Claude-SearchBot: No matching robots.txt rule blocks Claude-SearchBot from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. Claude-User: No matching robots.txt rule blocks Claude-User from /. Synthetic User-Agent probe returned HTTP 403. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. PerplexityBot: No matching robots.txt rule blocks PerplexityBot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. Applebot: No matching robots.txt rule blocks Applebot from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. MistralAI-User: No matching robots.txt rule blocks MistralAI-User from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. meta-externalfetcher: No matching robots.txt rule blocks meta-externalfetcher from /. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Relevant page controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large. AEO crawler readiness is 54%: discovery 23/45, index and snippet eligibility 25/25, synthetic reachability 2/20, sitemap freshness 5/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 8 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 100/100, answer-ready text 85/100, semantic structured data 95/100. Detected role: home (high confidence). Failed: earned 37 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: strict-transport-security, x-content-type-options. Missing: content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors), referrer-policy. Needs strengthening: none. Failed: earned 7 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
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
3 of 135 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1.36. Mobile 390px viewport: 0 of 57 failed. 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
Blog

About

Contact
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
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 28px/700 weight versus a 17px/400 median body style (1.65× size). Captured 5 supporting heading(s) and 4 action(s). The main heading has a clear rendered emphasis over body copy. 3 of 135 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 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
Desktop horizontal overflow: 939px. Mobile horizontal overflow at 390px: 7px. WCAG 2.2 AA target-size failures: 0. Targets smaller than 24×24px pass only when the required spacing or another WCAG exception applies. 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
Search

Search

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 95/100. Detected 1 JSON-LD block(s), 0 parse error(s), 8 graph node(s), and primary types ImageObject, Organization, WebPage, WebSite. Completeness: 75/100. Graph connectivity: 100/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content. Retired search feature: SearchAction; no coverage credit is awarded.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 100/100 for “Random Country Generator”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 85/100 from 445 main-content words, 2 concise answer block(s), 2 question heading(s), 5 definition(s), 1 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 54 visible text element(s).
Synthetic search-agent reachability
1 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-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
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: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AnthropicClaude model trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: blocked · HTTP 403
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
MicrosoftBing and CopilotBingbotUNKNOWN · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
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: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AppleSiri, Spotlight, and Safari searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Mistral AIMistral searchMistralAI-IndexUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: challenged · HTTP 403 · 2% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AmazonAlexa and Rufus searchAmzn-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
AmazonAlexa user fetchesAmzn-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: unknown
Synthetic User-Agent probe timed out.
Controls: robots meta: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy 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. 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.
