Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://www.maabarium.com
From https://maabarium.com/
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
86
out of 100
89
out of 100
99/111 rule points
96
out of 100
73/76 rule points
72
out of 100
68/94 rule points
85
out of 100
94/110 rule points
Category point breakdown
Biggest score-losing checks
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 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (2).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Publish a valid sitemap.xml
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.xml returned HTTP success but did not contain a urlset or sitemapindex root.
Priority
Priority 7: fix during launch polish.
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 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options.
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Fix 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: 14.
Priority
Priority 13: fix during launch polish.
Fix Prompt
Improve detectable color 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
75 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
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.
sitemap.xml 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.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
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 4 of 5 common public security headers. Present: strict-transport-security, content-security-policy, x-content-type-options, referrer-policy. Missing: x-frame-options. Failed: earned 15 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
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
75 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 1 violation rule(s), including 0 serious or critical rule(s). Top rules: region (2). 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
Runtime console health
Why 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 console error(s) and 0 uncaught page error(s) during render. Failed: earned 0 of 7 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 15: 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: 14. 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
The exact scanned URL was not found in the fetched sitemap.xml.
Structured data
Detected 1 JSON-LD block(s), 0 parse error(s), and types Offer, Organization, SoftwareApplication.
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 1142 visible words and 34 audience, use-case, pricing, or integration signals.
Authorship and accountability
No author meta value or structured-data author was detected.
Published or updated date
No datePublished or dateModified value was detected in structured data.
Supporting-source links
Detected 16 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 198 visible text element(s).
Synthetic search-agent reachability
8 of 8 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 by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by * allow: / · line 2
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 by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index,follow
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index,follow
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed by * allow: / · line 2
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 by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index,follow
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index,follow
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
Controls: robots meta: index,follow
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: index,follow
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed by * allow: / · line 2
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.
