Waymark / Routes / developer.chrome.com Track Core Web Vitals trends over time using the CrUX History API
domain: developer.chrome.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Call the CrUX History API endpoint with the same origin/url/formFactor/metric parameters as the standard CrUX API Retrieve up to roughly 40 weekly data points covering about 6 months of history Remember each weekly point is itself a 28-day trailing aggregate, so adjacent points overlap and smooth changes rather than showing daily swings Compute week-over-week percentile deltas to detect regressions after a deploy Reuse the same Google Cloud API key and quota as the standard CrUX API Known gotchas Because collection periods overlap (28-day windows advanced weekly), a single bad day is diluted across several data points, delaying visible signal History is capped at roughly 40 weeks; you cannot query further back for multi-year trends this way Sparse-traffic origins or pages can have gaps or missing weeks in the series
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp