Speed Insights
Grade A
98% performance
https://callintel.io
LCP
1.2s
Largest paint
TBT
0ms
Blocking time
CLS
0.001
Layout shift
77
out of 100
83
out of 100
124/150 rule points
92
out of 100
66/72 rule points
44
out of 100
31/70 rule points
89
out of 100
83/93 rule points
Category point breakdown
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
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 5 violation rule(s); 4 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: aria-prohibited-attr (1), color-contrast (2), heading-order (4), landmark-one-main (1), region (121).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Elements must only use permitted ARIA attributes
Fix all of the following: aria-label attribute cannot be used on a div with no valid role attribute.
Get Started
Elements must meet minimum color contrast ratio thresholds
Heading levels should only increase by one
Fix any of the following: Heading order invalid
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
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 70/100, answer-ready text 60/100, semantic structured data 70/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Fix 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, 3, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 4, 3, 3, 3, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 2, 6, 6, 6, 6, 6, 6, 6, 6, 6, 6, 6, 6, 2, 2, 4, 4, 4, 4, 4, 4, 4, 2, 4, 4, 4, 4, 4.
Priority
Priority 13: 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 56 total headings.
Priority
Priority 9: 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 1 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 2 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 2 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: 2 review and 1 not applicable.
Security
Severity mix: 2 critical, 3 high, 0 medium, 0 low. Coverage: 0 review and 1 not applicable.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 2 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 70/100, answer-ready text 60/100, semantic structured data 70/100. Detected role: home (high confidence). Failed: earned 27 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 1 H1 heading(s) and 56 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
Open Graph basics
Why this needs attention
The page is missing several social preview fields.
Launch links on X, LinkedIn, Slack, and communities look less trustworthy without a strong preview.
Recommended correction
Evidence
Detected 0 of 4 Open Graph basics. Failed: earned 0 of 5 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: lower-risk cleanup after urgent launch blockers.
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
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, 3, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 4, 3, 3, 3, 3, 3, 3, 2, 2, 3, 3, 3, 3, 2, 2, 6, 6, 6, 6, 6, 6, 6, 6, 6, 6, 6, 6, 2, 2, 4, 4, 4, 4, 4, 4, 4, 2, 4, 4, 4, 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
Landmark presence
Why this needs attention
The page is missing common landmarks such as header, nav, main, or footer.
Landmarks make the page easier to navigate for assistive technology and keyboard users.
Recommended correction
Evidence
Detected 0 main landmark(s) and 9 total landmark element(s) or roles. A page should expose one main landmark. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 18: 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
2 of 110 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 2.91. Mobile 390px viewport: 2 of 110 failed; worst ratio 2.91: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
Get Started
Get Started Free
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 5 violation rule(s); 4 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: aria-prohibited-attr (1), color-contrast (2), heading-order (4), landmark-one-main (1), region (121). Failed: earned 8 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
Elements must only use permitted ARIA attributes
Fix all of the following: aria-label attribute cannot be used on a div with no valid role attribute.
Get Started
Elements must meet minimum color contrast ratio thresholds
Heading levels should only increase by one
Fix any of the following: Heading order invalid
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: 1145ms. Load complete: 0ms. First contentful paint: 1164ms. Resources: 23. Scripts: 3. Images: 0. Third-party origins: 1. Transfer: 5592KB. Potential render-blocking resources: 3. Exceeded thresholds: Transfer size 5592KB (threshold 2200KB). 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.
Transfer size
3392KB over the rendered audit threshold.
3ipm9uc-yh5z8.css
1wlyh3tvgvl8u.css
0cz1d0mv5g_q7.js
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-06-28T08:33:06.758Z.
Structured data
Semantic schema score 70/100. Detected 1 JSON-LD block(s), 0 parse error(s), 6 graph node(s), and types ContactPoint, Offer, Organization, SoftwareApplication, WebSite. The schema type matches 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 70/100 for “Turn every call into booked revenue.”. Title/H1 token overlap is 0%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 60/100 from 797 main-content words, 1 concise answer block(s), 0 question heading(s), 5 definition(s), 1 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 0 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://callintel.io/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 8
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
OpenAIOpenAI model trainingGPTBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by gptbot allow: / · line 5
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 14
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
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 2
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * 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 google-extended allow: / · line 29
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 2
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
PerplexityPerplexity searchPerplexityBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by perplexitybot allow: / · line 23
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 2
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 applebot-extended allow: / · line 32
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
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 2
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 2
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 2
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
AmazonAmazon model trainingAmazonbotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by * allow: / · line 2
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 2
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 2
Synthetic probe: reachable · HTTP 200 · 99% sampled-content parity
Common CrawlOpen web datasetsCCBotPOLICY ALLOWED · Toggle crawler details
Model training
Robots: allowed by ccbot allow: / · line 35
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.
