www.engadget.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.
[](https://agentvitals.dev/results?url=https%3A%2F%2Fwww.engadget.com)
<a href="https://agentvitals.dev/results?url=https%3A%2F%2Fwww.engadget.com"><img src="https://agentvitals.dev/badge/engadget.com.svg" alt="Core Agent Vitals" height="20"></a>
An agent gets the basics but will guess on the gaps. 4/7 applicable facts come from machine-readable structured data.
Metrics
Token Cost breakdown
Where the page's tokens go (≈22,305 across regions). Most tokens are real content — the agent isn't paying much for chrome.
Final screenshot
Diagnostics
pre-JS raw HTML
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.
agent representation (Chrome/markdown output)
Fix: Trim boilerplate, collapse repeated structures, and drop decorative markup from agent-visible content so an agent spends fewer tokens to read the page.
Rendered profile: headless
Metrics
Token Cost breakdown
Where the page's tokens go (≈15,709 across regions). Most tokens are real content — the agent isn't paying much for chrome.
Final screenshot
Diagnostics
pre-JS raw HTML
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.
Rendered profile: headless
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
Issues (1)
~ llms.txt present + valid high impact Found at /llms.txt but missing H1/blockquote
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.
# Your Site
> One-line description for AI agents.
## Key pages
- /products — catalog
- /pricing — plans
- /docs — documentationSpec: https://llmstxt.org
Passed audits (11)
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.
Per-header findings (6)
| Header | Evidence |
|---|---|
| ✅ HTTPS | served over HTTPS |
| ❌ HSTS | no strict-transport-security header |
| ❌ Content-Security-Policy | no content-security-policy header |
| ❌ X-Content-Type-Options | missing nosniff |
| ⚠️ Referrer-Policy | no referrer-policy header (browser default applies) |
| ➖ CORS exposure | no CORS headers on the document (normal for an HTML page) |
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.