www.newegg.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.newegg.com)
<a href="https://agentvitals.dev/results?url=https%3A%2F%2Fwww.newegg.com"><img src="https://agentvitals.dev/badge/newegg.com.svg" alt="Core Agent Vitals" height="20"></a>
An agent is likely to fabricate missing details rather than say “I don’t know”. 2/7 applicable facts come from machine-readable structured data.
Metrics
Token Cost breakdown
Where the page's tokens go (≈169,471 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 (≈19,233 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.
content vs chrome/boilerplate
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
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 (6)
✗ 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).
User-agent: GPTBot
Allow: /
Disallow: /admin/~ No content-blocking cookie wall medium impact Consent platform: optanon (verify it doesn't block content)
Business impact A consent wall that hides content until a click is invisible to agents — they cannot click 'Accept'.
What we measured We fingerprint OneTrust, Cookiebot, Usercentrics and similar managers and flag content-blocking ones.
How to fix Use an overlay banner that leaves content in the DOM, not a blocking interstitial.
Spec: https://gdpr.eu/cookies/
✗ 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.
# robots.txt
Sitemap: https://example.com/sitemap.xml~ 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.
~ 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.
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.
Passed audits (6)
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 | max-age=31536000; includeSubDomains |
| ✅ Content-Security-Policy | policy present, script-src does not allow inline |
| ❌ 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.