Is this site fast for real users?

Enter a URL to see the Core Web Vitals Google collects from real Chrome users, on phone and desktop, with a short trend. A Lighthouse lab test shows where the time goes. The lab test can take up to 40 seconds.

LCP · INP · CLS
plus FCP and TTFB
28 days
of real Chrome users
€0
free, no email gate

What the check tests

Field data from the Chrome UX Report, the same source Google uses for Search Console's Core Web Vitals report, plus one PageSpeed Insights lab run.

  1. 01

    Largest Contentful Paint (LCP)

    How long until the main content (usually the hero image or headline) is visible. Good is 2.5 s or less for 75% of visits.

  2. 02

    Interaction to Next Paint (INP)

    How fast the page reacts when someone taps or clicks. Good is 200 ms or less. Heavy JavaScript and third-party tags are the usual culprits.

  3. 03

    Cumulative Layout Shift (CLS)

    How much the layout jumps while loading: images without dimensions, late banners, web fonts. Good is 0.1 or less.

  4. 04

    FCP and TTFB

    First Contentful Paint and Time to First Byte aren't Core Web Vitals, but they show whether a slow LCP starts at the server or in the browser.

  5. 05

    Phone vs desktop

    Real-user numbers for both device types. Most sites pass on desktop and fail on phones, and Google's mobile-first index looks at the phone.

  6. 06

    Trend

    The last few 28-day windows for phones, so you can see whether things got better or worse after a relaunch, a new theme or a new tag.

  7. 07

    Lab test

    A Lighthouse run on a simulated mid-range phone, with the biggest opportunities it found. Good for debugging, not what Google ranks on.

Questions

What is the difference between field data and lab data?

Field data comes from real Chrome users who visited the site over the last 28 days (the Chrome UX Report). Lab data is one simulated page load on a throttled phone. Google uses field data for its page experience signals. The lab test is there to find causes, and its score moves around from run to run.

Why does it say “not enough real-user data”?

Chrome only publishes numbers for pages and sites with enough eligible traffic. Smaller sites often have no data for a single URL; the check then falls back to the whole site (origin). If there is no origin data either, you only get the lab test. That is normal, not an error.

Do Core Web Vitals affect rankings?

They are part of Google's page experience signals, and Google describes them as one factor among many. Relevance and content quality matter more. Passing won't rescue a weak page, but failing badly on phones costs you users before it costs you rankings.

My lab score is 95 but Core Web Vitals fail. How?

The lab test loads one page once, with an empty cache and no logged-in state, cookie banner clicks or real devices. Real users bring slow phones, bad networks, consent tools and interactions. INP in particular can only be measured with real users; the lab has no clicks.

What is the 75th percentile?

Google judges each metric by the value that 75% of visits beat. So a “good” LCP means at least three out of four visits saw the main content within 2.5 seconds.

Slow site, and nobody can say why?

I trace slow Core Web Vitals to the cause, whether that's the theme, a tag manager, images or the host, and write down the fixes in the order they pay off. Planning a relaunch? Then speed goes into the migration plan from day one.