⚡ LCP · CLS · INP

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.

Core Web Vitals CheckerYour tool. Connected workflows.
Free tool guide

Get more from the Core Web Vitals Checker

By the SocialKit.tools team · Reviewed 4 November 2026 · 100% free, no sign-up

3 quick steps

How it works

  1. 1
    PASTE

    Enter a URL

    Choose mobile or desktop and paste the page to test.

  2. 2
    TEST

    Run Google Lighthouse

    Get LCP, INP, CLS, TBT and FCP plus real-user field data when Google has it.

  3. 3
    FIX

    Fix each failed audit

    Every failed audit comes with a one-line, specific fix.

The complete guide

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.

  1. Enter a URL and pick mobile or desktop — mobile is what Google ranks with.
  2. Wait 20–30 seconds while Lighthouse loads and measures the page.
  3. Read the vitals — green thresholds are Google’s official “good” bands.
  4. Work the failed-audits list top to bottom — each one names exactly what to change.
  5. 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.

MetricGoodNeeds improvementPoor
LCP (Largest Contentful Paint)≤ 2.5 s2.5–4 s> 4 s
INP (Interaction to Next Paint)≤ 200 ms200–500 ms> 500 ms
CLS (Cumulative Layout Shift)≤ 0.10.1–0.25> 0.25
FCP (First Contentful Paint)≤ 1.8 s1.8–3 s> 3 s
TBT (Total Blocking Time)≤ 200 ms200–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.

People also search

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.

MetricGoodNeeds improvementPoor
LCP≤ 2.5 s2.5–4 s> 4 s
INP≤ 200 ms200–500 ms> 500 ms
CLS≤ 0.10.1–0.25> 0.25

How to check Core Web Vitals of a website: step by step

  1. Paste the URL above

    Choose mobile first — Google ranks with the mobile version.

  2. Run the free test

    The checker calls Google PageSpeed Insights and returns lab and field data.

  3. Read field data first

    Real-user (CrUX) data decides the pass/fail; lab data helps you debug.

  4. Open each failed audit

    Every failed audit comes with a one-line fix.

  5. 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 checkerSearch Console Core Web Vitals report
ScopeOne URL at a time, instantlyGroups of similar URLs across your site
DataLab test + field data when availableField data only (last 28 days)
AccessAny public URL, no loginOnly sites you own
Use it forDebugging and before/after checksMonitoring 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.

  1. Compress and resize the hero image; serve WebP/AVIF.
  2. Preload the LCP image and avoid lazy-loading it.
  3. 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.

  1. Remove unused scripts and third-party widgets.
  2. Split long tasks; defer non-critical JS.
  3. Check the Animation Performance Checker for heavy effects.

CLS too high

Cause: Images, ads, fonts or banners load without reserved space.

  1. Set width and height on every image and embed.
  2. Reserve space for ads and cookie banners.
  3. 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
Also searched as

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.

MetricWhat the visitor feelsA common cause this audit looks for
LCPThe largest block on screen arrives lateHero image without dimensions, or a font that blocks first paint
INPA tap does nothing for a momentA long task on click: a heavy menu script, a third-party widget
CLSThe page jumps after it looked finishedAn 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.

Privacy

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.
Answers

Frequently asked questions

It uses Google PageSpeed/Lighthouse data when the endpoint responds, but scores are not guaranteed to match another run exactly. Lighthouse results can vary with device emulation, network conditions, server response and test timing.
Lab data is a fresh Lighthouse run on an emulated device — instant and repeatable. Field data (CrUX) is the 75th percentile of real Chrome users over the last 28 days — it’s what actually affects your Google ranking, and it appears only for sites with enough traffic.
Mobile Lighthouse simulates a mid-range phone on a slow 4G connection, so the same page takes longer to load and any main-thread work hurts more. Google ranks with mobile, so optimise for it first.
Follow the failed-audits list in the report — it’s sorted worst-first. Typically render-blocking CSS/fonts (hurts LCP), unreserved space for images or injected content (hurts CLS), and heavy third-party JavaScript (hurts INP/TBT).
CrUX field data is a rolling 28-day window, refreshed daily. After you ship fixes, lab scores improve immediately but field data takes up to a month to fully reflect the change.
Yes, completely free with no login. The check runs from your browser straight to Google’s public API — nothing is stored on our side.
Enter your URL — the checker runs Google Lighthouse plus real-user CrUX data and reports LCP, CLS, INP, TBT and FCP with a one-line fix per failed metric.
Yes, as part of Google’s page experience signals, but relevance and content quality matter more. Passing Core Web Vitals will not rescue a weak page, yet failing them can hold back a page that competes closely with others.
Yes. This Core Web Vitals free check has no login, no daily cap and no paid tier. It requests Google’s PageSpeed Insights data for the URL you enter, so the LCP, INP and CLS values are the same field and lab numbers Google reports.
In a web core vitals test, aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real visits. A page passes only when all three are in the good range.
Late-loading web fonts, banners and images without set dimensions push the heading and content down, which counts as layout shift. Reserve space with width and height attributes, preload the main font and avoid inserting bars above existing content. The Layout Shift Finder shows which elements move.