Developing
Public data on how heavy a site's ads are is now available for any site in CrUX.
In 60 seconds
- On September 15, 2026 Google added four ad metrics to CrUX: Ad Count, Ad Density, Ad Weight (network, in bytes) and Ad Weight (CPU, in milliseconds).
- They are available through the CrUX API, the History API and CrUX Vis for sites with third-party ads.
- Google called them experimental measurements that give transparency into ad experiences.
- Google did not make them ranking factors or add them to Core Web Vitals.
Impact Layer
- What changed
- Anyone can now query how many ads, how much screen and how many resources a site's ads use.
- Why it matters
- It makes ad load public and comparable, which publishers, advertisers and ad platforms may use in their own decisions, even if Google ranking does not.
- Who is affected
- Publishers who run ads, ad operations teams and SEO consultants.
- Martech stack area
- Analytics, SEO & Search
- Stack impact
- Check your own numbers before a competitor or buyer does, and note that definitions for native ads and house ads are unclear.
- Business impact
- Low The metrics are experimental, coverage was incomplete at launch and no thresholds exist.
- What to watch
- Whether Google publishes benchmarks, adds the metrics to PageSpeed Insights, or changes its page experience guidance.
On September 15, 2026, Google added four ad-related metrics to the Chrome User Experience Report (CrUX), according to Relevant Audience.
The four metrics
- Ad Count: the average number of ads visible in the viewport.
- Ad Density: the fraction of the viewport that ads occupy.
- Ad Weight (network): ad resource use in bytes.
- Ad Weight (CPU): ad resource use in milliseconds.
The data is available through the CrUX API, the CrUX History API and CrUX Vis for sites with third-party ads, and is public for any site. Barry Pollard of Google called them “experimental measurements that provide transparency into sites’ ad experiences.”
What they are not
Google did not call them ranking factors or add them to Core Web Vitals, published no benchmarks for a “good” value, and noted that definitions are unclear for native ads, sponsored content and house ads. Coverage was incomplete at launch, and some sites returned no data. A summary of Google’s page experience documentation says Core Web Vitals are used by ranking systems and that other page experience aspects do not directly help a site rank.
Our read
This is a transparency feature, not a rule. Its practical effect is that anybody, including advertisers and rivals, can now look up how ad-heavy a page is. Publishers should look at their own values and compare them with similar sites. Do not treat them as an SEO target until Google says they matter for rankings.
Sources
- Relevant Audience: Google adds ad metrics to the Chrome User Experience Report (opens in a new tab)
Source of the metric definitions, access points, Google staff quotations and caveats.
- Search Engine Roundtable: Google page experience document adds CrUX ad metrics (opens in a new tab)
Context on the page experience documentation. Not read directly; cited by the search summary used.