cam.ac.uk

Report from 7/20/2026, 1:30:45 PM https://cam.ac.uk
Latest run · lab, cold cache
75
7/20/2026
28-day score · p75 · the standard
5/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/cam.ac.uk.svg)](https://agentvitals.dev/results?url=https%3A%2F%2Fcam.ac.uk)
<a href="https://agentvitals.dev/results?url=https%3A%2F%2Fcam.ac.uk"><img src="https://agentvitals.dev/badge/cam.ac.uk.svg" alt="Core Agent Vitals" height="20"></a>
What AI tells your customers about youAgent confidence: LOW
🟡Business nameUniversity of Cambridge · 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
🟡DescriptionThe University of Cambridge is one of the world’s leading universities, with a rich history of radical thinking dating back to 1209. · 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.

75
Overall score
weighted CAV (0–100)
PASS
0–4950–8990–100

Metrics

100%
CRR Content Recovery Good
0.96
SSD Semantic Signal Density Good
489 tok
TC Token Cost Good
28 ms
TTFUT Time to First Useful Token N/A

Token Cost breakdown

Where the page's tokens go (≈3,240 across regions). Most tokens are real content — the agent isn't paying much for chrome.

Content
90.7% · 2,940
Chrome (nav / header / footer)
9.3% · 300
Boilerplate (cookie / ad)
0% · 0
Other
0% · 0

Final screenshot

Final screenshot of https://cam.ac.uk

Diagnostics

No issues found — this page is well-prepared for agents.

Rendered profile: headless

Agent Discoverability 88/100 · Agent Ready

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) Major AI bots allowed Learn →
sitemap.xml Found at /sitemap.xml Learn →
JSON-LD structured data Types: CollegeOrUniversity Learn →
~ agents.json Absent (emerging standard) Learn →
~ WebMCP endpoint Absent (emerging standard) Learn →
~ OpenAPI / API docs No OpenAPI/Swagger found Learn →

Issues (4)

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

~ 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 (8)

✓ robots.txt allows AI bots✓ No CAPTCHA wall✓ No content-blocking cookie wall✓ Machine-readable prices✓ No login wall on public content✓ Structured data (JSON-LD)✓ XML sitemap present + fresh✓ 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.

84Transport posture (0–100, unscored)
4pass
1warn
0fail
Per-header findings (6)
HeaderEvidence
✅ HTTPSserved over HTTPS
⚠️ HSTSmax-age=2592000 is below the 180-day baseline
✅ Content-Security-Policypolicy present, script-src does not allow inline
✅ X-Content-Type-Optionsnosniff
✅ Referrer-Policystrict-origin-when-cross-origin
➖ CORS exposureno CORS headers on the document (normal for an HTML page)
Full profile — how to improve · unused JS · network · timing

A deeper scan (a second render, ~30–60s): network waterfall, unused JavaScript, long tasks, and prioritized fixes. Runs only when you ask; the result is cached so it never re-runs.

Analyzing…
running mobile + desktop · ~30s