Enter LCP, INP and CLS to get Googleโs Good / Needs Improvement / Poor rating instantly. Uses Googleโs current official thresholds (INP since March 2024).
LCP โ Largest Contentful Paint
Time for the largest content element to render (seconds)
Good
s
0sGood โค2.5sโค4sPoor >4s6s+
INP โ Interaction to Next Paint
Input responsiveness in ms โ replaced FID in March 2024
๐ก Enter values in the Desktop tab too to compare both devices side by side.
๐ก Improvement Tips
All three metrics pass Googleโs thresholds. Keep it that way.
Re-check with PageSpeed Insights after each release to catch regressions.
Watch real-user data in the Search Console Core Web Vitals report.
๐ How to read your results
Where do the numbers come from? Use the โDiscover what your real users are experiencingโ (field data) section at the top of PageSpeed Insights, or the Core Web Vitals report in Search Console. Google uses the 75th-percentile value of 28 days of real visits, not the Lighthouse lab score below it.
LCP (Largest Contentful Paint) โ Good at 2.5 s or less, Poor above 4 s. Usually a large hero image or web font on the first screen. Add fetchpriority="high" to the hero image, serve WebP or AVIF, and if TTFB is above 0.8 s fix caching or add a CDN first.
INP (Interaction to Next Paint) โ Good at 200 ms or less, Poor above 500 ms. Long JavaScript tasks after a click or tap are the cause. Break up long tasks (scheduler.yield or setTimeout) and defer heavy third-party scripts such as chat widgets, ads and tag managers.
CLS (Cumulative Layout Shift) โ Good at 0.1 or less, Poor above 0.25. Images, ads and embeds without reserved space push content around. Set width and height or aspect-ratio, and reserve space for late banners and cookie notices.
What to fix first? Any Poor metric first; otherwise the Needs Improvement metric on your highest-traffic templates (product or article pages). A page only passes when all three metrics are Good.
Core Web Vitals are three metrics Google uses to measure real usersโ page experience, and they are used as one of the page experience signals in Google Search. LCP (Largest Contentful Paint) is the time until the largest element on the first screen renders, INP (Interaction to Next Paint) is how long the page takes to respond after a click, tap or key press, and CLS (Cumulative Layout Shift) measures how much content jumps around while you read. INP replaced FID in March 2024, so the current set is LCP, INP and CLS. Enter the values from PageSpeed Insights or Search Console and this checker rates each one with Googleโs official thresholds as Good, Needs Improvement or Poor, tells you how many of the three pass, and shows fix-it tips only for the metrics that are not Good โ Poor ones first. For example, LCP 2.51 s, INP 201 ms and CLS 0.101 are each just over the Good threshold, so all three are rated Needs Improvement and the screen shows exactly those numbers. You can rate mobile and desktop separately and compare them side by side, and the values you enter are stored in the page address so one link shares the same result. Everything is calculated in your browser.
Common Use Cases
๐
SEO Audit
Paste the field-data values from the top of PageSpeed Insights to see how many of the three metrics pass and which Poor metric to fix first before anything else.
๐ฑ
Mobile vs Desktop
Mobile LCP is often far slower than desktop on the same page. Enter both in their own tabs and the checker rates them side by side so you know which device to work on first.
๐ ๏ธ
Before / After Comparison
Enter values before and after optimizing images or trimming scripts to see whether the rating changed, then paste the share link with the values into your changelog or team report.
๐
Client Reporting
Agencies and freelancers can show a client each metricโs Good, Needs Improvement or Poor rating and the โ2 of 3 passedโ summary at a glance, without explaining raw percentiles.
How to Use
1
Get your values
Run your URL in PageSpeed Insights (pagespeed.web.dev) and note LCP (seconds), INP (milliseconds) and CLS from the โDiscover what your real users are experiencingโ section, or use the Search Console report.
2
Pick a device and enter them
Choose the Mobile or Desktop tab, then drag the sliders or type the numbers. An LCP pasted in milliseconds such as 2500ms is converted to 2.50 s automatically, and negative values are blocked.
3
Read the ratings
Each metric gets a Good, Needs Improvement or Poor badge and the overall card shows how many of the three passed. Empty fields are not rated; they show โEnter a valueโ instead.
4
Fix and share
Tips appear only for metrics that are not Good, Poor ones first. The values live in the page address, so the share button or a copied link opens the same result for your team.
Frequently Asked Questions
A. Google replaced FID (First Input Delay) with INP (Interaction to Next Paint) in March 2024. FID only measured the delay before the very first interaction, while INP looks at the responsiveness of all clicks, taps and key presses during a visit. Good is 200 ms or less and Poor is above 500 ms.
A. Yes. Google treats a page as passing Core Web Vitals only when LCP, INP and CLS are all Good, which is why the overall card shows how many of the three passed. Keep in mind that Core Web Vitals are just one of Googleโs page experience signals; relevance and content quality matter far more for rankings.
A. Use the field data at the top of PageSpeed Insights (pagespeed.web.dev) or the Core Web Vitals report in Google Search Console, which show the 75th percentile of 28 days of real visits. The Lighthouse lab numbers further down are only a guide, and INP needs real interactions so it does not appear in lab tests.
A. The 0โ100 performance score is calculated by Lighthouse from a single lab run, whereas the Core Web Vitals assessment comes from real visitorsโ LCP, INP and CLS. A page can score above 90 and still be rated Needs Improvement if real-user LCP is over 2.5 seconds, so enter field-data values here.
A. Enter both. Google collects mobile and desktop data separately, and most sites look worse on mobile. Put each set in its own tab at the top of the checker and a comparison table appears so you can decide which device to improve first.