← Analyze a URL · Tested sites

www.readthedocs.org

Report from 7/23/2026, 10:32:52 AM https://www.readthedocs.org
Latest run · lab, cold cache
49
7/23/2026
28-day score · p75 · the standard
—
4/7 runs — building history (nightly)

Scored by v3 · source-of-truth hashes: score db860d6ac94e · thresholds e94f8b33e500 — verifiable against the canonical scorer.

The 28-day score is the p75 of nightly runs — the stable number to cite. Deterministic metrics (CRR/SSD/TC) show their latest value (they move only when the site changes); timing (TTFUT) and answer-fidelity (AF) are smoothed by 28-day p75 — the same lab-vs-field split Core Web Vitals uses. Synthetic daily measurement, not real-user field data.

Core Agent Vitals badge  Embed this badge

Show your agent-readiness score anywhere — it links back to this report.

[![Core Agent Vitals](https://agentvitals.dev/badge/readthedocs.org.svg)](https://agentvitals.dev/results?url=https%3A%2F%2Fwww.readthedocs.org)
<a href="https://agentvitals.dev/results?url=https%3A%2F%2Fwww.readthedocs.org"><img src="https://agentvitals.dev/badge/readthedocs.org.svg" alt="Core Agent Vitals" height="20"></a>
What AI tells your customers about youAgent confidence: LOW
🟡Business nameRead the Docs · guessed from page text (no structured data)
❌Categorynot found
➖Pricenot applicable · not applicable to this page type
➖Locationnot applicable · not applicable to this page type
➖Hoursnot applicable · not applicable to this page type
➖Productsnot applicable · not applicable to this page type
🟡DescriptionRead the Docs is a documentation building and hosting platform aimed at helping developers creating documentation from code with versioned documentation, integrated search, pull request previews an… · guessed from page text (no structured data)

An agent is likely to fabricate missing details rather than say “I don’t know”. 0/3 applicable facts come from machine-readable structured data.

DesktopMobile
49
Overall score
weighted CAV (0–100)
FAIL
0–4950–8990–100

Metrics

94%
CRR Content Recovery Needs work
0.33
SSD Semantic Signal Density Poor
494 tok
TC Token Cost Good
48 ms
TTFUT Time to First Useful Token N/A

Token Cost breakdown

Where the page's tokens go (≈1,784 across regions). 41% is non-content — chrome and boilerplate an agent pays for. Add landmark roles (main/nav/header/footer) so agents can skip it.

Content
58.6% · 1,046
Chrome (nav / header / footer)
14.4% · 257
Boilerplate (cookie / ad)
0% · 0
Other
27% · 481

Final screenshot

Final screenshot of https://www.readthedocs.org

Diagnostics

high SSD Low signal-to-noise for agents

content vs chrome/boilerplate

Evidencesignal 0.55 · JSON-LD 0/1 · missing: structured-data
ImpactAgent spends tokens parsing nav/boilerplate instead of content.
Effort30–90 min

Fix: Wrap the real content in <main>/<article>, cut repeated nav/boilerplate, and keep the primary content dense and early in the DOM.

medium CRR Content is hidden behind JavaScript

pre-JS raw HTML

Evidence6% of content requires JS · 94% of rendered content recovered (rest is placeholder/wrong)
ImpactA non-rendering agent never sees the JS-injected content.
Effort1–4 h

Fix: Server-render or statically generate the main content so a non-JS agent still receives it; make client rendering a progressive enhancement, not the source of truth.

medium TC 41.4% of tokens are non-content (boilerplate/chrome)

agent representation — token decomposition

EvidenceToken decomposition: content 58.6%, chrome 14.4%, boilerplate 0%, other 27%. Only 58.6% of the agent's tokens are real content.
ImpactAn agent pays for boilerplate on every request and has less context left for the real content.
Effort30–90 min

Fix: Strip repeated nav/header/footer/cookie chrome from the agent-visible output; wrap content in <main>/<article> so the extractor keeps signal and drops boilerplate.

Rendered profile: headless

Agent Discoverability 57/100 · Needs Work

Access & discovery checks — separate from the gated CAV metrics above. Click an issue for business impact, what we measured, and how to fix. · Take the Agent Readiness course →

Agent files & endpoints

✗ llms.txt Absent at /llms.txt and /.well-known/llms.txt Learn →
✗ robots.txt (AI bots) Blocks: * (all) Learn →
✗ sitemap.xml No /sitemap.xml Learn →
✗ JSON-LD structured data No JSON-LD found Learn →
~ agents.json Absent (emerging standard) Learn →
~ WebMCP endpoint Absent (emerging standard) Learn →
~ OpenAPI / API docs No OpenAPI/Swagger found Learn →

Issues (7)

✗ robots.txt allows AI bots high impact Blocks: * (all)

Business impact If robots.txt blocks AI crawlers you are invisible to ChatGPT, Claude and Perplexity — they skip you and recommend a competitor instead.

What we measured We read /robots.txt and test it against 16 AI user-agents (GPTBot, ClaudeBot, PerplexityBot, …) for a Disallow that blocks them.

How to fix Allow major AI bots to public content; restrict only private paths (/admin, /api).

Learn how to implement →

User-agent: GPTBot
Allow: /
Disallow: /admin/

Spec: https://platform.openai.com/docs/gptbot

✗ llms.txt present high impact Absent at /llms.txt and /.well-known/llms.txt

Business impact llms.txt is the robots.txt for AI: it tells agents what your site is, what matters, and where to find it. Without it AI guesses — and guessing means inaccurate recommendations and lost visibility.

What we measured We fetch /llms.txt and /.well-known/llms.txt and validate the spec (H1 title + a one-line blockquote summary). We also note /llms-full.txt (your full content as Markdown).

How to fix Create /llms.txt with a short summary + key pages; optionally /llms-full.txt with full content in Markdown.

Learn how to implement →

# Your Site
> One-line description for AI agents.

## Key pages
- /products — catalog
- /pricing — plans
- /docs — documentation

Spec: https://llmstxt.org

✗ Structured data (JSON-LD) medium impact No JSON-LD found

Business impact Schema.org JSON-LD tells agents what a page IS (product, article, business) with typed fields (price, rating, hours). Without it agents extract less reliably.

What we measured We parse <script type=application/ld+json>, validate it, and check for populated @type fields.

How to fix Add JSON-LD: Organization/LocalBusiness on the homepage, Product on product pages, Article on posts.

Learn how to implement →

<script type="application/ld+json">{"@context":"https://schema.org","@type":"Organization","name":"Your Co","url":"https://example.com"}</script>

Spec: https://schema.org/

✗ XML sitemap present medium impact No /sitemap.xml

Business impact A sitemap is your table of contents for AI crawlers. Without it agents follow homepage links and miss deep pages (products, docs, pricing) — shrinking what they can recommend.

What we measured We fetch /sitemap.xml (and /sitemap_index.xml), confirm valid XML with <loc> entries, and check <lastmod> freshness.

How to fix Generate an XML sitemap of all public pages with current lastmod dates and reference it in robots.txt.

Learn how to implement →

# robots.txt
Sitemap: https://example.com/sitemap.xml

Spec: https://www.sitemaps.org/

~ agents.json discovery low impact Absent (emerging standard)

Business impact agents.json describes what your site can DO for agents (services, endpoints, capabilities) — an emerging discovery standard. Early adopters get native agent integration.

What we measured We check /agents.json and /.well-known/agents.json for a valid configuration.

How to fix Publish /agents.json describing your site's capabilities and actions.

Learn how to implement →

Spec: https://github.com/wild-card-ai/agents-json

~ WebMCP endpoint low impact Absent (emerging standard)

Business impact WebMCP lets agents call actions on your site directly (book, buy, query) instead of scraping the DOM. Early adopters get native AI-agent interoperability.

What we measured We check /.well-known/webmcp and /webmcp.json for a valid actions array.

How to fix Add a WebMCP endpoint exposing your key actions to agents.

Learn how to implement →

Spec: https://webmcp.org

~ API documentation low impact No OpenAPI/Swagger found

Business impact Programmatic agents prefer a typed API. An OpenAPI/Swagger spec lets them integrate without scraping.

What we measured We probe /openapi.json, /swagger.json, /api-docs and /.well-known/openapi.json.

How to fix Publish an OpenAPI spec at a well-known path.

Learn how to implement →

Spec: https://www.openapis.org/

Passed audits (5)

✓ No CAPTCHA wall✓ No content-blocking cookie wall✓ Machine-readable prices✓ No login wall on public content✓ Server response (TTFB)

Transport & Trust (SEC 1.0.0)

HTTPS, HSTS, CSP, sniffing, referrer and CORS posture. Diagnostic only — this does not affect the CAV score. A security header does not make a page more legible to an agent, so scoring it would reward a CDN toggle that changes nothing an agent can recover. We measure it and say so.

60Transport posture (0–100, unscored)
4pass
0warn
2fail
Per-header findings (6)
HeaderEvidence
✅ HTTPSserved over HTTPS
❌ HSTSno strict-transport-security header
❌ Content-Security-Policyno content-security-policy header
✅ X-Content-Type-Optionsnosniff
✅ Referrer-Policyno-referrer-when-downgrade
✅ CORS exposureaccess-control-allow-origin: *
Full profile — how to improve · unused JS · network · timing

How to improve

highSplit the heaviest unused bundlehighest leverage

vendor.js — 128 KiB transferred, 80.7% unused

EvidenceCDP JS coverage: 103 KiB of this bundle is never executed on load.
Impact~-103 KiB transfer; lower Token Cost + faster agent parse.
Effort30–90 min
FixDynamic-import() the below-the-fold parts of vendor.js, or drop unused dependencies.
mediumCut third-party weight

fontawesome.com — 401 KiB, 21 requests, 28 ms main-thread

EvidenceThird-party is 36.2% of total transfer (24 requests); fontawesome.com is the largest.
ImpactFewer bytes + main-thread stalls before your content settles for an agent.
Effort1–3 h
FixLazy-load, self-host, or remove fontawesome.com; defer non-critical third-party scripts.
mediumBreak up long main-thread tasks

longest task 131 ms (5 total)

EvidenceMain thread blocked 131 ms by the longest task.
ImpactFaster interactivity + content settling.
Effort1–4 h
FixSplit heavy work, defer third-party scripts, move compute off the main thread.

Third-party impact

24 third-party requests · 677 KiB (36.2% of transfer) · 28 ms main-thread — code an agent must also fetch/run before your content settles. Fewer, lazier third-parties = faster, cheaper agent reads.

Third-party domainReqsTransferMain-thread
fontawesome.com21401 KiB28 ms
githubusercontent.com2276 KiB—
plausible.io10 KiB—

Wasted JavaScript (by bundle)

Transfer-accurate — each bundle's transfer size × its unused %, ranked by wasted bytes (the biggest code-splitting wins). Unused JS also inflates Token Cost (TC).

BundleTransferUnusedWasted
https://about.readthedocs.com/theme/js/vendor.js128 KiB80.7%103 KiB
https://about.readthedocs.com/_/static/javascript/readthedocs-addons.js128 KiB44.6%57 KiB
https://about.readthedocs.com/theme/js/site.js5 KiB62.5%3 KiB
https://kit.fontawesome.com/53af4251af.js 3P6 KiB44.5%3 KiB

Network

47Requests
1874 KiBTransferred
4Scripts
36.2%3rd-party
5Long tasks
Font (19)
1033 KiB
Image (13)
345 KiB
Script (4)
267 KiB
Stylesheet (1)
120 KiB
Fetch (5)
94 KiB
Document (1)
8 KiB
Other (1)
4 KiB
XHR (3)
3 KiB
Heaviest requests (30)
URLTypeStatusTransfer
https://avatars.githubusercontent.com/u/3608264?v=4Image200239 KiB
https://about.readthedocs.com/theme/css/fonts/lato-bold-italic.woff2?e48918f9c91871c0ce3eFont200190 KiB
https://about.readthedocs.com/theme/css/fonts/lato-bold.woff2?21b3848a32fce5b0f501Font200181 KiB
https://about.readthedocs.com/theme/css/fonts/lato-heavy.woff2?75f024ce11d1fb961e8cFont200181 KiB
https://about.readthedocs.com/theme/css/fonts/lato-normal.woff2?75614cfcfedd509b1f7aFont200179 KiB
https://about.readthedocs.com/_/static/javascript/readthedocs-addons.jsScript200128 KiB
https://about.readthedocs.com/theme/js/vendor.jsScript200128 KiB
https://about.readthedocs.com/theme/css/site.cssStylesheet200120 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/css/pro.min.css?token=53af4251afFetch20081 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-2.woff2Font20039 KiB
https://avatars.githubusercontent.com/u/1654763?v=4Image20037 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-brands-400-0.woff2Font20037 KiB
https://about.readthedocs.com/images/homepage.pngImage20033 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-7.woff2Font20026 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-6.woff2Font20024 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-5.woff2Font20022 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-24.woff2Font20020 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-3.woff2Font20018 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-2.woff2Font20017 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-28.woff2Font20017 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-1.woff2Font20015 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-19.woff2Font20014 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-16.woff2Font20014 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-0.woff2Font20013 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-duotone-900-14.woff2Font20012 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/webfonts/pro-fa-solid-900-0.woff2Font20012 KiB
https://about.readthedocs.com/images/flask-logo.pngImage2008 KiB
https://about.readthedocs.com/?ref=app.readthedocs.orgDocument2008 KiB
https://ka-p.fontawesome.com/releases/v6.7.2/css/pro-v5-font-face.min.css?token=53af4251afFetch2007 KiB
https://about.readthedocs.com/images/anaconda-logo.svgImage2007 KiB

Long tasks (>50 ms)

StartDuration
1098 ms131 ms
831 ms85 ms
936 ms71 ms
1016 ms58 ms
1321 ms57 ms
Analyzing…
running mobile + desktop · ~30s