Speed Insights
Grade A
98% performance
https://alprad.com
From Alprad.com
LCP
1.2s
Largest paint
TBT
0ms
Blocking time
CLS
0.01
Layout shift
42
out of 100
66
out of 100
100/150 rule points
75
out of 100
54/72 rule points
56
out of 100
45/80 rule points
88
out of 100
97/110 rule points
Category point breakdown
- Search discovery is materially blocked.
- 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 OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more. OAI-SearchBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Claude-SearchBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Claude-User: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Googlebot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Bingbot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. PerplexityBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Applebot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. MistralAI-Index: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. MistralAI-User: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. meta-externalfetcher: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Amzn-SearchBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Amzn-User: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. AEO crawler readiness is 35%: discovery 0/45, index and snippet eligibility 25/25, synthetic reachability 0/20, sitemap freshness 10/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 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. 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 40/100, answer-ready text 25/100, semantic structured data 40/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
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); 3 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: heading-order (1), landmark-one-main (1), region (10).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
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
Add relevant structured data
Why this needs attention
The page is missing a primary JSON-LD entity that matches its actual role, or its named entity is not supported by visible content.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 1 JSON-LD block(s). Primary types: BikeStore. No primary type matches the page role. The named entity was not clearly supported by visible page content.
Priority
Priority 12: 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 OAI-SearchBot, Claude-SearchBot, Claude-User, and 9 more. OAI-SearchBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Claude-SearchBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Claude-User: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Googlebot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Bingbot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. PerplexityBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Applebot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. MistralAI-Index: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. MistralAI-User: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. meta-externalfetcher: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Amzn-SearchBot: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. Amzn-User: Allowed by * allow: / on line 3. Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge. AEO crawler readiness is 35%: discovery 0/45, index and snippet eligibility 25/25, synthetic reachability 0/20, sitemap freshness 10/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 5 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 40/100, answer-ready text 25/100, semantic structured data 40/100. Detected role: home (high confidence). Failed: earned 14 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
Relevant schema coverage
Why this needs attention
The page is missing a primary JSON-LD entity that matches its actual role, or its named entity is not supported by visible content.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 1 JSON-LD block(s). Primary types: BikeStore. No primary type matches the page role. The named entity was not clearly supported by visible page content. Failed: earned 3 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: 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
1 of 1 JSON-LD block(s) parsed. Semantic quality is 40/100: completeness 100/100, graph connectivity 0/100, primary types BikeStore, currently useful search-feature types none. Nested types do not count as separate schema coverage. Failed: earned 5 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
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
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 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. Needs strengthening: none. 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
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, 5, 5, 5, 5 (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
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
2 of 98 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1. Mobile 390px viewport: 1 of 30 failed; worst ratio 4.29: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
Verkstad▾ Hela verkstadenService, fit och eftermarknad Service & underhållGenomg
Costruita a mano, su misura per te.
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); 3 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 2 result(s) require review. Top rules: heading-order (1), landmark-one-main (1), region (10). 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.
Affected elements
Heading levels should only increase by one
Fix any of the following: Heading order invalid
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
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
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 79.2px/700 weight versus a 17px/400 median body style (4.66× size). Captured 0 supporting heading(s) and 3 action(s). The main heading has a clear rendered emphasis over body copy. 2 of 98 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-09-11.
Structured data
Semantic schema score 40/100. Detected 1 JSON-LD block(s), 0 parse error(s), 8 graph node(s), and primary types BikeStore. Completeness: 100/100. Graph connectivity: 0/100. No primary schema type matched the detected page role. The primary schema entity was not clearly supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 40/100 for “Samma händer.Hela vägen.”. Title/H1 token overlap is 0%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 25/100 from 444 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 53 visible text element(s).
Synthetic search-agent reachability
0 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 by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 3
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 trainingClaudeBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 3
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
GoogleGoogle Search and AI featuresGooglebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 3
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
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 searchApplebotFAIL · BLOCKED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 3
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 3
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 3
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
AmazonAlexa user fetchesAmzn-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 3
Synthetic probe: challenged · HTTP 403 · 12% sampled-content parity
Synthetic User-Agent probe encountered an HTTP 403 bot or security challenge.
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 3
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.
