Google has added four ad-load measurements to the Chrome User Experience Report, the public dataset behind Core Web Vitals. Starting September 15, the dataset now reports how many ads appear on a page, how much of the viewport they cover, and how much network and processor capacity they consume.
What Chrome is measuring
CrUX does not collect new telemetry for these signals. It reuses data Chrome already gathers, sampling the viewport once per second and reporting the 75th percentile. That means the figures describe a bad-but-not-worst-case visit, not an average one.
- Ad count: the average number of ads visible in the viewport.
- Ad density: the average share of the viewport occupied by ads.
- Ad weight (network): network usage in bytes.
- Ad weight (CPU): processor usage in milliseconds.
Chrome identifies advertising through network-level filtering and script execution analysis, matching resource requests against Google’s ad filter list. The data is available through the CrUX API, CrUX History API, and CrUX Vis.
A big caveat publishers need to watch
Aggregate reporting is limited to sites with an ads.txt file that names at least one authorised seller. So the picture is really a measure of ad load across the programmatically monetised web, not all websites. It excludes direct-sold inventory, subscription sites, and pages without third-party ads.
Google has set no benchmarks and says there are no plans to set them. The metrics are experimental and sit outside Core Web Vitals. That creates a familiar market dynamic: a buyer or DSP may eventually pick a threshold and start filtering inventory above it, turning an open measurement into a de facto standard without anyone formally proposing it.
Why this matters for marketing teams
Barry Pollard, who works on web performance at Google, said the release “provide[s] transparency into sites’ ad experiences.” Alex Cone, group product manager at Chrome, said early conversations “indicate an appetite for ad experience metrics,” but no demand-side or supply-side platform has publicly committed to using them yet.
For publishers, this is a signal to audit ad experience before buyers do. For media buyers, it offers a public layer to evaluate inventory quality beyond viewability and click metrics. Bill Reardon, general manager of enterprise platform at Google Ads, said Display and Video 360 supports the initiative and will explore how the signals can “improve quality and support advertiser goals.”
A practical response
Pull your data. Use the CrUX API to check top landing pages, especially mobile, where ad weight hits performance harder. Watch the buy side. Monitor DSP and SSP announcements. The first platform to adopt a cutoff will effectively set the standard. Test before overcorrecting. If your density looks high, reduce the most costly units first. The goal is to improve experience without crashing revenue from programmatic demand.
The release also lands while generative search surfaces are reducing publisher traffic. A better ad-load metric does not fix shrinking visits; it raises the pressure on sites earning less per visitor. That makes early measurement and layout discipline more valuable, not less.
Source: PPC Land
