Honest performance measurement: separating real telemetry from your own dev traffic, and turning budgets into tests.
A performance dashboard is only as good as the data behind it. This one measures two different things and refuses to mix them: field telemetry from real visitors, and lab measurements taken from a production build.
Core Web Vitals at the 75th percentile, from visitors at the analytics consent tier. Scored against Google's published bands, so the verdict matches what Search Console reports.
Every number above reads the production lane only. This is the split it was filtered from — shown rather than hidden, because an aggregate that quietly drops rows looks identical to one with nothing to drop.
Production traffic is 97.2% of collected samples. If that share moves sharply, the filter is the first thing to check — not the site.
Bundle size never shows up in real-user data until it has already shipped. These come from a production build, committed to the repository so growth is visible in review.
route_js_kb Poorbaseline_js_kb Needs workdoc_html_kb GoodMeasured 2026-10-24 · NODE_ENV=production
Think this pattern could be better? Tell us how.
Leave feedback