Google Chrome has turned ad load into public field data. On September 15, Chrome added four experimental measurements to the Chrome User Experience Report: Ad Count, Ad Density, Ad Weight: Network and Ad Weight: CPU. Together they show how many ad elements are in view, how much of the screen they occupy, and how many bytes and CPU milliseconds they consume.
What Chrome just added
- Ad Count: average distinct ad elements visible per second, sampled across a page visit.
- Ad Density: average share of the viewport covered by ads, reported as a percentage.
- Ad Weight: Network: kilobytes transferred for ad scripts, images and stylesheets.
- Ad Weight: CPU: milliseconds of JavaScript CPU time spent inside ad frames, excluding main-frame ad scripts.
Chrome publishes the 75th percentile for eligible URLs and origins, the same aggregation logic it uses for Core Web Vitals.
Why it matters
These numbers describe rather than grade. Chrome is explicit: the ad metrics are not part of Core Web Vitals and have no suggested targets. That is useful because buyers and publishers can now compare real-user ad load without relying only on vendor scores or one-off audits.
Eligibility is narrower than ordinary CrUX. Pages need at least one authorized seller in ads.txt to be included. Sites that sell only direct deals without a declared seller will not show data. For now access runs through the CrUX API, CrUX History API and the Ad panel in Chrome DevTools, with BigQuery access planned as coverage expands.
PPC Land quotes Sara Badler, Chief Advertising Officer North America at The Guardian, calling the release a great step forward and pointing to the metrics as a clear, objective ground truth for publisher experience.
The context you need
Chrome already enforces the Coalition for Better Ads mobile density line above 30%, and its Heavy Ad Intervention can unload resource-hungry ads. The new CrUX fields are not another rule. They are a population-level view of what real Chrome sessions encounter.
PPC Land’s early CrUX readings illustrate the gap: at the 75th percentile, its mobile Ad Density held around 22% while network weight rose to about 2,010 KB, even as Core Web Vitals stayed good. A site can look clean on experience signals while still carrying a heavy ad payload.
What to do now
For advertisers, check density and weight before committing budget. A density figure is harder to game than a viewability metric, but origin-level p75 can still hide page-level variance. Use it alongside MFA and fraud controls rather than as a standalone score.
For publishers, audit top landing pages. Remember the CPU metric excludes main-frame ad scripts, so it undercounts full monetization overhead. Do not treat it as total page cost.
A simple frame: separate screen share from resource cost. One large unit can raise Ad Density without moving Ad Count; several small units can do the opposite. Network and CPU weight tell you whether the ad stack is hurting performance. You need all three.
Source: PPC Land
