Google’s Chrome User Experience Report (CrUX) has quietly powered Core Web Vitals and the page experience signal for years. On September 15, 2026, Google published documentation for an experimental set of ad metrics, pushing CrUX beyond load time and responsiveness into advertising load. For performance marketers, D2C teams and publishers, that makes ad density a field-data problem, not just a yield conversation.
What CrUX is adding
CrUX aggregates real Chrome sessions from opted-in desktop and Android users and reports a 28-day rolling window. It already measures Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift at the 75th percentile. The new experimental layer adds four measurements: Ad Count, Ad Density, Ad Weight: CPU and Ad Weight: Network.
Chrome samples the viewport once per second to count visible ad frames and the share of screen they occupy, then totals the processing and network load of ad scripts. The figures appear in the CrUX API, History API and a DevTools panel; BigQuery support is pending. Unlike Core Web Vitals, these ad metrics have no good or poor thresholds.
Why this matters
CrUX feeds Search Console and PageSpeed Insights, and field data informs Google’s page experience ranking factor. If ad code hurts Interaction to Next Paint, the damage appears in the same dataset Google Search uses. That link is measurable: after Google Publisher Tag began yielding during out-of-viewport ad insertion in 2024, mobile INP pass rates for origins using it rose from 55.58% to 66.12%, according to the CrUX team. Work with consent management platforms including OneTrust was also credited with INP gains.
The new metrics change visibility. Chrome already enforces the Better Ads Standards, filtering ads on mobile pages above 30% ad density and unloading heavy ads. What changes is that a site’s ad footprint becomes public and comparable, using a browser owned by a company that also sells advertising.
Action plan for marketers
- Check ads.txt first. Only origins whose ads.txt file names at least one authorized seller are included; a missing or placeholder file excludes you from the data.
- Baseline density and INP together. Use the CrUX API or DevTools panel to compare high ad density with weak responsiveness.
- Audit ad vendors by CPU and network weight. Lazy-load below-the-fold units and test consent management scripts as performance variables.
- Wait for the 28-day window. Field data reflects roughly four weeks of traffic, so give fixes a full cycle before judging them.
Use an ad load budget: set a visible density cap, a script CPU limit and an INP threshold before chasing higher revenue per session. If a new unit lifts density while INP falls, you may be trading organic visibility for short-term yield.
Source: PPC Land
