Real field data from the Chrome UX Report (CrUX): p75 for LCP, INP, CLS, FCP and TTFB. Compare your site against competitors — by origin or specific pages.
The tool shows how fast sites are for real Chrome users and puts them side by side in one table. Use it to compare your site with competitors from the search results or to find page types with the worst metrics. You can also track the effect of speed work, but the data covers 28 days, so changes show up gradually.
Enter addresses in the “Sites or pages (one per line, up to 20)” field. You can skip the protocol, because the tool adds https:// itself. Duplicate addresses are checked once, and anything after the 20th unique address is ignored.
Then follow these steps:
At the Origin scope, only the protocol and domain are kept from each address, while at the URL scope only the part after # is dropped. Note that example.com and www.example.com are different origins for CrUX.
Each number in the table is the 75th percentile (p75): in 75% of page loads the metric was this value or better. The cell colour depends on the thresholds Google sets for each metric. Between the “good” and “poor” zones lies the yellow “needs improvement” zone.
The thresholds are as follows, with the “good” limit inclusive:
In the table, times of 1000 ms or more are shown in seconds, and CLS is rounded to two decimal places.
The CWV column shows “Pass” when LCP, INP and CLS are all in the green zone. If any of these metrics is yellow or red, it shows “Fail”, and if one of them has no data, “n/a”. FCP and TTFB do not affect this status, because they are not Core Web Vitals.
The dates under the table show the collection period. It covers 28 days and moves forward daily. In the cwv-compare.csv file, values are not rounded: times are in milliseconds and CLS is a decimal number. For addresses without data, the error text goes into the CWV column.
The data comes from Google's Chrome UX Report (CrUX) API. Your browser sends the address and device type to /api/crux, a proxy server on marko-f.com. The proxy adds the API key and forwards the request to Google, so you don't need your own key. It limits the number of simultaneous requests, so if some rows come back with an error, run the check again a little later.
The “No CrUX data” message means Google has no record for that address. CrUX only includes public pages and origins with enough visits, which is why a single page often has no data while the whole site does. The tool does not run lab tests like Lighthouse and does not show history, only the current p75 values for 28 days.
The thresholds and the percentile come from web.dev. The CrUX rules are documented on Chrome for Developers.