What is Chrome UX Report (CrUX) data and how do I read it for my Webflow site?

Why does Google seem to have its own opinion of my site speed?

Google has its own opinion of your site speed because it collects real speed data from real Chrome users, not from a lab test on your laptop. That dataset is the Chrome UX Report, usually called CrUX. It is the field data behind your Core Web Vitals, and it is what Google actually uses when speed touches ranking.

This trips up a lot of founders I work with. Their Webflow site feels fast on their own fast connection, yet Google flags it. The reason is that CrUX reflects everyone who visited, including people on mid range phones and slow networks. Once you understand CrUX, the mystery goes away and you can fix the right things.

What is the Chrome UX Report?

The Chrome UX Report is Google's public dataset of real user performance, gathered from Chrome users who have opted in. It records how actual visitors experienced your pages, then aggregates that into the metrics Google reports. It is called field data because it comes from the field, not a simulator.

CrUX tracks the three Core Web Vitals, which are Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift. It also tracks First Contentful Paint and Time to First Byte. Interaction to Next Paint, or INP, replaced First Input Delay as a Core Web Vital in March 2024, so if you are still chasing the old metric, you are measuring the wrong thing.

How is CrUX different from Lighthouse and PageSpeed Insights lab scores?

CrUX is real user field data, while Lighthouse is a lab test run once in a controlled setting. A Lighthouse score is a simulation on a single device and connection. CrUX is the aggregate of many real visits over time. When the two disagree, Google trusts the field data.

PageSpeed Insights shows you both, which is why it confuses people. The top section pulls CrUX field data for your page and origin. The lower section runs a fresh Lighthouse lab test. I tell clients to treat the lab score as a diagnostic clue and the CrUX numbers as the real report card. I go deeper on this in my post on reading Webflow performance in PageSpeed Insights.

What does the 28-day rolling window mean for me?

The 28-day rolling window means CrUX always reflects the last 28 days of real visits, blended together. It is not last month and it is not today. It is a moving average that updates daily, around 04:00 UTC, and the freshest data is only about two days old.

This has a real consequence for how you judge fixes. If you ship a big performance improvement today, CrUX will not flip overnight. The old, slower experiences stay in the window for weeks and drag the average. I warn clients to expect two to four weeks before a genuine fix fully shows up, so they do not panic and undo good work.

Why does the 75th percentile matter so much?

The 75th percentile matters because Google grades you by your typical bad experience, not your best one. To pass a metric, 75 percent of your real visits must hit the good threshold. That means a quarter of your visitors can struggle and you still pass, but your fast visitors cannot rescue a slow tail.

The good thresholds at that percentile are clear. Largest Contentful Paint should be 2.5 seconds or less. Interaction to Next Paint should be 200 milliseconds or less. Cumulative Layout Shift should be 0.1 or less. If you want a focused plan for the hardest one, I wrote a five step guide on fixing INP under 200 milliseconds in Webflow.

Where can I actually see my CrUX data?

You can see CrUX in four main places, each suited to a different need. PageSpeed Insights is the fastest for a single URL. The Core Web Vitals report in Google Search Console groups your whole site into good, needs improvement, and poor buckets. Those two cover most owners.

For deeper work there is the CrUX API, which returns data by origin and by page and is free within a limit of 150 queries per minute per Google Cloud project. There is also the full historical dataset in BigQuery for anyone who wants trends over many months. Tools like DebugBear sit on top of these to make the data friendlier.

What if my Webflow page has no CrUX data at all?

If your page has no CrUX data, it simply does not have enough real Chrome traffic yet to report. CrUX needs a minimum volume of visits before it will publish numbers for a specific URL. New pages and low traffic sites often show origin level data but not page level data.

When that happens, do not fly blind. Fall back to the Lighthouse lab score for direction, and lean on the origin level CrUX numbers that cover your whole domain. As traffic grows, page level data appears. Until then, fix the obvious things, since the fundamentals of a fast Webflow site rarely change with traffic volume.

Does CrUX cover mobile and desktop separately?

Yes, CrUX reports mobile and desktop as separate form factors, and they often tell very different stories. A site can pass on desktop, where connections and devices are stronger, and fail on mobile, where slower phones and networks are common. Since most traffic for many sites is mobile, the mobile numbers usually matter most.

I always check the mobile view first. It is the harder test and the more honest one. When I read a client's data in PageSpeed Insights or the Search Console Core Web Vitals report, I treat a mobile pass as the real goal and a desktop pass as the easy half. If you only ever look at desktop on your own fast laptop, you are grading yourself on the gentlest possible conditions and missing where real visitors struggle.

How does CrUX connect to Google rankings?

CrUX is the data source behind the page experience signals that feed Google ranking, so it is the version of your speed that actually counts for search. Google has been clear that Core Web Vitals are one factor among many, not a magic lever. But when quality is close between two pages, the faster real world experience can be the tiebreaker.

I never sell Core Web Vitals as a ranking miracle, because that is not honest. What I tell clients is that CrUX reflects a real user experience, and a good experience keeps people on the page and moving toward action. Rankings are a bonus. The main prize is visitors who do not bounce because the page felt slow or jumpy. Fix the experience for humans first, and the search benefit follows quietly.

How should I use CrUX without obsessing over it?

Use CrUX as your monthly scorecard, not your daily mood. Check the Search Console Core Web Vitals report once a month, note which templates fall into needs improvement or poor, and fix those first. Confirm real user impact over the following weeks rather than refreshing scores every hour.

Speed is a means, not the goal. The goal is visitors who stay and act. If your Webflow site is stuck in the poor bucket and you are not sure why, let's chat. I am happy to read your CrUX data with you and turn it into a short, practical fix list. For the metric that trips up most sites, start with my guide to optimizing INP and Core Web Vitals in Webflow.