Sample site report

A publisher’s Site Report, on a sample site

Below is the screen a publisher sees in a Site Report. The site is illustrative and every figure comes from synthetic demo data: this is not a real publisher or real Chrome measurements. A real report shows your own site, on real Chrome UX Report data.

How to use it to improve your site

  1. See where you rank

    Your site’s place in its category and in the market, on phone and desktop separately.

  2. Find what pulls the score down

    Every metric is compared with similar publishers: see which of ad density, ad weight or page experience weighs most on your score.

  3. Follow the effect of a change

    Run the report again after a fix. Chrome data covers the last 28 days, so the effect shows up gradually over about four weeks, not at once.

Synthetic demo data — these are not real Chrome UX Report measurements.

Where city-news.example stands

Among the publishers PubRank tracks in this market, by publisher experience score. The others are not named.

Phone57.7

In News12 of 25 scored sitesTop 48%
In the market166 of 337 scored sitesTop 50%

Desktop57.5

In News13 of 25 scored sitesBottom 52%
In the market176 of 337 scored sitesBottom 49%
How to read this reportWhat the scores and metrics mean

Each publisher is scored on two things people notice when they visit a site: how much advertising gets in their way (ad load) and how fast and stable the page is (page experience). The data comes from the Chrome UX Report — anonymous measurements from real Chrome users over the last 28 days. Hover or tap the i icons in the report for the same explanations.

Scores

0–100, higher is better.

Overall score
The site’s overall score, from 0 to 100. With Phone + Desktop it blends both devices by how much of the site’s Chrome traffic comes from each. Higher is better.
Publisher experience
The combined score on one device, from ad load and page experience. 0–100, higher is better.
Ad load
How heavy the advertising is for visitors compared with similar publishers: how many ads are on screen, how much of the screen they cover, and how much processing and data they use. 0–100; a higher score means a lighter ad load than peers.
Page experience
How fast and stable the page feels to real visitors, based on Google’s Core Web Vitals (LCP, INP, CLS). 0–100, higher is better.
Score colours
Green is 75 or more, amber 50–74, red below 50. The bands are relative to the publishers we compare against; they are not official Google thresholds.

Ad metrics

Measured by Chrome for real visitors. Lower is better.

Ad count
The average number of ads visible on screen at the same time while people scroll the page. Lower is better.
Ad density
The average share of the visible screen covered by ads while people scroll the page. Lower is better.
Ad weight – CPU
The total processor time used by ads during a visit. High values slow the page down and drain phone batteries. Lower is better.
Ad weight – Network
The total data downloaded by ads during a visit. High values slow loading and use mobile data. Lower is better.

Page experience metrics

Lower is better.

Core Web Vitals (CWV)
Google’s three standard measures of page experience — LCP, INP and CLS — each with published “good” and “poor” thresholds.
Largest Contentful Paint (LCP)
How long it takes for the main content of the page to appear. Good: 2.5 s or less. Poor: more than 4 s.
Interaction to Next Paint (INP)
How quickly the page responds when someone taps, clicks or types. Good: 200 ms or less. Poor: more than 500 ms.
Cumulative Layout Shift (CLS)
How much the content jumps around while the page loads, for example when an ad pushes text down. Good: 0.1 or less. Poor: more than 0.25.

Reading the tables

p75
The value that 75% of real Chrome visits over the last 28 days matched or beat. It describes a typical-to-worse visit rather than the best case.
Score
The metric converted to 0–100. Ad metrics: rank among the compared publishers (100 = lightest). Core Web Vitals: position against Google’s thresholds (80 at “good”, 50 at “poor”).
Compared with
Which publishers an ad metric was ranked against: the same category when at least 20 other publishers are available, otherwise all publishers on that device. n is the number compared.
Weekly trend
The p75 value week by week. Ad metrics only have history since Chrome began reporting them. A rising line means the metric is getting worse.
Status
Scored: enough data on every device. Partial: one device or page experience is missing. Insufficient CrUX data: too little real Chrome traffic, or no ads detected. Benchmark too small: not enough comparable publishers yet.
Worsening
At least one ad metric is 20% or more worse than four weeks earlier.
Status
city-news.example
News
57.7
57.757.5Scored

Measured origin https://www.city-news.example · Overall score combines phone and desktop by Chrome traffic share

Phone

Scored
Ad load 40.5
Page experience 83.4
Publisher experience 57.7

Rank News: 12 of 25 scored sitesMarket: 166 of 337 scored sites

Metricp75 Score Compared with Weekly trend
Ad metrics
Ad count 1.8344.0News · n=24
Ad density 27%32.0News · n=24
Ad weight – CPU *1,237 ms42.0News · n=24
Ad weight – Network 1,981 KB50.0News · n=24
Page experience · Core Web Vitals
Largest Contentful Paint 2,227 ms82.2Google thresholds
Interaction to Next Paint 181 ms81.9Google thresholds
Cumulative Layout Shift 0.0786.0Google thresholds

* Experimental CrUX metric; unit not yet verified against the live API.

Desktop

Scored
Ad load 39.5
Page experience 84.5
Publisher experience 57.5

Rank News: 13 of 25 scored sitesMarket: 176 of 337 scored sites

Metricp75 Score Compared with Weekly trend
Ad metrics
Ad count 2.0630.0News · n=24
Ad density 24%48.0News · n=24
Ad weight – CPU *1,058 ms30.0News · n=24
Ad weight – Network 2,002 KB46.0News · n=24
Page experience · Core Web Vitals
Largest Contentful Paint 1,634 ms86.9Google thresholds
Interaction to Next Paint 154 ms84.6Google thresholds
Cumulative Layout Shift 0.0982.0Google thresholds

* Experimental CrUX metric; unit not yet verified against the live API.

This score compares the browser-observed advertising and page experience of publisher environments. Ad load metrics are ranked against comparable publishers on the same device; page experience uses Core Web Vitals thresholds. Scores are relative and based on Chrome UX Report field data (p75, 28-day windows).

It does not measure viewability, invalid traffic, brand safety or campaign performance, and it is not a Google rating. The four ad metrics are experimental in CrUX; their history currently covers only the weeks since Chrome began reporting them.

Look at your own site