Skip to content
Performance

Chrome Now Measures Ads on Your Site: Four New CrUX Metrics and What They Mean for Performance

3 min read

On September 15, 2026, Google added four new metrics to the Chrome User Experience Report (CrUX) that measure the ad load of web pages using real-user data for the first time. They are not another Core Web Vitals entry and not a ranking factor, yet they deserve attention from anyone who shows ads on a site or is responsible for them.

The four new metrics

CrUX now publishes the following:

  • Ad Count – the average number of ads in the viewport.
  • Ad Density – the average fraction of the viewport area occupied by ads.
  • Ad Weight (Network) – resources consumed by ads, measured in bytes.
  • Ad Weight (CPU) – resources consumed by ads, measured in milliseconds.

The count and density pair describes how much space ads take up in front of the user’s eyes. The weight pair shows how much data and processor time ads cost. The second part matters more for performance, because heavy ad scripts are a common cause of slow pages.

Where to find them

The metrics are available through the CrUX API and the CrUX History API, and for sites with third-party ads you can view them in CrUX Vis. All four are currently labeled experimental.

What they are not

It is important not to overreact. The new metrics are not part of Core Web Vitals, and Google has not set recommended thresholds for them yet. According to the sources we used, they are not currently used as a ranking factor. Google still presents them as transparency for the ad ecosystem, mainly useful to advertisers and the services that place ads.

Why this concerns you

Even if your site has no banners, the principle is the same: third-party scripts cost performance. A typical ad-supported site might have:

  • ads that load above the fold and push content around (hurting CLS),
  • ad scripts that block the main thread and worsen responsiveness (INP),
  • pages that download hundreds of extra kilobytes just for a few banners.

The new metrics give you an objective number instead of a feeling that “ads slow the site down”. If you run a site with ads or affiliate banners, try CrUX Vis and see where you stand. It will be useful once thresholds are set.

What you can do right now

  • Measure a baseline. Record today’s values so you can track the effect of changes.
  • Reduce the number of ad slots and avoid placing them above the fold where they get in the way of content.
  • Reserve space for ads with a fixed container height so the page does not jump.
  • Lazy-load ads only when they approach the viewport.
  • Vet your vendors. Ask how their scripts affect CPU and data transfer.

Conclusion

Chrome now shows what ads on a page really cost. For now it is an experiment without thresholds and without any effect on search rankings, but the direction is clear: ad load is becoming measurable. Want to know what third parties cost your site? Get in touch with FullNet Servis, we are happy to run a performance audit.

Potřebujete pomoc s webovým projektem?

Rádi vám pomůžeme. Konzultace je zdarma a nezávazná.

Poraďte se s námi
Let's collaborate

Tell us about your project

Describe your project and we'll get back to you.

50+ satisfied companies
We reply within 24h
Free consultation
Bc. Martin Procházka
founder & developer
Please enter your name.
Please enter a valid email address.
Please enter a valid phone number.
Please describe what you need.
You must agree to the processing of personal data.