Speed Insights
Grade A
92% performance
https://bugshield.co.uk
LCP
640ms
Largest paint
TBT
305ms
Blocking time
CLS
0.000
Layout shift
81
out of 100
100
out of 100
111/111 rule points
76
out of 100
58/76 rule points
66
out of 100
62/94 rule points
83
out of 100
91/110 rule points
Category point breakdown
Biggest score-losing checks
Add common public security headers
Why this needs attention
Several basic browser protection headers were not visible.
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.
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 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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 2 image(s) missing alt text out of 26.
Priority
Priority 11: 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
Horizontal overflow: 0px. Small tap targets: 42.
Priority
Priority 13: fix during launch polish.
Affected elements
Skip to main content
Product
Solutions
Resources
Fix Prompt
Improve 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: 1035ms. Load complete: 1036ms. First contentful paint: 640ms. Resources: 36. Scripts: 21. Images: 2. Third-party origins: 6. Transfer: not available.
Priority
Priority 14: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
No failed checks in this category.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
Common security headers
Why this needs attention
Several basic browser protection headers were not visible.
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. 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
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 2 image(s) missing alt text out of 26. 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
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 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (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
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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: 1035ms. Load complete: 1036ms. First contentful paint: 640ms. Resources: 36. Scripts: 21. Images: 2. Third-party origins: 6. Transfer: not available. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: 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
Horizontal overflow: 0px. Small tap targets: 42. 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
Skip to main content
Product
Solutions
Resources
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.
Structured data
Detected 2 JSON-LD block(s), 0 parse error(s), and types Country, Organization, ProfessionalService, WebSite.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Detected 3 of 3 core identity signals across the title, description, and H1.
Answer-ready visible text
Detected 2087 visible words and 46 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
No datePublished or dateModified value was detected in structured data.
Supporting-source links
Detected 35 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 287 visible text element(s).
Synthetic search-agent reachability
8 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://bugshield.co.uk/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
GPTBotModel training
Robots: allowed by gptbot allow: / · line 6
Probe: not tested for this control
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
ClaudeBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Claude-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Google-ExtendedData-use policy control
Robots: allowed by google-extended allow: / · line 21
Probe: not tested for this control
BingbotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
PerplexityBotAI search
Robots: allowed by perplexitybot allow: / · line 18
Probe: reachable · HTTP 200 · 100% parity
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
ApplebotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Applebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
meta-externalagentModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
AmazonbotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
CCBotModel training
Robots: allowed by ccbot allow: / · line 24
Probe: not tested for this control
Ready combines robots policy, a bounded synthetic User-Agent fetch, indexability, and snippet eligibility. Synthetic probes do not prove vendor-origin traffic. Purple 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.
