Speed Insights
Grade C
79% performance
https://livedemo.ai
LCP
388ms
Largest paint
TBT
657ms
Blocking time
CLS
0.002
Layout shift
66
out of 100
83
out of 100
85/103 rule points
55
out of 100
42/76 rule points
50
out of 100
47/94 rule points
76
out of 100
84/110 rule points
Category point breakdown
Biggest score-losing checks
Remove exposed sensitive files
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response.
Priority
Priority 1: fix before sharing the page publicly.
Fix Prompt
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 8 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), color-contrast (1), link-name (4), heading-order (2), landmark-main-is-top-level (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Buttons must have discernible text
Fix any of the following: Element does not have inner text that is visible to screen readers 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 does not have an implicit (wrapped) <label> Element does not have an explicit <label> Element's default semantics were not overridden with role="none" or role="presentation"
Craft a demo!
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers 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
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers 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
Fix Prompt
Add basic structured data
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s).
Priority
Priority 12: fix during launch polish.
Fix Prompt
Use one clear H1 and ordered headings
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 8 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 6 high, 3 medium, 1 low.
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, 6 high, 3 medium, 1 low.
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.
Heading structure
Why this needs attention
The page heading structure is either missing a single main heading or skips heading levels.
Clear headings help visitors, search engines, and assistive technology understand the page quickly.
Recommended correction
Evidence
Detected 1 H1 heading(s) and 8 total headings. Failed: earned 0 of 8 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Schema presence
Why this needs attention
No JSON-LD schema was detected on the page.
Structured data gives search and answer engines explicit facts about your product.
Recommended correction
Evidence
Detected 0 JSON-LD schema block(s). Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: fix during launch polish.
Fix Prompt
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
Sensitive file probes
Why this needs attention
A small public allowlist probe found a sensitive-looking file path.
Publicly exposed config or backup files can leak implementation details or secrets.
Recommended correction
Evidence
A small allowlist probe returned a public success response. Failed: earned 0 of 16 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 1: 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
Heading levels found: 1, 2, 3, 2, 3, 2, 4, 4. 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
Semantic buttons and links
Why this needs attention
Interactive controls are not consistently represented as semantic buttons or links.
Non-semantic controls can be hard to use with keyboards and screen readers.
Recommended correction
Evidence
Detected 3 semantic control(s) out of 4. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 17: 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
12 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 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
Craft a demo!
Simple, Honest Pricing
Start free. Scale when you're ready.
Monthly
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 8 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (1), color-contrast (1), link-name (4), heading-order (2), landmark-main-is-top-level (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
Buttons must have discernible text
Fix any of the following: Element does not have inner text that is visible to screen readers 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 does not have an implicit (wrapped) <label> Element does not have an explicit <label> Element's default semantics were not overridden with role="none" or role="presentation"
Craft a demo!
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers 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
Links must have discernible text
Fix all of the following: Element is in tab order and does not have accessible text Fix any of the following: Element does not have text that is visible to screen readers 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
Fix Prompt
Spacing consistency
Why this needs attention
The page exposes few consistent spacing signals in class or inline styles.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Detected 1 spacing class/style signal(s). Failed: earned 0 of 7 points.
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: 670ms. Load complete: 0ms. First contentful paint: 388ms. Resources: 44. Scripts: 21. Images: 8. Third-party origins: 15. 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: 8. 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 tutorials...
Resources
Interactive control
Start creating
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 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and types none. No primary schema type matched the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 55/100 for “Turn any product flowinto an interactive demoguided storybuyer journeyinteractive demobuyers can click through”. Title/H1 token overlap is 0%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 78/100 from 253 main-content words, 2 concise answer block(s), 0 question heading(s), 1 definition(s), 7 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 129 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://livedemo.ai/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index,follow
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow; Googlebot meta: index,follow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index,follow
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 3
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by * allow: / · line 3
Probe: not tested for this control
Controls: robots meta: index,follow
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.
