Core Web Vitals Checker
Measure LCP, CLS, INP, TBT and FCP using Google PageSpeed/Lighthouse data when available, plus real-user field data when Google exposes it. Results can vary by run, device and test conditions. Free, no login.
Get more from the Core Web Vitals Checker
How it works
- 1PASTE
Enter a URL
Choose mobile or desktop and paste the page to test.
- 2TEST
Run Google Lighthouse
Get LCP, INP, CLS, TBT and FCP plus real-user field data when Google has it.
- 3FIX
Fix each failed audit
Every failed audit comes with a one-line, specific fix.
Core Web Vitals Checker: everything you need to know
It calls the Google PageSpeed Insights API directly from your browser — the same Lighthouse engine and the same numbers as pagespeed.web.dev and Hostinger’s speed test. You get lab metrics, real-user CrUX field data where available, and every failed audit sorted worst-first with a plain-language fix. If Google’s shared no-key quota is momentarily exhausted, the tool retries through 5 routes and then automatically runs a built-in static speed audit of the same failure causes, so you always get actionable results — and you can save a free Google API key once (stored only in your browser) for guaranteed full Lighthouse reports.
- Enter a URL and pick mobile or desktop — mobile is what Google ranks with.
- Wait 20–30 seconds while Lighthouse loads and measures the page.
- Read the vitals — green thresholds are Google’s official “good” bands.
- Work the failed-audits list top to bottom — each one names exactly what to change.
- Re-run after fixing — lab scores update instantly; field data follows in ~28 days.
Google’s official thresholds: LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 — measured at the 75th percentile of real users. In the lab, also aim for TBT under 200 ms and FCP under 1.8 seconds. The table below shows all three bands for every metric.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | ≤ 2.5 s | 2.5–4 s | > 4 s |
| INP (Interaction to Next Paint) | ≤ 200 ms | 200–500 ms | > 500 ms |
| CLS (Cumulative Layout Shift) | ≤ 0.1 | 0.1–0.25 | > 0.25 |
| FCP (First Contentful Paint) | ≤ 1.8 s | 1.8–3 s | > 3 s |
| TBT (Total Blocking Time) | ≤ 200 ms | 200–600 ms | > 600 ms |
Run a free core web vitals test on any page in about thirty seconds — this is a Google Core Web Vitals checker in the literal sense, because it calls Google's own PageSpeed Insights engine and reports the same LCP, INP and CLS numbers, plus real-user field data. Bookmark it as your core web vitals check online: no login, no quota games, and every failed audit comes with a specific fix.
What a Core Web Vitals check tells you
Searches for a website Core Web Vitals checker all want the same three numbers — LCP (loading), CLS (visual stability) and INP (responsiveness) — because those are the field metrics Google actually uses. This core web vitals checker reports all three for any URL, so you know exactly which one is holding your page back before you start optimizing.
Test Core Web Vitals online for free
Run a free Core Web Vitals test online: this Core Web Vitals checker measures LCP, INP and CLS using Google PageSpeed/Lighthouse data, and shows real-user field data when Google has it for your URL. Use it as a website Core Web Vitals checker before and after each change — results vary between runs, so check a few times and compare the trend.
Compare field data with a lab test
Start with the mobile run. When real-user field data is available, use it to understand what visitors experienced. Use the Lighthouse run to find likely causes and check whether an individual fix improves the tested page. Investigate layout shifts.
Core Web Vitals: questions people search, answered
People search for a core web vitals test, a Core Web Vitals tester, a core web vitals checker online or simply “check core web vitals” when Google Search Console shows a failed assessment. Below: what the three metrics mean, how to test them free, how to read the report and how to fix a failed Core Web Vitals assessment.
What are Core Web Vitals?
Core Web Vitals are three Google metrics that measure real page experience: Largest Contentful Paint (LCP) for loading speed, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. A page passes when at least 75% of visits are “good” on all three.
| Metric | Good | Needs improvement | Poor |
|---|---|---|---|
| LCP | ≤ 2.5 s | 2.5–4 s | > 4 s |
| INP | ≤ 200 ms | 200–500 ms | > 500 ms |
| CLS | ≤ 0.1 | 0.1–0.25 | > 0.25 |
How to check Core Web Vitals of a website: step by step
Paste the URL above
Choose mobile first — Google ranks with the mobile version.
Run the free test
The checker calls Google PageSpeed Insights and returns lab and field data.
Read field data first
Real-user (CrUX) data decides the pass/fail; lab data helps you debug.
Open each failed audit
Every failed audit comes with a one-line fix.
Fix, deploy and re-test
Field data updates over a 28-day window, so expect gradual change.
Core Web Vitals test vs Search Console report
| This online checker | Search Console Core Web Vitals report | |
|---|---|---|
| Scope | One URL at a time, instantly | Groups of similar URLs across your site |
| Data | Lab test + field data when available | Field data only (last 28 days) |
| Access | Any public URL, no login | Only sites you own |
| Use it for | Debugging and before/after checks | Monitoring the whole site |
- Use both: test and fix pages here, then watch the site-wide status in Search Console
Core Web Vitals assessment failed: how to fix it
LCP too slow
Cause: A large hero image, slow server or render-blocking CSS/JS.
- Compress and resize the hero image; serve WebP/AVIF.
- Preload the LCP image and avoid lazy-loading it.
- Use a CDN and caching to cut server response time.
INP too high
Cause: Heavy JavaScript blocks the main thread when people tap or type.
- Remove unused scripts and third-party widgets.
- Split long tasks; defer non-critical JS.
- Check the Animation Performance Checker for heavy effects.
CLS too high
Cause: Images, ads, fonts or banners load without reserved space.
- Set width and height on every image and embed.
- Reserve space for ads and cookie banners.
- Find each shifting element with the Layout Shift Finder.
Core Web Vitals tools
- This Core Web Vitals checker — free online test for any URL with fixes
- Google PageSpeed Insights — Google’s official lab + field report
- Search Console Core Web Vitals report — site-wide field data for verified owners
- Chrome DevTools Performance panel — deep debugging for developers
- Layout Shift Finder — finds the exact elements behind CLS
What a Core Web Vitals audit includes
A core web vitals audit is wider than a single “is it fast?” test. Search Console groups URLs into Good, Needs improvement, or Poor for three field metrics. This checker explains those three and where each one usually breaks, so the audit has a sequence instead of a colour.
| Metric | What the visitor feels | A common cause this audit looks for |
|---|---|---|
| LCP | The largest block on screen arrives late | Hero image without dimensions, or a font that blocks first paint |
| INP | A tap does nothing for a moment | A long task on click: a heavy menu script, a third-party widget |
| CLS | The page jumps after it looked finished | An ad, image, or webfont with no reserved space. A jumping title is a CLS bug, not an SEO title problem. See the CLS checker. |
Field data (what Chrome users experienced over 28 days) is what Search Console uses. A lab run on your laptop can look fine on a fast connection and still fail the field report on mobile. Use this page to name the metric, then confirm the URL group in Search Console before you rewrite a template. An audit of one homepage does not clear a template that also renders 200 article URLs. Fix the template, then check one URL from each template.
Method. The page explains the thresholds Google publishes for LCP, INP and CLS and maps them to causes you can see in the page. It does not replace the Chrome User Experience Report and it does not invent a field score when no public data exists.
How this tool handles your data
- Public page fetch. To read a public web page, your browser requests it directly or through a public relay (a CORS proxy) because browsers cannot read other sites on their own. Only the URL you enter is sent; the analysis itself happens in your browser.
- Google PageSpeed Insights. Speed, Lighthouse and Core Web Vitals checks send the URL you enter to Google’s PageSpeed Insights API. Google’s own privacy policy applies to that request.
- No account, no tracking of your input. The tool is free with no login. Anonymous usage statistics (Google Analytics) and ads may use cookies only as described in our Privacy & Cookie Policy.