Free tool
See the LCP, INP and CLS that real Chrome users experienced on any site over the last 28 days — the same field data Google uses when it judges page experience. No account, no queue, no Lighthouse run to wait for.
Three metrics decide whether Google considers your page experience good. Here is what each one measures and what actually moves it.
Core Web Vitals are the three user-experience metrics Google treats as a ranking signal: Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. A page passes when the 75th percentile of real visits is in the good range for all three — so you are judged by your slower users, not your average one.
LCP is how long it takes for the biggest thing in the viewport — usually a hero image, video poster or headline block — to finish rendering. Good is 2.5s or less. The usual culprits are a slow server response, render-blocking CSS or JavaScript, and hero images that are neither preloaded nor properly sized.
INP measures how long the page takes to visually respond to a click, tap or key press, across the whole visit — not just the first one. Good is 200ms or less. Long JavaScript tasks are the usual cause: heavy hydration, third-party tags, and event handlers that do layout work synchronously.
CLS adds up how much visible content jumps around without the user causing it. Good is 0.1 or less. Images and iframes without width and height, ads and embeds injected above existing content, and web fonts that swap to different metrics are what shift a layout.
FID was replaced by INP in March 2024. FID only measured the delay before the first interaction started processing, which almost every site passed. INP measures the full interaction latency across the whole session, so pages that felt sluggish now score like it.
This tool shows field data: what actual Chrome users on actual devices and networks experienced. Lighthouse and PageSpeed Insights' performance score are lab data — one simulated run on one simulated device. Lab data is reproducible and good for debugging; field data is what Google ranks on. You want both, and you want them to agree.
The Chrome UX Report (CrUX) aggregates anonymised measurements from Chrome users who opted into usage statistics reporting. It publishes a 28-day rolling window per URL and per origin. If a specific page has too little traffic, CrUX has no entry for it and we show the origin-level result instead.
A missing CrUX entry does not mean your site is slow — it means too few Chrome users visited it for Google to publish an aggregate. Newer or lower-traffic sites are in this bucket constantly. Real user monitoring on your own site is how you measure vitals before CrUX has enough of a sample.
Every Core Web Vitals checker, this one included, gives you a number for today. None of them tell you that last Thursday's deploy added 900ms to LCP. PingView runs the checks on a schedule, keeps the history, and alerts you the moment a metric crosses a threshold.
Inspect a certificate, its chain and expiry date, plus a domain reputation snapshot.
Translate an uptime percentage into the downtime it actually allows per day, month and year.
Estimate what an hour of downtime costs your business, in your own numbers.
Continuous vitals tracking with history, thresholds and regression alerts.
Scheduled lab audits for performance, accessibility, SEO and best practices.
The rest of PingView's free toolkit for uptime, certificates and performance.
Yes, completely. There is no account, no rate-limited trial and no email wall. You can also share a result by copying the URL from your address bar.
The Chrome UX Report (CrUX), Google's public dataset of real Chrome user measurements. It is the same field data that appears in PageSpeed Insights and in Search Console's Core Web Vitals report.
The field data should match, because it is the same dataset. PageSpeed Insights also shows a lab performance score from a simulated Lighthouse run, which is a different measurement and will not match field numbers.
CrUX only publishes an entry once a URL or origin has enough real Chrome traffic. Below that threshold Google publishes nothing. Lower-traffic sites need lab tests or their own real user monitoring instead.
A URL result covers that one page. An origin result aggregates every page on the domain. We check the exact URL first and fall back to the origin when the page itself has too little traffic — the result header tells you which one you're looking at.
CrUX publishes a 28-day rolling window and refreshes daily. Because it is an average over four weeks, a change you ship today takes weeks to fully appear — which is exactly why continuous monitoring catches regressions that this checker cannot.
Almost always, and mobile is usually worse. Google evaluates page experience per device type, so check both. Use the toggle above to switch.
It is one of many ranking signals, and it matters most as a tie-breaker between pages of comparable relevance. Failing vitals will not rescue thin content, but among close competitors, being the fast one is worth having.