Chrome now publishes four experimental ad metrics in its public user experience data, and DevTools has a new panel to inspect them. If your business website shows ads, the numbers describe how heavy those ads feel to real visitors. If your site shows no ads, you can skip the details and keep your usual speed checks.
Chrome announced the metrics on September 15, 2026. They are experimental, they are not part of Core Web Vitals, and Chrome has not set targets for them. This post explains what they mean and how to run a short check.
What Chrome Added
The Chrome team added four measurements to the Chrome User Experience Report, often called CrUX. This report collects field data from real Chrome users. The new numbers describe websites' ad loads as real users encounter them.
- Ad Count: the average number of ads visible in the viewport.
- Ad Density: the average share of the viewport that ads cover.
- Ad Weight (Network): the data that ads download, measured in bytes.
- Ad Weight (CPU): the processing time ads use, measured in milliseconds.
The data is aggregate. It does not describe any one person, and Chrome says it is not meant for individual targeting.
What the Metrics Do Not Mean
Chrome says plainly that these metrics are not part of Core Web Vitals. They have no suggested thresholds, so there is no pass or fail line. Chrome also says it is open to feedback and may change the metrics or add others.
The announcement does not discuss search ranking. Do not assume a link between these numbers and your search position. Treat them as a diagnostic tool, not a score to chase.
The audience Chrome names is mostly publishers, advertisers and ad services. Many small business sites still carry ads, though. Examples include a local news blog, a community directory, an affiliate section or a banner swap with a partner.
The New DevTools Ads Panel
Chrome 153 and 154 reached stable in September 2026. The DevTools team added an Ads subsection to the Application panel. It gives you a dashboard of the four experimental metrics for the page you are viewing.
The panel also splits CPU and network use by ad elements. It lists the ad scripts running in the main frame. A toggle highlights where ads sit on the page, so you can see them the way a visitor does.
The same release lets you edit cookie flags in the Application panel. That helps when your team tests how a cookie behaves, which can matter for ad scripts.
A Short Check for Sites With Ads
You do not need to be technical to start. Ask your web team or agency to run these steps, or follow them yourself in Chrome.
- Open the page in a fresh Chrome window. Pick your home page and your busiest landing page. Use a private window so extensions do not change the result.
- Open DevTools and find the Ads section. It sits under the Application panel. Note the four values for each page.
- Turn on the highlight toggle. Look at how much of the first screen the ads cover. Ask whether a visitor can find your phone button, form or main message without scrolling past an ad.
- Read the ad script list. Count the scripts and write down who runs each one. Remove any you no longer use.
- Check public field data. The CrUX data is available for sites with enough real traffic. Smaller sites may not have enough visits to appear, so a missing result is normal.
How Ad Load Connects to Speed
Ads are code, and code takes time to download and run. Ad Weight (CPU) shows the processing cost, which can slow how fast a page responds to taps. Ad Weight (Network) shows the download cost, which can slow how fast a page loads on a weak mobile signal.
That link is why the metrics belong in your speed review. Keep checking Core Web Vitals as before. Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift remain the numbers Chrome points to for page experience.
If a slow page also carries heavy ads, the new panel helps you see how much of the cost comes from ads and how much from your own site. You can then decide where to fix first.
Questions to Ask Your Web Team
- Which ad scripts run on our pages, and who approved each one?
- Do ads push our contact details or booking button below the first screen?
- How much CPU time and data do ads add on our top three pages?
- Can we load ads after the main content so visitors see our message first?
- Do ad slots have reserved space, so the layout does not jump while ads load?
What to Do Next
Run the check once now and save the numbers in a simple note. Run it again after any change to your ad setup. Because the metrics are experimental, avoid setting hard goals. Look for large swings and for ads that crowd out your own content.
If you show no ads, make no changes. Spend the time on the basics: fast pages, readable text and a working mobile layout. Chrome says more data should become available over the coming month, so revisit the panel then.
Sources
Want a second pair of eyes on this for your own site? Contact us or schedule a call.
Tags
Frequently Asked Questions
Are the new Chrome ad metrics part of Core Web Vitals?
No. Chrome states the ad metrics are not part of Core Web Vitals and have no suggested targets or thresholds. They are labeled experimental.
Do I need to act if my business site shows no ads?
Probably not. These metrics describe ad load, so a site without ads has little to check. Keep watching your normal speed and responsiveness numbers instead.
Where can I see the ad data for my site?
Chrome added an Ads section to the Application panel in DevTools. It shows the four metrics, lists ad scripts in the main frame, and can highlight ads on the page.
Enjoyed this article?
Share it with your network
