Speed Insights
Grade A
97% performance
https://socialdata.tools
From socialdata.tools
LCP
1.1s
Largest paint
TBT
90ms
Blocking time
CLS
0.000
Layout shift
81
out of 100
100
out of 100
111/111 rule points
76
out of 100
58/76 rule points
81
out of 100
76/94 rule points
67
out of 100
74/110 rule points
Category point breakdown
Biggest score-losing checks
Add common public security headers
-18 rule ptsWhy 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.
Agent Prompt
Fix rendered axe accessibility violations
-18 rule ptsWhy 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), including 1 serious or critical rule(s). Top rules: scrollable-region-focusable (1).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Scrollable region must have keyboard access
Fix any of the following: Element should have focusable content Element should be focusable
Agent Prompt
Fix rendered layout ergonomics
-9 rule ptsWhy 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: 43.
Priority
Priority 13: fix during launch polish.
Affected elements
SocialData home
Login
Start for free
API reference
Agent Prompt
Add trust signals
-10 rule ptsWhy this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 trust-signal keyword occurrence(s).
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Balance landing page copy
-10 rule ptsWhy this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 1878 visible word(s). General page range: 80-1800 words.
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Agent Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low.
No failed checks in this category.
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.
No failed checks in this category.
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.
Common security headers
0/18Why 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.
Priority
Priority 5: fix before sharing the page publicly.
Agent Prompt
Rendered axe accessibility violations
0/18Why 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), including 1 serious or critical rule(s). Top rules: scrollable-region-focusable (1). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Scrollable region must have keyboard access
Fix any of the following: Element should have focusable content Element should be focusable
Agent Prompt
Text density
0/10Why this needs attention
The page has too little or too much detectable text for a useful launch page.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 1878 visible word(s). General page range: 80-1800 words. Failed: earned 0 of 10 points.
Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Trust signals
0/10Why this needs attention
The page does not expose detectable proof, customer, review, security, or credibility signals.
Trust signals reduce hesitation when strangers see the product for the first time.
Recommended correction
Evidence
Detected 0 trust-signal keyword occurrence(s). Failed: earned 0 of 10 points.
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Agent Prompt
Runtime console health
0/7Why 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 1 site-authored console error(s) and 0 uncaught page error(s) during render. Samples: Hydration completed but contains mismatches. Failed: earned 0 of 7 points.
Priority
Priority 15: fix during launch polish.
Agent Prompt
Rendered layout ergonomics
0/9Why 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: 43. Failed: earned 0 of 9 points.
Priority
Priority 13: fix during launch polish.
Affected elements
SocialData home
Login
Start for free
API reference
Agent 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 100/100. Detected 2 JSON-LD block(s), 0 parse error(s), 24 graph node(s), and types Answer, ContactPoint, CreativeWork, FAQPage, Offer, Organization, QuantitativeValue, Question, SoftwareApplication, UnitPriceSpecification, WebSite. The schema type matches the detected page role.
Public or paywalled content
No isAccessibleForFree structured-data value was detected.
Entity clarity
Entity alignment scored 95/100 for “The X API for public data, priced per result.”. Title/H1 token overlap is 83%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 100/100 from 1408 main-content words, 19 concise answer block(s), 15 question heading(s), 18 definition(s), 6 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 204 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://socialdata.tools/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OpenAIChatGPT searchOAI-SearchBotAI search
Robots: allowed by oai-searchbot allow: / · line 32
Probe: reachable · HTTP 200 · 100% parity
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by gptbot allow: / · line 32
Probe: not tested for this control
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed by claudebot allow: / · line 32
Probe: not tested for this control
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by claude-searchbot allow: / · line 32
Probe: reachable · HTTP 200 · 100% parity
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by claude-user allow: / · line 32
Probe: reachable · HTTP 200 · 100% parity
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by google-extended allow: / · line 32
Probe: not tested for this control
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by perplexitybot allow: / · line 32
Probe: reachable · HTTP 200 · 100% parity
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by applebot allow: / · line 32
Probe: reachable · HTTP 200 · 100% parity
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by applebot-extended allow: / · line 32
Probe: not tested for this control
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by mistralai-user allow: / · line 32
Probe: reachable · HTTP 200 · 100% parity
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by meta-externalagent allow: / · line 32
Probe: not tested for this control
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by amazonbot allow: / · line 32
Probe: not tested for this control
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 5
Probe: reachable · HTTP 200 · 100% parity
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by ccbot allow: / · line 32
Probe: not tested for this control
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.
