Speed Insights
Grade A
96% performance
https://cleanpasteai.com
LCP
580ms
Largest paint
TBT
176ms
Blocking time
CLS
0.001
Layout shift
91
out of 100
100
out of 100
111/111 rule points
100
out of 100
76/76 rule points
72
out of 100
68/94 rule points
92
out of 100
101/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 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (70), landmark-unique (1), region (5).
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Cleans invisible Unicode
0 characters · 0 words
<button type="button" class="inline-flex min-w-[4.75rem] shrink-0 items-center justify-center whitespace-nowrap rounded-full border border-[#4b8adb]/40 bg-white px-4 py-1.5 text-sm
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Fix any of the following: The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
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: 69.
Priority
Priority 13: fix during launch polish.
Affected elements
Claim 50% Off
Dismiss offer banner
Clean Paste AI
Features
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
32 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.62.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
Claude
ChatGPT
Gemini
Docs
Fix 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.
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.
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.
No failed checks in this category.
Design
Severity mix: 0 critical, 3 high, 6 medium, 2 low.
Failed checks
These checks need attention.
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
32 of 100 rendered text color sample(s) missed WCAG contrast targets. Worst rendered ratio: 2.62. Failed: earned 0 of 8 points.
Priority
Priority 20: lower-risk cleanup after urgent launch blockers.
Affected elements
Claude
ChatGPT
Gemini
Docs
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 3 violation rule(s), including 1 serious or critical rule(s). Top rules: color-contrast (70), landmark-unique (1), region (5). Failed: earned 0 of 18 points.
Priority
Priority 5: fix before sharing the page publicly.
Affected elements
Cleans invisible Unicode
0 characters · 0 words
<button type="button" class="inline-flex min-w-[4.75rem] shrink-0 items-center justify-center whitespace-nowrap rounded-full border border-[#4b8adb]/40 bg-white px-4 py-1.5 text-sm
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination
Fix any of the following: The landmark must have a unique aria-label, aria-labelledby, or title to make landmarks distinguishable
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: 69. Failed: earned 0 of 9 points.
Priority
Priority 13: fix during launch polish.
Affected elements
Claim 50% Off
Dismiss offer banner
Clean Paste AI
Features
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 with lastmod 2026-08-20.
Structured data
Semantic schema score 90/100. Detected 2 JSON-LD block(s), 0 parse error(s), 26 graph node(s), and types AggregateOffer, Answer, ContactPoint, FAQPage, ImageObject, Offer, Organization, Question, SoftwareApplication, 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 “Clean Paste Tool for AI Output”. Title/H1 token overlap is 100%; description match detected; identity schema detected.
Answer-ready visible text
Answerability scored 95/100 from 1455 main-content words, 15 concise answer block(s), 8 question heading(s), 17 definition(s), 1 list(s), and 1 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 171 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://cleanpasteai.com/llms.txt returned HTTP 200; this is supplemental and does not determine AI-search eligibility.
OAI-SearchBotAI search
Robots: allowed by oai-searchbot allow: / · line 12
Probe: reachable · HTTP 200 · 100% parity
GPTBotModel training
Robots: allowed by gptbot allow: / · line 6
Probe: not tested for this control
ChatGPT-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
ClaudeBotModel training
Robots: allowed by claudebot allow: / · line 15
Probe: not tested for this control
Claude-SearchBotAI search
Robots: allowed by claude-searchbot allow: / · line 18
Probe: reachable · HTTP 200 · 100% parity
Claude-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
GooglebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Google-ExtendedData-use policy control
Robots: allowed by google-extended allow: / · line 21
Probe: not tested for this control
BingbotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
PerplexityBotAI search
Robots: allowed by perplexitybot allow: / · line 24
Probe: reachable · HTTP 200 · 100% parity
Perplexity-UserUser-requested fetch
Robots: not applicable to user-requested fetches
Probe: not tested for this control
ApplebotSearch and discovery
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Applebot-ExtendedData-use policy control
Robots: allowed by applebot-extended allow: / · line 30
Probe: not tested for this control
MistralAI-IndexAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
MistralAI-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
meta-externalagentModel training
Robots: allowed by * allow: / · line 2
Probe: not tested for this control
meta-externalfetcherUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
AmazonbotModel training
Robots: allowed by amazonbot allow: / · line 27
Probe: not tested for this control
Amzn-SearchBotAI search
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
Amzn-UserUser-requested fetch
Robots: allowed by * allow: / · line 2
Probe: reachable · HTTP 200 · 100% parity
CCBotModel training
Robots: allowed by * allow: / · line 2
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.
