vercel.com

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.

 Embed this badge

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

Markdown

[![Core Agent Vitals](https://agentvitals.dev/badge/vercel.com.svg)](https://agentvitals.dev/results?url=https%3A%2F%2Fvercel.com%2F)

HTML

<a href="https://agentvitals.dev/results?url=https%3A%2F%2Fvercel.com%2F"><img src="https://agentvitals.dev/badge/vercel.com.svg" alt="Core Agent Vitals" height="20"></a>

We recovered only a shell of this page (under 200 tokens) — likely a soft bot-block or a client-rendered app that served our scanner almost no content. The metrics below reflect that shell, not your real site; the score is capped until an agent can retrieve real content.

49

Overall score

weighted CAV (0–100)

WARN

0–4950–8990–100

Metrics

100%

CRR Content Recovery Good

0.60

SSD Semantic Signal Density Needs work

115 tok

TC Token Cost Good

33 ms

TTFUT Time to First Useful Token N/A

Token Cost breakdown

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

Content

35.9% · 1,061

Chrome (nav / header / footer)

63.7% · 1,885

Boilerplate (cookie / ad)

0% · 0

Other

0.4% · 11

Final screenshot

Diagnostics

high TC 64.1% of tokens are non-content (boilerplate/chrome)

agent representation — token decomposition

EvidenceToken decomposition: content 35.9%, chrome 63.7%, boilerplate 0%, other 0.4%. Only 35.900000000000006% 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.

medium SSD Low signal-to-noise for agents

content vs chrome/boilerplate

Evidencesignal 0.16 · generic JSON-LD 1/1

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.

Rendered profile: headless

We recovered only a shell of this page (under 200 tokens) — likely a soft bot-block or a client-rendered app that served our scanner almost no content. The metrics below reflect that shell, not your real site; the score is capped until an agent can retrieve real content.

49

Overall score

weighted CAV (0–100)

WARN

0–4950–8990–100

Metrics

100%

CRR Content Recovery Good

0.60

SSD Semantic Signal Density Needs work

115 tok

TC Token Cost Good

65 ms

TTFUT Time to First Useful Token N/A

Token Cost breakdown

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

Content

35.9% · 1,062

Chrome (nav / header / footer)

63.7% · 1,884

Boilerplate (cookie / ad)

0% · 0

Other

0.4% · 11

Final screenshot

Diagnostics

high TC 64.1% of tokens are non-content (boilerplate/chrome)

agent representation — token decomposition

EvidenceToken decomposition: content 35.9%, chrome 63.7%, boilerplate 0%, other 0.4%. Only 35.900000000000006% 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.

medium SSD Low signal-to-noise for agents

content vs chrome/boilerplate

Evidencesignal 0.16 · generic JSON-LD 1/1

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.

Rendered profile: headless

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.