Core Web Vitals checker
Enter a site or a page. You see how fast it was for real Chrome visitors over the last 28 days, on phones and on desktops, whether it passes Google’s Core Web Vitals, and how that changed over 25 weeks.
Google shows 28-day averages, Chrome only. Want today’s numbers, iPhones included?
We’re planning real-visitor monitoring for PingWise: your site’s speed as your own visitors get it, next to what our 20 probes see, so you know whether it’s the server, the network or the page. Leave your email and get one email when it opens.
Get an email the moment this site goes down.
Downtime confirmed from 20 locations before you are told, plus SSL and domain expiry warnings.
What are Core Web Vitals?
Three measurements Google takes from real visits to judge how a page feels: how soon the main content shows, how quickly the page reacts, and whether it jumps around while loading. Google uses them as one of its ranking signals. A page passes when all three are «good» for at least 75% of visits.
Largest Contentful Paint
When the biggest thing on screen, usually the main image or headline, has shown. Good: within 2.5 seconds. Poor: over 4 seconds.
Interaction to Next Paint
How long the page takes to react to a tap, click or key press. Good: within 200 ms. Poor: over 500 ms.
Cumulative Layout Shift
How much the content moves while the page loads, for example when an ad pushes the text down. Good: 0.1 or less. Poor: over 0.25.
FCP and TTFB
First Contentful Paint (anything on screen) and Time to First Byte (the server’s first answer). Not part of the pass mark, but they explain a slow LCP.
Google’s own real-visitor data.
We don’t load the page ourselves. We ask the Chrome UX Report, Google’s public record of how pages performed for real Chrome users, for the page you entered and for its whole site. These are the same figures Google Search Console and PageSpeed Insights show as «field data».
Rolling window
Every figure covers the last 28 days and is updated daily, about two days behind.
75th percentile
The value that 75% of visits were within. It’s the number Google judges, because averages hide the slow visits.
Chrome only
Chrome on Android and desktop. iPhones and Firefox are not in Google’s data at all.
Trend
The weekly 75th percentile for phones over about six months, so you see whether a change helped.
Why does it say «No Google data» for my site?
Google publishes these figures only for pages and sites with enough Chrome visitors who share usage statistics. Most small and medium sites aren’t included. It says nothing about how fast your site is.
Why are these numbers different from Lighthouse or PageSpeed’s score?
Lighthouse loads the page once, on one simulated device: that’s lab data. This tool shows field data: what happened on real visitors’ phones and computers, on their own networks. Google ranks on the field data.
I fixed my page. Why hasn’t the result changed?
Each figure is a 28-day rolling window, so an improvement shows gradually and is fully visible about four weeks later.
Why are phones and desktops shown separately?
They usually differ a lot: phones have slower processors and networks. Google also judges them separately.
Are iPhone visitors included?
No. Google’s data comes from Chrome on Android and desktop only. Every browser on an iPhone is left out, which for many European sites is a large share of visitors.
Do you store what I check?
We keep your IP address and the time for one hour, only to limit how often you can check. The address you enter goes to Google’s Chrome UX Report service to get the figures; Google handles it under its own privacy policy and does not receive your IP address. Google’s answer stays in our server’s memory for up to an hour and is not saved. Details: Privacy Policy, section 2.8.
Related: the TTFB checker measures your server’s first answer from 20 locations right now, and website monitoring keeps checking it.