Speed Insights
Grade A
98% performance
https://limitedcompany.accountants
LCP
1.7s
Largest paint
TBT
0ms
Blocking time
CLS
0.001
Layout shift
83
out of 100
94
out of 100
141/150 rule points
88
out of 100
67/76 rule points
85
out of 100
80/94 rule points
75
out of 100
83/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
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 3 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, referrer-policy. Missing: content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). 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 2 violation rule(s); 2 non-contrast rule(s) are scored here, including 1 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: target-size (3), region (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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 55/100, answer-ready text 100/100, semantic structured data 86/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Improve 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
2 of 2 JSON-LD block(s) parsed. Semantic quality is 86/100: completeness 95/100, graph connectivity 15/100, primary types AccountingService, FAQPage, Organization, WebPage, WebSite, currently useful search-feature types Organization, WebSite, and limited-eligibility types FAQPage. Nested types do not count as separate schema coverage.
Priority
Priority 10: 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: 0px. Mobile horizontal overflow at 390px: 0px. WCAG 2.2 AA target-size failures: 3. 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
Directions
Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
Directions
Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
Directions
Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
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 0 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: 3 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 0 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 3 review and 0 not applicable.
Failed checks
These checks need attention.
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 55/100, answer-ready text 100/100, semantic structured data 86/100. Detected role: home (high confidence). Failed: earned 32 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
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
2 of 2 JSON-LD block(s) parsed. Semantic quality is 86/100: completeness 95/100, graph connectivity 15/100, primary types AccountingService, FAQPage, Organization, WebPage, 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 3 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, referrer-policy. Missing: content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none. Failed: earned 9 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
4 of 434 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 3.06. Mobile 390px viewport: 4 of 326 failed; worst ratio 3.06: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
Indicative, based on your answers. Send it over and we confirm a fixed monthly f
Certified advisor
Certified ProAdvisor
Supported software
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 2 violation rule(s); 2 non-contrast rule(s) are scored here, including 1 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: target-size (3), region (1). 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
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
All touch targets must be 24px large, or leave sufficient space
Fix any of the following: Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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: 10 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: 4 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. More than three distinct actions compete in a captured first viewport. 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
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: 1731ms. Load complete: 2414ms. First contentful paint: 1692ms. Largest contentful paint: 1692ms. Total blocking time: 0ms. Cumulative layout shift: 0.001. Resources: 89. Scripts: 70. Images: 5. Third-party origins: 1. Transfer: 1310KB. Potential render-blocking resources: 1. Metrics outside the good range: Script requests 70 scripts (good at or below 20 scripts). Failed: earned 8 of 10 points from partial coverage.
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.
Script requests
50 scripts over the rendered audit threshold.
styles-qJv8p3_m.css
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: 0px. Mobile horizontal overflow at 390px: 0px. WCAG 2.2 AA target-size failures: 3. 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
Directions
Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
Directions
Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
Directions
Target has insufficient size (58.9px by 18.7px, should be at least 24px by 24px) Target has insufficient space to its closest neighbors. Safe clickable space has a diameter of 19.6px instead of at least 24px.
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 86/100. Detected 2 JSON-LD block(s), 0 parse error(s), 23 graph node(s), and primary types AccountingService, FAQPage, Organization, WebPage, WebSite. Completeness: 95/100. Graph connectivity: 15/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 55/100 for “Clear numbers.Better decisions.”. Title/H1 token overlap is 0%; description match not detected; identity schema detected.
Answer-ready visible text
Answerability scored 100/100 from 815 main-content words, 8 concise answer block(s), 7 question heading(s), 10 definition(s), 6 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 434 visible text element(s).
Synthetic search-agent reachability
8 of 8 completed search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://limitedcompany.accountants/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 oai-searchbot allow: / · line 20
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by gptbot allow: / · line 17
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 claudebot allow: / · line 26
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 62
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by claude-user allow: / · line 29
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by googlebot allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by google-extended allow: / · line 35
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by bingbot allow: / · line 5
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by perplexitybot allow: / · line 32
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
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 applebot allow: / · line 38
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by applebot-extended allow: / · line 47
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 62
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 62
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by meta-externalagent allow: / · line 50
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 62
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by amazonbot allow: / · line 53
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 62
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 62
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by ccbot allow: / · line 59
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.
To refresh your Pro site score and fixes, open your Pro dashboard and run a site audit.
