On September 15, Chrome introduced four experimental advertising fields in the Chrome User Experience Report, usually called CrUX. They describe the ad load that eligible pages delivered to real Chrome users:
- Ad Count: the average number of ads visible in the viewport
- Ad Density: the average share of the viewport occupied by ads
- Ad Weight, Network: bytes used by advertising resources
- Ad Weight, CPU: processing time used by advertising resources
This is field data about the page around an ad. It is not a score for the ad, the audience or the lead that came from it.
Read the number at the right level
Chrome reports the new fields for a whole-site origin, such as https://example.com, as well as for individual page URLs on eligible sites. Its methodology says the published value is the 75th percentile, or p75. In plain English, 75% of the measured sessions had that value or better, while 25% had a heavier experience.
Coverage has another important limit. Chrome includes the fields only for sites with at least one authorized seller listed in ads.txt, on top of the usual CrUX eligibility rules. A blank result can mean the page or origin is outside the dataset. It does not mean the page had no ads.
Count and density come from viewport samples taken once per second. Network and CPU weight build across the session. That makes all four useful descriptions, but they answer different questions. A page can show a small number of large ads, many small ads or lightweight ads that stay on screen for a long time.
There is no pass mark
Chrome labels every field experimental. The release says they are not part of Core Web Vitals and gives no recommended target or threshold.
It also does not announce that Google Ads uses these fields for bidding, ranking inventory or judging campaign results. Chrome says advertisers and ad services may find them useful when valuing opportunities. That is a proposed use, not outcome proof.
So avoid turning one value into a red or green label. A higher density can prompt a closer look. It cannot tell you whether the right person noticed the ad, clicked it or became a qualified lead.
Start with the placements that already matter
This release is most useful when you buy ads across publisher pages or display inventory. It is much less direct for a service business running only Search ads, where the click starts on Google’s results page rather than a publisher placement.
For a placement review, begin with pages or origins that already account for meaningful spend. Record:
- The exact page or origin and the date checked
- Which of the four CrUX fields are available
- The placement’s spend, clicks and conversion data for the same review window
- The downstream result you care about, such as a qualified inquiry or booked appointment
Keep missing data as missing. Do not replace it with a guess or with a local DevTools reading that looks similar.
Then ask whether the browser signal and the business result point in the same direction. A heavy page with weak qualified-lead results deserves a closer placement review. A heavy page with strong results needs a more careful decision. The CrUX field alone does not settle either case.
Put the page signal beside the lead record
The placement report tells you where the spend went. CrUX can add context about the page environment. The CRM tells you what arrived after the click.
In Glory’s paid advertising and CRM work, those records belong together. A placement decision should show the media cost, the page context and the lead quality it produced. That gives the person moving budget something stronger than a page score with no business outcome attached.
Chrome’s new fields are a useful reason to inspect ad environments with better evidence. For now, treat them as a screening signal: check coverage, keep the four measures separate and require campaign and CRM data before you act. Chrome may add guidance as the experiment develops. Until then, the metrics tell you how heavy the page was, not whether the campaign worked.
Source note: Metric definitions, coverage and methodology come from Chrome for Developers. The fields are experimental, have no suggested thresholds and are not Core Web Vitals. Glory wrote the placement-review method.