Speed Insights
Grade A
96% performance
https://www.nsandi.com
From nsandi.com
LCP
1.4s
Largest paint
TBT
8ms
Blocking time
CLS
0.06
Layout shift
69
out of 100
66
out of 100
85/128 rule points
90
out of 100
69/76 rule points
77
out of 100
62/80 rule points
80
out of 100
81/101 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
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 63/100, answer-ready text 17/100, semantic structured data 0/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 8 violation rule(s); 8 non-contrast rule(s) are scored here, including 6 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 3 result(s) require review. Top rules: aria-required-children (1), aria-required-parent (6), list (1), listitem (3), object-alt (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Certain ARIA roles must contain particular children
Fix any of the following: Element has children which are not allowed: li
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parents role not present: menu, menubar, group
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parents role not present: menu, menubar, group
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parents role not present: menu, menubar, group
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 4 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: content-security-policy. Needs strengthening: none.
Priority
Priority 5: fix before sharing the page publicly.
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 2 visible H1 heading(s), 34 H1 characters, 118 introductory supporting-copy characters after excluding bylines and short labels, and 8 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
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
No JSON-LD schema blocks were detected.
Priority
Priority 12: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 1 review and 2 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: 3 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 1 review and 2 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: 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 63/100, answer-ready text 17/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 12 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
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 2 visible H1 heading(s) and 15 visible heading(s) in the rendered page. Heading-level order is assessed separately under Accessibility. Failed: earned 3 of 8 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: 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
No JSON-LD schema blocks were detected. 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 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 4 of 5 common public security controls. Present: strict-transport-security, x-content-type-options, frame protection (x-frame-options), referrer-policy. Missing: content-security-policy. Needs strengthening: none. 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.
Fix Prompt
Visible cookie flags
Why this needs attention
The safe public scan could not inspect private or browser-set cookies, so cookie flag coverage was not verified.
Session and preference cookies should avoid unnecessary exposure before early users sign in or submit forms.
Recommended correction
Evidence
Observed 2 cookie(s) without storing names or values. Secure: 2/2. HttpOnly: 1/2. SameSite: 2/2. SameSite=None without Secure: 0. Failed: earned 3 of 4 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
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); 8 non-contrast rule(s) are scored here, including 6 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 3 result(s) require review. Top rules: aria-required-children (1), aria-required-parent (6), list (1), listitem (3), object-alt (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
Certain ARIA roles must contain particular children
Fix any of the following: Element has children which are not allowed: li
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parents role not present: menu, menubar, group
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parents role not present: menu, menubar, group
Certain ARIA roles must be contained by particular parents
Fix any of the following: Required ARIA parents role not present: menu, menubar, group
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 2 visible H1 heading(s), 34 H1 characters, 118 introductory supporting-copy characters after excluding bylines and short labels, and 8 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 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: 1780ms. Load complete: 1926ms. First contentful paint: 1164ms. Largest contentful paint: 1404ms. Total blocking time: 8ms. Cumulative layout shift: 0.061. Resources: 45. Scripts: 15. Images: 9. Third-party origins: 5. Transfer: 2470KB. Potential render-blocking resources: 4. Metrics outside the good range: Transfer size 2470KB (good at or below 2200KB). 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.
Transfer size
270KB over the rendered audit threshold.
js_DOuG-FdXWK8WfSEbuMSukgMDtlXo_CcFc7E6zS4y3K8.js
jquery.min.js
css_1de4syK-QcY3pGTfnM0-Bl9-LFNNdgblSZLRqDlbfG8.css
Fix Prompt
Runtime console health
Why this needs attention
The rendered page produced console or uncaught JavaScript errors.
Runtime errors can break forms, CTAs, animations, tracking, or responsive behavior even when the static HTML looks fine.
Recommended correction
Evidence
Detected 0 site-authored console error(s) and 3 uncaught page error(s) during render. Samples: Cannot read properties of null (reading 'addEventListener') | $.cookie is not a function | $(...).stickyTableHeaders is not a function Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 15: 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.
Structured data
Semantic schema score 0/100. Detected 0 JSON-LD block(s), 0 parse error(s), 0 graph node(s), and primary types none. Completeness: 0/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 63/100 for “Saving. Nothing more, Nothing less”. Title/H1 token overlap is 25%; description match detected; identity schema not detected.
Answer-ready visible text
Answerability scored 17/100 from 65 main-content words, 0 concise answer block(s), 1 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 66 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-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
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
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
AnthropicClaude user fetchesClaude-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
GoogleGoogle Search and AI featuresGooglebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
GoogleGemini data use and groundingGoogle-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotUNKNOWN · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
PerplexityPerplexity searchPerplexityBotUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
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 searchApplebotUNKNOWN · Toggle crawler details
Search and discovery
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
AppleApple foundation-model trainingApplebot-ExtendedPOLICY ALLOWED · Toggle crawler details
Data-use policy control
Robots: allowed
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
Mistral AIMistral user fetchesMistralAI-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
MetaMeta AI model and product datameta-externalagentPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
MetaMeta AI user fetchesmeta-externalfetcherUNKNOWN · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotUNKNOWN · Toggle crawler details
AI search
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
AmazonAlexa user fetchesAmzn-UserUNKNOWN · Toggle crawler details
User-requested fetch
Robots: allowed
Synthetic probe: redirected · HTTP 302
Redirect target: https://www.nsandi.com/
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed
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.
