Speed Insights
Incomplete capture
Missing LCP, TBT, CLS
https://bunzee.ai
LCP
N/A
Largest paint
TBT
N/A
Blocking time
CLS
N/A
Layout shift
78
out of 100
93
out of 100
103/111 rule points
100
out of 100
76/76 rule points
50
out of 100
47/94 rule points
67
out of 100
74/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 4 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (3), color-contrast (1), link-name (1), aria-allowed-role (3).
Priority
Priority 5: fix before sharing the page publicly.
Fix Prompt
Use one clear H1 and ordered headings
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 1 H1 heading(s) and 4 total headings.
Priority
Priority 9: fix during launch polish.
Fix Prompt
Fix 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: 1, 3, 3, 3.
Priority
Priority 13: fix during launch polish.
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 rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 1204ms. Load complete: 1206ms. First contentful paint: 1028ms. Resources: 96. Scripts: 43. Images: 10. Third-party origins: 13. Transfer: not available.
Priority
Priority 14: 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.
No failed checks in this category.
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.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
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 1 H1 heading(s) and 4 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
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: 1, 3, 3, 3. 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
Semantic buttons and links
Why this needs attention
Interactive controls are not consistently represented as semantic buttons or links.
Non-semantic controls can be hard to use with keyboards and screen readers.
Recommended correction
Evidence
Detected 5 semantic control(s) out of 8. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 17: 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
42 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 1.47. 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 4 violation rule(s), including 3 serious or critical rule(s). Top rules: button-name (3), color-contrast (1), link-name (1), aria-allowed-role (3). 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
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 trust-signal keyword occurrence(s). 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
Rendered speed signals
Why this needs attention
The browser-rendered page shows slow or heavy speed signals.
Slow pages lose impatient visitors and make every SEO, social, and paid-traffic visit work harder.
Recommended correction
Evidence
DOMContentLoaded: 1204ms. Load complete: 1206ms. First contentful paint: 1028ms. Resources: 96. Scripts: 43. Images: 10. Third-party origins: 13. Transfer: not available. Failed: earned 0 of 10 points.
How FreeScan evaluates this check (opens in a new tab)Priority
Priority 14: fix during launch polish.
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 3 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 URL appears in sitemap.xml with lastmod 2026-08-05.
Structured data
Detected 6 JSON-LD block(s), 0 parse error(s), and types AggregateRating, Answer, BreadcrumbList, FAQPage, ListItem, Offer, Organization, Person, PostalAddress, Question, Rating, Review, SearchAction, SoftwareApplication, SpeakableSpecification, 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 88 visible words and 2 audience, use-case, pricing, or integration signals.
Authorship and accountability
Detected author or accountable entity: Sarah, James, Emily, Michael, Jessica.
Published or updated date
Structured data reports dateModified 2026-08-05.
Supporting-source links
Detected 9 external source or reference link(s); link quality still requires editorial review.
Rendered content availability
Rendered audit completed with 111 visible text element(s).
Synthetic search-agent reachability
8 of 8 search/discovery User-Agent probes returned reachable content.
Optional LLM-readable summary
https://bunzee.ai/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: max-image-preview:large; X-Robots-Tag: all
OpenAIOpenAI model trainingGPTBotModel training
Robots: allowed by gptbot allow: / · line 13
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
OpenAIChatGPT user fetchesChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AnthropicClaude model trainingClaudeBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AnthropicClaude searchClaude-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AnthropicClaude user fetchesClaude-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
GoogleGoogle Search and AI featuresGooglebotSearch and discovery
Robots: allowed by googlebot allow: / · line 88
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; Googlebot meta: index,follow; X-Robots-Tag: all
GoogleGemini data use and groundingGoogle-ExtendedData-use policy control
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
MicrosoftBing and CopilotBingbotSearch and discovery
Robots: allowed by bingbot allow: / · line 55
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
PerplexityPerplexity searchPerplexityBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
PerplexityPerplexity user fetchesPerplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AppleSiri, Spotlight, and Safari searchApplebotSearch and discovery
Robots: allowed by applebot allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AppleApple foundation-model trainingApplebot-ExtendedData-use policy control
Robots: allowed by applebot allow: / · line 2
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
Mistral AIMistral searchMistralAI-IndexAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
Mistral AIMistral user fetchesMistralAI-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
MetaMeta AI model and product datameta-externalagentModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
MetaMeta AI user fetchesmeta-externalfetcherUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AmazonAmazon model trainingAmazonbotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AmazonAlexa and Rufus searchAmzn-SearchBotAI search
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
AmazonAlexa user fetchesAmzn-UserUser-requested fetch
Robots: allowed
Probe: reachable · HTTP 200 · 100% parity
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
Common CrawlOpen web datasetsCCBotModel training
Robots: allowed
Probe: not tested for this control
Controls: robots meta: max-image-preview:large; X-Robots-Tag: all
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.
