What is a Core Web Vitals checker?
Core Web Vitals are three measurements Google uses to describe how a page feels to a visitor: how fast the main content appears (LCP), how quickly the page reacts to a tap or click (INP), and how much the layout jumps around while loading (CLS). Most people who search for a core web vitals checker want to know one thing: do my numbers pass?
This page answers that part. It is a scoring and guidance tool, not a speed test. It never loads your site. You run a real test elsewhere, for example in Google's Core Web Vitals documentation and linked tools, then type the three results into the boxes. Each box has its own colour meter and a Good, Needs Improvement or Poor label.
Below the scores you get fix suggestions for any metric that is not Good, plus a checklist of 14 common optimisations you can tick off as you work. The thresholds built in are LCP 2.5 seconds, INP 200 milliseconds and CLS 0.1 for Good, and 4 seconds, 500 milliseconds and 0.25 as the upper edge of Needs Improvement. Anything beyond that is Poor.
How to check your Core Web Vitals scores here
- Run your page through PageSpeed Insights or open the Core Web Vitals report in Google Search Console and note the LCP, INP and CLS values.
- Type LCP in seconds into the first box (for example 2.1), INP in milliseconds into the second (for example 180) and CLS as a plain number into the third (for example 0.08).
- Watch each meter update. It turns green, amber or red and shows the label under the box, such as 2.1s with a Good tick.
- Read the overall verdict box. It only says Passing when all three numbers are entered and all three are Good. Leave one blank and a good set still shows Needs Improvement.
- Open the Fix Recommendations list that appears for any metric outside the Good range and pick the items that match your page.
- Scroll to the CWV Self-Assessment Checklist and tick each optimisation you have already done. The counter shows progress out of 14.
- Fix what you can, re-test in your measuring tool, and enter the new numbers to confirm the change.
What this Core Web Vitals checker includes
Three live scoring boxes
LCP, INP and CLS each have an input, a coloured meter and a Good, Needs Improvement or Poor label that update as you type. Meters are scaled to 6 seconds, 700 milliseconds and 0.4.
Overall pass or fail verdict
A single box summarises the result: Passing, Needs Improvement or Failing. Any Poor metric makes the verdict Failing.
Targeted fix lists
Only the metrics that miss the Good range produce suggestions, such as preloading the LCP image, deferring third-party scripts or adding width and height to images.
14-point self-assessment checklist
Five LCP items, four INP items and five CLS items cover things like next-gen image formats, long main-thread tasks and reserved ad space. A progress bar tracks completion.
Threshold badges on every card
Each metric card prints its three ranges so you can see where your number sits without looking anything up.
Links to real measuring tools
Cards point to PageSpeed Insights, the Search Console Core Web Vitals report, WebPageTest and Lighthouse, since those are what produce the numbers you need.
Who uses it, and for what
- Freelancer writing an audit. You have PageSpeed Insights numbers for a client's homepage and need a quick, readable verdict. Enter them, screenshot the result and attach the matching fix list to your report.
- Store owner checking a product page. Your LCP is 3.4 seconds because of a large banner image. The tool marks it Needs Improvement and points you to image format, preload and server response time.
- Developer after a deploy. You added a chat widget and INP jumped from 150 to 320 milliseconds. Entering both values shows the move from Good to Needs Improvement and why third-party scripts are the first suspect.
- Student learning the metrics. Try different values and watch the labels change. It is a fast way to learn where the Good, Needs Improvement and Poor lines sit for each metric.
- Content team doing a monthly review. Use the checklist as a shared to-do for the team, then record the 14-point score next to the measured numbers. Pair it with a link audit for the rest of the monthly review.
Tips for reading your results
- Prefer field data over lab data. Google judges pages on real visitor data, so the numbers from Search Console or the field section of PageSpeed Insights matter more than a single lab run.
- Test mobile first. Mobile devices are slower and usually give worse numbers, so a page that passes on desktop can still fail for most visitors.
- Enter all three metrics before trusting the verdict. A set of two good values with the third blank will not show Passing.
- Fix the worst metric first. One Poor value drags the verdict down more than two small misses in the amber range.
- Re-test after each change, not after ten. Several edits at once make it hard to know which one helped. If a change involves redirects, confirm them with the Redirect Checker too, since extra hops slow loading.
- Do not treat the checklist as a score of your site (page titles are a separate job: see the SERP Preview Tool). Ticking all 14 boxes does not guarantee a pass, because your measured numbers decide that.
Is it safe? Privacy and limits
Everything you type stays in your browser. The scoring and checklist run in JavaScript on the page, and nothing is sent to a server or saved when you close or refresh it. The tool does not load your URL or measure your site, so it cannot confirm that the numbers you enter are real. The links to PageSpeed Insights, Search Console, WebPageTest and Lighthouse open those external services in a new tab. Passing here does not guarantee any ranking result.
Core Web Vitals FAQ
It turns three numbers you already have into a clear verdict. You enter LCP in seconds, INP in milliseconds and CLS as a unitless score. The tool compares each one with Google's published thresholds, colours a meter, writes a Good, Needs Improvement or Poor label and shows an overall result. It then lists fixes for anything that missed. It does not test your website, so you need a measurement from PageSpeed Insights, Search Console or a similar source first. Think of it as a reader and explainer for those results.
For a Good rating, LCP must be 2.5 seconds or less, INP 200 milliseconds or less and CLS 0.1 or less. This tool treats LCP up to 4 seconds, INP up to 500 milliseconds and CLS up to 0.25 as Needs Improvement, and anything above that as Poor. Google assesses these at the 75th percentile of real visits, so at least three out of four page loads need to meet the Good level. A fast median is not enough if a slow quarter of visitors drags the figure down.
The easiest source is PageSpeed Insights: paste your URL and look at the field data section, which shows real-user figures when enough traffic exists. Google Search Console has a Core Web Vitals report that groups your pages by status across the whole site. WebPageTest and the Lighthouse panel in Chrome DevTools give lab results from a single simulated run. Lab numbers are fine for debugging, but they can differ from field data, so say which one you entered when you share a result.
Because at least one of the three boxes is empty. The Passing verdict only appears when LCP, INP and CLS are all filled in and all three land in the Good range. If you enter two Good values and leave the third blank, the tool cannot confirm a pass, so it falls back to Needs Improvement. Fill in the missing metric and the verdict updates straight away. If you truly do not have a value, treat the result as incomplete rather than failed.
Interaction to Next Paint, or INP, replaced First Input Delay as a Core Web Vital in March 2024. It looks at how long the page takes to respond across all interactions in a visit rather than only the first one. This tool scores INP, LCP and CLS. It does not score First Contentful Paint or Time to First Byte, although TTFB shows up as an item in the LCP checklist because a slow server delays everything else.
They are one signal among many. Google says page experience is something its ranking systems consider, but relevance and content quality still carry far more weight. A slow page with the best answer can outrank a fast page with a weak one. The practical case for fixing these numbers is just as strong from the visitor side: slower loading and shifting layouts make people leave. Treat a pass as a worthwhile goal, not as a ranking switch. Google's own documentation on this is linked from the intro above.
Start with the largest element above the fold, which is usually a hero image or a headline block. Compress that image, serve it as WebP or AVIF, give it explicit width and height, and preload it. Then check server response time, because a slow first byte delays everything that follows. Remove CSS and scripts that block rendering in the head. Do not lazy-load the LCP image, since that delays it. The Fix Recommendations list shows these same steps when your LCP is outside the Good range.
No to both. The 14 checkboxes are a personal to-do list. They count how many items you have ticked and fill a progress bar, but they do not feed into the pass or fail verdict, which depends only on the three numbers you typed. The ticks are not stored, so reloading the page clears them. If you want a record, copy your results into your own notes or audit document before leaving.
Not directly. It scores one set of three numbers at a time, so it works as a page-level check. For a site-wide view, use the Core Web Vitals report in Google Search Console, which groups URLs with similar problems and shows trends from real user data. You can then take the numbers for a representative page into this tool to see the explanation and fix list. If you are also tidying up page metadata, the Meta Tag Analyzer covers that side of on-page checks.