Speed Insights
Grade A
97% performance
https://socialscheduling.tools
From socialscheduling.tools
LCP
960ms
Largest paint
TBT
57ms
Blocking time
CLS
0.02
Layout shift
85
out of 100
100
out of 100
110/110 rule points
75
out of 100
54/72 rule points
100
out of 100
94/94 rule points
66
out of 100
73/110 rule points
Category point breakdown
Biggest score-losing checks
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
Make the primary CTA obvious
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
No actionable link or button with a clear CTA label was detected.
Priority
Priority 4: 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 1 H1 heading(s), 53 H1 characters, 151 supporting-copy characters, and 0 actionable CTA(s).
Priority
Priority 6: fix during launch polish.
Fix Prompt
Add trust signals
Why 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 strong, specific trust or proof signal(s). Generic words such as “security” do not count by themselves.
Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Strengthen visual hierarchy
Why this needs attention
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
Detected 3 of 4 hierarchy signals from one H1, supporting headings, an actionable CTA, and emphasized text.
Priority
Priority 12: fix during launch polish.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 1 not applicable.
No failed checks in this category.
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, 5 medium, 0 low. Coverage: 0 review and 0 not applicable.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 7 high, 3 medium, 1 low. Coverage: 0 review and 1 not applicable.
No failed checks in this category.
Accessibility
Severity mix: 0 critical, 3 high, 5 medium, 0 low. Coverage: 0 review and 0 not applicable.
No failed checks in this category.
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: 0 review and 0 not applicable.
Failed checks
These checks need attention.
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
Visible primary CTA
Why this needs attention
The page does not have a detectable call to action.
Early visitors need a clear next step, such as trying the product, joining a waitlist, or booking a demo.
Recommended correction
Evidence
No actionable link or button with a clear CTA label was detected. Failed: earned 0 of 14 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 4: 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 1 H1 heading(s), 53 H1 characters, 151 supporting-copy characters, and 0 actionable CTA(s). Failed: earned 11 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
Text density
Why 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 1533 visible word(s). Expected 120-1200 words for the detected home page role. Failed: earned 8 of 10 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 21: lower-risk cleanup after urgent launch blockers.
Fix Prompt
Trust signals
Why 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 strong, specific trust or proof signal(s). Generic words such as “security” do not count by themselves. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: lower-risk cleanup after urgent launch blockers.
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 0 spacing uses across 0 distinct spacing token(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
Visual hierarchy
Why this needs attention
The page does not expose enough hierarchy signals from headings, emphasis, or CTA structure.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
Detected 3 of 4 hierarchy signals from one H1, supporting headings, an actionable CTA, and emphasized text. Failed: earned 7 of 9 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 12: 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 100/100. Detected 1 JSON-LD block(s), 0 parse error(s), 44 graph node(s), and types ImageObject, ItemList, ListItem, Organization, Person, WebPage, 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 100/100 for “Compare social media scheduling tools for your setup.”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 90/100 from 854 main-content words, 4 concise answer block(s), 1 question heading(s), 5 definition(s), 11 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 128 visible text element(s).
Synthetic search-agent reachability
8 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-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed
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
Probe: not tested for this control
Controls: robots meta: index, follow
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
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
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: index, follow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index, follow
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
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.
