Why Web Vitals Leaderboard Shows "Chrome UX report data not found"

Updated

Web Vitals Leaderboard returns "Oops.. Chrome UX report data not found!" when the URL or origin you entered has no matching record in the Chrome UX Report (CrUX). The tool does not measure your site itself — it only looks up an existing CrUX dataset, so a missing record means CrUX has nothing aggregated for that origin or URL, not that the tool is broken. This usually happens for low-traffic sites, brand-new domains, or URLs that don't match the exact origin CrUX tracks.

What the error actually means

The leaderboard pulls from the Chrome UX Report API, which aggregates real-world experience metrics from Chrome users for sites known to Google's web crawlers. When you add a URL or origin and click View Results, the tool queries that dataset. If no record comes back, it shows the "Chrome UX report data not found!" message instead of a rank table.

So the error is a data-availability problem, not a performance verdict. Your site may be perfectly fast and still produce this message if CrUX has never collected enough data for it.

Why your site may not appear in CrUX

The most common causes, roughly in order of likelihood:

  • Not enough real-world traffic. CrUX only publishes data for origins and URLs with a sufficient volume of Chrome user visits. A site with little traffic won't qualify.
  • The URL or origin doesn't match what CrUX tracks. CrUX aggregates by origin (for example, https://example.com) and by specific URL. Entering a path, a subdomain, or a slightly different hostname can miss the record.
  • The site is new or recently changed. Data is a 28-day rolling average, so a newly launched or recently migrated domain may not have accumulated a full window yet.
  • Google's crawlers don't know the site. CrUX covers destinations known to Google's web crawlers; a site that isn't crawled or indexed won't be represented.
  • The page is private or gated. Pages behind a login or otherwise not publicly reachable by real Chrome users won't generate the aggregated data CrUX needs.

How to check and fix it

  1. Confirm the exact origin. Enter the origin in the form CrUX uses, typically https://example.com with no trailing path. Try the bare origin first, then a specific URL if you need page-level data.
  2. Verify the site has real Chrome traffic. If the domain is new, low-traffic, or internal-only, expect no CrUX record. There is no setting in the tool that can create one.
  3. Re-check after the 28-day window. Because CrUX is a 28-day rolling average, a site that recently crossed the traffic threshold may only appear once enough data accumulates.
  4. Test a known high-traffic origin. Enter a large public site to confirm the tool itself is working. If that returns a rank table, the issue is your site's CrUX coverage, not the leaderboard.
  5. Use the device filter to narrow results. Once a record exists, you can switch between All devices, Mobile, Desktop, and Tablet to see how rankings differ by platform.

What to do if CrUX simply has no data for you

If your site genuinely lacks CrUX coverage, the leaderboard can't rank it — there's no workaround inside the tool. In that case:

  • Use field-data alternatives that don't depend on CrUX volume thresholds, or rely on lab testing for a directional read on speed.
  • Focus on the metric the leaderboard treats as most important: LCP. Based on real website data, top-performing sites render LCP in about 1.2 seconds, which is why LCP drives the ranking.
  • Revisit the leaderboard later once your site has enough public Chrome traffic to enter the dataset.

The key takeaway: "Chrome UX report data not found" means CrUX has no aggregated record for the origin or URL you entered. Fix the input if it's a mismatch, or accept that the site needs more real-world Chrome traffic before it can be ranked.