www.linear.app

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/linear.app.svg)](https://agentvitals.dev/results?url=https%3A%2F%2Fwww.linear.app)

HTML

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

67

Overall score

weighted CAV (0–100)

WARN

0–4950–8990–100

Metrics

90%

CRR Content Recovery Needs work

0.55

SSD Semantic Signal Density Needs work

2,192 tok

TC Token Cost Good

347 ms

TTFUT Time to First Useful Token N/A

Token Cost breakdown

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

Content

91.5% · 5,410

Chrome (nav / header / footer)

8.3% · 492

Boilerplate (cookie / ad)

0% · 0

Other

0.2% · 10

Final screenshot

Diagnostics

medium CRR Content is hidden behind JavaScript

pre-JS raw HTML

Evidence10% of content requires JS · 90% 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 SSD Low signal-to-noise for agents

content vs chrome/boilerplate

Evidencesignal 0.91 (full) · 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.

Rendered profile: headless

67

Overall score

weighted CAV (0–100)

WARN

0–4950–8990–100

Metrics

90%

CRR Content Recovery Needs work

0.55

SSD Semantic Signal Density Needs work

2,195 tok

TC Token Cost Good

256 ms

TTFUT Time to First Useful Token N/A

Token Cost breakdown

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

Content

91.5% · 5,413

Chrome (nav / header / footer)

8.3% · 492

Boilerplate (cookie / ad)

0% · 0

Other

0.2% · 10

Final screenshot

Diagnostics

medium CRR Content is hidden behind JavaScript

pre-JS raw HTML

Evidence10% of content requires JS · 90% 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 SSD Low signal-to-noise for agents

content vs chrome/boilerplate

Evidencesignal 0.91 (full) · 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.

Rendered profile: headless

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

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.