Google has started publishing data on the advertising load of websites for both media buyers and site owners. On September 15, the company added four experimental ad experience metrics to the Chrome User Experience Report, the field dataset known as CrUX, according to Search Engine Journal, Digiday and Search Engine Roundtable.
The four measurements are Ad Count, Ad Density, Ad Weight: CPU and Ad Weight: Network. Per Chrome's announcement, cited across the three reports, Ad Count tracks how many distinct ad frames a user sees in the viewport on average while scrolling. Ad Density captures what share of that visible area the ad frames take up. The two weight metrics tally the computing load and the network traffic that ad scripts and assets generate over a session, expressed in milliseconds and bytes respectively.
CrUX is built from real browsing sessions of Chrome users who have opted into anonymous measurement, Search Engine Journal notes, spanning Android, ChromeOS, Linux, macOS and Windows but not Chrome on iOS. It is the same dataset that feeds the Core Web Vitals field numbers in PageSpeed Insights. The ad figures are queryable now through the CrUX API and CrUX History API, and visible in Chrome DevTools; Search Engine Roundtable adds that sites carrying third-party ads can already be checked in CrUX Vis, though the data was not populating for every site it tried. A BigQuery dataset is planned for later, which would allow analysis at scale.
Digiday, which put follow-up questions to Google, reported the most detail on mechanics. Chrome classifies advertising through a mix of network-level filtering and analysis of script execution, so a URL matching its ad filter list counts, as do frames spawned by scripts already tagged as ad-related. The browser samples the visible viewport once per second to compute count and density, while CPU and network consumption accumulate over the whole session. CrUX then reports the 75th percentile. Aggregate reporting only covers sites whose ads.txt file lists at least one authorized seller, single-page applications can accumulate measurements across soft navigations, and local DevTools readings may not match the aggregated numbers.
Google is treating all four signals as experimental. They are not part of Core Web Vitals, and there are no recommended thresholds separating an acceptable ad load from an excessive one, per Digiday.
Advertisers have already shown interest. Bill Reardon, general manager for enterprise platform at Google Ads, said in the launch materials that "Display & Video 360 supports this initiative to bring transparency to page layout quality," adding that Google wants to explore with the industry how the signals can support advertiser goals. Google told Digiday that independent ad platforms will receive the data at the same time as Google's advertising businesses, while the remedies ruling in its ad tech antitrust case remains pending. Google did not disclose whether DV360 is testing the signals for inventory evaluation, bidding or reporting.
Search consultant Glenn Gabe wrote on X, "Every site owner running ads (especially a lot of ads) should run this TODAY." Google's Barry Pollard and Alex Cone described the metrics as transparency tools for web advertisers and the services placing their ads, according to Search Engine Roundtable.
The metrics could affect how brands and media buyers value inventory. Digiday places the launch against falling site visits from AI Overviews and changing page-view economics. A standardized Chrome measure of advertising load gives buyers another way to compare placements and publishers a common measure for their inventory. Search Engine Journal also raised the unconfirmed possibility that ad experience could eventually influence ranking systems. Sites seeking citations from AI answer engines while carrying dense advertising can now measure that load publicly. Publishers can use CrUX Vis to establish their own baseline before buyers begin using the same data.