Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://aicallingagents.co.in
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
70
out of 100
84
out of 100
93/111 rule points
55
out of 100
42/76 rule points
61
out of 100
57/94 rule points
80
out of 100
88/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 2 violation rule(s), including 0 serious or critical rule(s). Top rules: heading-order (7), region (54).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Clarify the hero promise
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 4 H1 heading(s) and 145 meta-description characters.
Priority
Priority 6: fix during launch polish.
Fix Prompt
Write a clear page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 78 characters.
Priority
Priority 8: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 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, 7 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.
Page title
Why this needs attention
The browser title is missing, too short, or too long for a reliable search result headline.
Search engines, social previews, and saved browser tabs use the title to tell people what your product is.
Recommended correction
Evidence
Title is 78 characters. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 8: 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 4 H1 heading(s) and 54 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
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: 4, 2, 3, 3, 3, 3, 3, 3, 3, 6, 3, 4, 4, 6, 1, 6, 1, 3, 6, 1, 4, 3, 4, 3, 4, 3, 4, 3, 4, 3, 4, 3, 4, 4, 4, 4, 4, 4, 6, 1, 3, 3, 3, 3, 4, 3, 5, 5, 5, 2, 2, 2, 2, 2. 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
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
17 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.
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 2 violation rule(s), including 0 serious or critical rule(s). Top rules: heading-order (7), region (54). 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
Hero clarity signals
Why this needs attention
The hero area does not provide enough clear product context.
Visitors decide quickly whether the product is relevant; a vague hero weakens every acquisition channel.
Recommended correction
Evidence
Detected 4 H1 heading(s) and 145 meta-description characters. Failed: earned 0 of 13 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 6: 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: 31. Failed: earned 0 of 9 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 13: 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
A sitemap index was found; this safe scan did not recursively fetch child sitemaps.
Structured data
Detected 1 JSON-LD block(s), 0 parse error(s), and types BreadcrumbList, EntryPoint, ImageObject, ListItem, PropertyValueSpecification, ReadAction, SearchAction, WebPage, 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 722 visible words and 17 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
Structured data reports dateModified 2026-07-20T06:08:10+00:00.
Supporting-source links
Detected 31 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 271 visible text element(s).
Synthetic search-agent reachability
8 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://aicallingagents.co.in/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow, max-image-preview:large, max-snippet:-1, max-video-preview:-1
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.
