Social Rocket
Google has published new experimental ad metrics in the Chrome User Experience Report (CrUX) on 15 September 2026. Publishers, advertisers, and adtech providers can now publicly compare, for the first time, how heavily ads burden real Chrome users on a website – not just by count, but also by visible area, CPU load, and network usage.
The data is available via CrUX Vis, the CrUX API, the CrUX History API, and Chrome DevTools. Google also stresses that the new signals are still experimental, are not part of the Core Web Vitals, and currently have no official thresholds for "good" or "poor."
The four ad metrics Google is introducing
CrUX measures four dimensions of the ad experience:
- Ad Count: the average number of visible ads in the viewport,
- Ad Density: the share of the visible area that ads occupy during a session,
- Ad Weight: CPU: the cumulative compute time generated by ads and their associated scripts,
- Ad Weight: Network: the network data transferred by ads and their resources.
Field values are based on real Chrome sessions and are reported as the 75th percentile (p75) over rolling 28-day periods. The aim is to surface a typically worse user experience without single extreme cases dominating the metric.
How Chrome detects an ad at all
Chrome combines several signals for detection. Among other things, the browser checks requests against a filter list derived from EasyList and analyses whether resources or frames were generated by scripts already recognised as ad-related.
If an iframe is classified as an ad, that classification persists for the frame. DevTools also lets you directly inspect which frames and network requests Chrome has recognised as ad-related.
Additional conditions apply to the aggregated CrUX values: Google only considers websites that list at least one authorised seller in an ads.txt file. Local measurements in the DevTools ad panel can therefore differ from the published CrUX data.
Why the metrics matter for media buyers and publishers
Until now, the quality of an ad environment could often only be assessed indirectly, through viewability, load times, fraud signals, or in-house UX measurements. CrUX now makes part of the actual ad load in the browser publicly comparable.
This can have several practical applications:
- Publishers can check whether additional placements significantly increase ad density or CPU load.
- Media buyers can compare different domains in terms of ad density and technical load.
- Adtech teams can monitor changes via the API and detect regressions automatically.
- Product teams can track the ad experience and technical performance together.
Google itself explicitly names CrUX Vis as a dashboard for non-technical stakeholders and the APIs for automated monitoring.
If you want to place these measures within a broader KPI framework, see our guide to social media goals and KPIs 2026. That missing shared standards are a budget problem in other ad channels too is shown by our article on creator marketing measurement and the new IAB standards.
Not a new ranking factor and not an official quality score
It is important not to over-interpret the launch. Google is currently assigning no categories such as "Good," "Needs Improvement," or "Poor" to the new ad metrics. The values are also explicitly not part of the Core Web Vitals.
Digiday further reports that independent ad platforms are set to gain access to the data at the same time as Google's own advertising systems. According to the report, Google has not disclosed whether Display & Video 360 already uses the signals for bidding, inventory valuation, or reporting.
For media buyers, CrUX is therefore initially primarily a transparency and comparison signal, not a finished quality score for inventory.
Why the topic goes beyond display advertising
The release fits a broader trend: marketing platforms are increasingly making finer-grained measurement data available directly within the product. Google, for example, now also shows AI visibility in Merchant Center, while other ecosystems try to trace advertising effects back to offline or retail data.
The difference with CrUX is that the data comes directly from the browser and describes how advertising technically and visually reaches the user. That makes it interesting for publishers, advertisers, and independent measurement providers alike.