Speed Insights
Grade B
89% performance
https://zensched.app
LCP
3.1s
Largest paint
TBT
21ms
Blocking time
CLS
0.09
Layout shift
76
out of 100
86
out of 100
130/150 rule points
88
out of 100
67/76 rule points
90
out of 100
74/80 rule points
79
out of 100
87/110 rule points
Category point breakdown
- Material high-impact failures span 4 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
Shorten the meta description
Why this needs attention
The meta description is 178 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 178 characters, above the 170-character maximum.
Priority
Priority 3: 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); 1 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: label (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Form elements must have labels
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element has no placeholder attribute Element's default semantics were not overridden with role="none" or role="presentation"
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 80/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Review introductory clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 1 visible H1 heading(s), 51 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 30 actionable CTA(s). Rendered evidence was used where available. The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. 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 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 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 1 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 1 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: 1 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 80/100. Detected role: home (high confidence). Failed: earned 31 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
Meta description
Why this needs attention
The meta description is 178 characters, so it is longer than the recommended maximum.
Long descriptions are likely to be truncated or rewritten, which can hide the most useful part of the message.
Recommended correction
Evidence
Meta description is 178 characters, above the 170-character maximum. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
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 80/100: completeness 75/100, graph connectivity 0/100, primary types Organization, currently useful search-feature types Organization. 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
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); 1 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: label (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
Form elements must have labels
Fix any of the following: Element does not have an implicit (wrapped) <label> Element does not have an explicit <label> aria-label attribute does not exist or is empty aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty Element has no title attribute Element has no placeholder attribute Element's default semantics were not overridden with role="none" or role="presentation"
Fix Prompt
Hero clarity signals
Why this needs attention
One or more heading, introductory-copy, or next-action signals fell outside this heuristic's expected range; this does not by itself prove the page is vague.
The introduction should help visitors understand the purpose of this particular page.
Recommended correction
Evidence
Detected 1 visible H1 heading(s), 51 H1 characters, 0 introductory supporting-copy characters after excluding bylines and short labels, and 30 actionable CTA(s). Rendered evidence was used where available. The H1 text is treated as a subject label, so an appropriate short place, product, or page name does not lose points. Detected role: home (high confidence). Failed: earned 9 of 13 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: fix during launch polish.
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: 1 unique above-fold action(s), 3 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 3 unique above-fold action(s), 7 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
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: 3118ms. Load complete: 0ms. First contentful paint: 3060ms. Largest contentful paint: 3060ms. Total blocking time: 21ms. Cumulative layout shift: 0.09. Resources: 110. Scripts: 3. Images: 22. Third-party origins: 26. Transfer: 2452KB. Potential render-blocking resources: 3. Metrics outside the good range: DOMContentLoaded 3118ms (good at or below 2500ms); First contentful paint 3060ms (good at or below 2200ms); Largest contentful paint 3060ms (good at or below 2500ms); Transfer size 2452KB (good at or below 2200KB); Third-party origins 26 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.
DOMContentLoaded
618ms over the rendered audit threshold.
First contentful paint
860ms over the rendered audit threshold.
Largest contentful paint
560ms over the rendered audit threshold.
Transfer size
252KB 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
The exact URL appears in the fetched sitemap.
Structured data
Semantic schema score 80/100. Detected 1 JSON-LD block(s), 0 parse error(s), 1 graph node(s), and primary types Organization. Completeness: 75/100. Graph connectivity: 0/100. A primary schema type matches the detected page role. The schema entity is supported by visible page content.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 55/100 for “Yourbookinglink.Takebookingsanywhere.Keepeverycent.”. Title/H1 token overlap is 0%; description match not detected; identity schema detected.
Answer-ready visible text
Answerability scored 100/100 from 1010 main-content words, 12 concise answer block(s), 9 question heading(s), 2 definition(s), 13 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 96 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://zensched.app/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 * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 26
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 26
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AnthropicClaude user fetchesClaude-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% 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 · 99% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 26
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by bingbot allow: / · line 12
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% 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 * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed by * allow: / · line 26
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 26
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 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 26
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 26
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 26
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.
