Speed Insights
Grade A
100% performance
https://xmail.black
From xmail.black
LCP
368ms
Largest paint
TBT
0ms
Blocking time
CLS
0.002
Layout shift
39
out of 100
40
out of 100
57/142 rule points
81
out of 100
59/72 rule points
72
out of 100
58/80 rule points
63
out of 100
68/101 rule points
Category point breakdown
- The hero and primary action are missing alongside 6 launch essentials.
- Material high-impact failures span 4 categories.
- The page has 4 strong thin-page signals across content, navigation, action, and credibility.
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
Improve AI search and crawler readiness
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. Non-robots access or indexing restrictions affect Claude-SearchBot, Claude-User, PerplexityBot, and 1 more. Claude-SearchBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Claude-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. PerplexityBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. MistralAI-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 67%: discovery 34/45, index and snippet eligibility 20/25, synthetic reachability 13/20, sitemap freshness 0/10. robots.txt did not block the scored AI search or user-fetch agents for this page path.
Priority
Priority 2: 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 15/100, semantic structured data 0/100. Detected role: home (high confidence).
Priority
Priority 6: fix during launch polish.
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 2 of 5 common public security controls. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none.
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
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit.
Priority
Priority 4: fix before sharing the page publicly.
Fix Prompt
Add a useful meta description
Why this needs attention
No meta description was detected in the public page metadata.
Without a description, search and answer previews may select less useful page text automatically.
Recommended correction
Evidence
No meta description was detected.
Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 2 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: 0 review and 2 not applicable.
Design
Severity mix: 0 critical, 3 high, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
SEO / AEO
Severity mix: 1 critical, 8 high, 3 medium, 1 low. Coverage: 0 review and 2 not applicable.
Accessibility
Severity mix: 0 critical, 3 high, 6 medium, 0 low. Coverage: 0 review and 2 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, 7 medium, 1 low. Coverage: 0 review and 0 not applicable.
Failed checks
These checks need attention.
Crawler access
Why this needs attention
One or more AI discovery, user-fetch, indexability, snippet, synthetic reachability, or sitemap signals need attention.
AI search systems need crawlable, reachable, indexable, and quotable public content. Training and data-use choices remain neutral publisher preferences.
Recommended correction
Evidence
FreeScan.app reached the public page with HTTP 200. Non-robots access or indexing restrictions affect Claude-SearchBot, Claude-User, PerplexityBot, and 1 more. Claude-SearchBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. Claude-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. PerplexityBot: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. MistralAI-User: Allowed by * allow: / on line 31. Synthetic User-Agent probe returned HTTP 403. GPTBot, ClaudeBot, Google-Extended, and 4 more are explicit training or data-use opt-outs and do not reduce the AEO score. AEO crawler readiness is 67%: discovery 34/45, index and snippet eligibility 20/25, synthetic reachability 13/20, sitemap freshness 0/10. robots.txt did not block the scored AI search or user-fetch agents for this page path. Failed: earned 9 of 14 points from partial coverage.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 2: fix before sharing the page publicly.
Fix Prompt
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 15/100, semantic structured data 0/100. Detected role: home (high confidence). Failed: earned 13 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
Meta description
Why this needs attention
No meta description was detected in the public page metadata.
Without a description, search and answer previews may select less useful page text automatically.
Recommended correction
Evidence
No meta description was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 3: fix before sharing the page publicly.
Fix Prompt
Canonical tag
Why this needs attention
The page does not declare which public URL is the preferred version.
A canonical tag reduces duplicate URL confusion before marketing links start spreading.
Recommended correction
Evidence
No canonical link tag was detected. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 9: fix during launch polish.
Fix Prompt
Sitemap validity
Why this needs attention
The sitemap file was not reachable or did not look like valid sitemap XML.
A sitemap helps search engines discover the landing page and related public pages sooner.
Recommended correction
Evidence
sitemap at /sitemap.xml returned HTTP success but did not contain a urlset or sitemapindex root. Failed: earned 0 of 12 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 7: 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
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
Internal link basics
Why this needs attention
The page has too few detectable links to other public pages on the same site.
Internal links help visitors find pricing, docs, contact, legal, or product details without getting stuck.
Recommended correction
Evidence
Detected 0 visible internal link target(s) in the rendered page. Failed: earned 0 of 6 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 16: 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 2 of 5 common public security controls. Present: x-content-type-options, referrer-policy. Missing: strict-transport-security, content-security-policy, frame protection (x-frame-options or content-security-policy frame-ancestors). Needs strengthening: none. Failed: earned 5 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
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 visible main landmark(s) and 0 visible 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 23 rendered text color sample(s) across captured viewports missed WCAG contrast targets. Worst rendered ratio: 1. Mobile 390px viewport: 0 of 12 failed. 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
Xmail
Black
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); 2 non-contrast rule(s) are scored here, including 0 serious or critical rule(s). Color contrast is scored once by the dedicated contrast check. 1 result(s) require review. Top rules: landmark-one-main (1), region (8). Failed: earned 14 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
Document should have one main landmark
Fix all of the following: Document does not have a main landmark
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
All page content should be contained by landmarks
Fix any of the following: Some page content is not contained by landmarks
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
Rendered CTA evidence: 0 desktop above-fold action(s) across 0 unique purpose(s); 0 mobile above-fold action(s) across 0 unique purpose(s). 0 repeated occurrence(s) were deduplicated and earned no extra credit. 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
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 1 visible H1 heading(s), 11 H1 characters, 37 introductory supporting-copy characters after excluding bylines and short labels, and 2 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
Text density
Why this needs attention
The page may not provide enough useful context for its detected role, or its rendered structure needs review.
Too little copy can leave visitors confused; too much copy can bury the value proposition.
Recommended correction
Evidence
Detected about 35 visible word(s) in the rendered page. The contextual range is 120-1200 words for the detected home page role. Failed: earned 3 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
Rendered composition and spacing
Why this needs attention
Rendered geometry found cramped text, overly long lines, undersized body copy, or too many competing actions in the first viewport.
Consistent spacing helps the page feel deliberate and easier to scan.
Recommended correction
Evidence
Desktop 1366px: 0 unique above-fold action(s), 1 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Mobile 390px: 0 unique above-fold action(s), 1 body sample(s) below 14px, 0 cramped line-height sample(s), and 0 overlong line sample(s). Repeated CTA labels are deduplicated and do not earn extra credit. Failed: earned 2 of 7 points from partial coverage.
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
Rendered typography, geometry, and contrast show that the main heading is not distinct or legible enough, or that the hierarchy needs manual review.
Hierarchy tells visitors what to read first and what action to take next.
Recommended correction
Evidence
The rendered H1 is 144px/100 weight versus a 18px/100 median body style (8× size). Captured 1 supporting heading(s) and 2 action(s). The main heading has a clear rendered emphasis over body copy. 2 of 23 rendered text samples missed contrast targets, so hierarchy is not considered fully legible. Failed: earned 6 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
No canonical URL was detected.
Sitemap coverage and freshness
The exact scanned URL was not found 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 70/100 for “Xmail Black”. Title/H1 token overlap is 100%; description match not detected; identity schema not detected.
Answer-ready visible text
Answerability scored 15/100 from 47 main-content words, 0 concise answer block(s), 0 question heading(s), 2 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 11 visible text element(s).
Synthetic search-agent reachability
6 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-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
OpenAIOpenAI model trainingGPTBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by gptbot disallow: / · line 55
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 trainingClaudeBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by claudebot disallow: / · line 46
Synthetic probe: not applicable to this policy control
AnthropicClaude searchClaude-SearchBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
AnthropicClaude user fetchesClaude-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
GoogleGoogle Search and AI featuresGooglebotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
GoogleGemini data use and groundingGoogle-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by google-extended disallow: / · line 52
Synthetic probe: not applicable to this policy control
MicrosoftBing and CopilotBingbotPASS · ALLOWED · Toggle crawler details
Search and discovery
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
PerplexityPerplexity searchPerplexityBotFAIL · BLOCKED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
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 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AppleApple foundation-model trainingApplebot-ExtendedOPTED OUT · Toggle crawler details
Data-use policy control
Robots: blocked by applebot-extended disallow: / · line 37
Synthetic probe: not applicable to this policy control
Mistral AIMistral searchMistralAI-IndexPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Mistral AIMistral user fetchesMistralAI-UserFAIL · BLOCKED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: blocked · HTTP 403
MetaMeta AI model and product datameta-externalagentOPTED OUT · Toggle crawler details
Model training
Robots: blocked by meta-externalagent disallow: / · line 58
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 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAmazon model trainingAmazonbotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by amazonbot disallow: / · line 34
Synthetic probe: not applicable to this policy control
AmazonAlexa and Rufus searchAmzn-SearchBotPASS · ALLOWED · Toggle crawler details
AI search
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
AmazonAlexa user fetchesAmzn-UserPASS · ALLOWED · Toggle crawler details
User-requested fetch
Robots: allowed by * allow: / · line 31
Synthetic probe: reachable · HTTP 200 · 100% sampled-content parity
Common CrawlOpen web datasetsCCBotOPTED OUT · Toggle crawler details
Model training
Robots: blocked by ccbot disallow: / · line 43
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.
