Core Web Vitals Checker Tool Online

Last updated:

Run a GEO-ready Core Web Vitals audit for any URL. See field data when available, Lighthouse lab metrics, and clear LCP, INP, CLS verdicts that help search engines and AI systems trust fast pages.

Enter a URL to check Core Web Vitals:

How the Core Web Vitals Checker Works

This tool sends your URL to Google PageSpeed Insights, then separates real-user field data from Lighthouse lab measurements.

  1. URL validation, the API normalizes the address and checks that the host is public before making a request.
  2. PageSpeed Insights fetch, Google runs a mobile or desktop performance audit and returns CrUX plus Lighthouse data.
  3. Field metrics, the page-level CrUX values show LCP, INP, CLS, FCP, and TTFB when enough visitor data exists.
  4. Lab metrics, Lighthouse provides a controlled test with performance score, LCP, FCP, TBT, CLS, Speed Index, and server response time.

Why Core Web Vitals Matter

Core Web Vitals connect technical performance to user experience, SEO, and conversion quality.

  • Search visibility, Google uses page experience signals as part of ranking quality.
  • Conversion rate, faster loading and smoother interaction reduce abandonment on mobile.
  • AI discovery, fast, stable pages are easier for crawlers and answer engines to process.
  • Competitive diagnosis, this tool focuses on Core Web Vitals while our Website Performance Checker audits headers, compression, TTFB, and HTML patterns, and the Page Weight Checker breaks down exactly which assets are slowing the page down.

Core Web Vitals Thresholds

Aim for Good on all three Core Web Vitals at the 75th percentile of page loads.

MetricGoodNeeds workPoor
LCP
Largest Contentful Paint
≤ 2.5s2.5s to 4.0s> 4.0s
INP
Interaction to Next Paint
≤ 200ms200ms to 500ms> 500ms
CLS
Cumulative Layout Shift
≤ 0.10.1 to 0.25> 0.25

What to Fix First

Poor LCP usually needs image, hosting, font, and render-blocking fixes. Poor INP usually needs JavaScript reduction. Poor CLS needs reserved image, ad, and embed space. For implementation help, read our website speed optimization guide.

What Each Core Web Vital Measures

Each metric maps to a different part of the experience, which means each has its own typical cause and primary fix. Use this alongside the thresholds above to prioritize work.

MetricWhat it measuresCommon cause of failurePrimary fix
LCPLoading: time to render the largest visible elementHeavy hero image, slow server, render-blocking CSS or fontsOptimize and preload the hero asset, improve TTFB, remove blocking resources
INPResponsiveness: delay between interaction and next paintHeavy JavaScript and long main-thread tasksReduce and split JavaScript, defer third-party scripts, break up long tasks
CLSVisual stability: unexpected layout movementImages without dimensions, late ads, injected bannersSet width and height, reserve space for embeds, avoid inserting content above existing content

Google grades these at the 75th percentile of real visits using field data. To turn a failing report into a fixed page, see our website speed and performance optimization service or request a free website audit.

Next steps

Core Web Vitals Checker related tools and articles

Continue with the closest follow-up checks and guides based on this tool's topic, crawl intent, and optimization workflow.

Core Web Vitals Checker: FAQ

What data does the Core Web Vitals Checker return?
It requests Google PageSpeed Insights for the selected mobile or desktop strategy. The rendered report can include page-level Chrome UX Report field metrics, origin-level field metrics, a Lighthouse performance score, and lab values for FCP, LCP, TBT, CLS, Speed Index, and server response time.
How should I read field data versus lab data?
Field data summarizes eligible real Chrome visits and is the evidence used for Core Web Vitals assessment. Lab data is one simulated Lighthouse run that helps diagnose a specific load. A good lab result does not guarantee good field data, and a single poor lab run does not prove most users have a poor experience.
Why are page field metrics missing while origin data is available?
The exact URL may not have enough eligible Chrome traffic for a page-level dataset. Google can sometimes provide aggregated data for the whole origin instead. Origin data is useful context but may combine templates and routes with very different performance.
What thresholds should I use for LCP, INP, and CLS?
At the 75th percentile, Good is LCP at or below 2.5 seconds, INP at or below 200 milliseconds, and CLS at or below 0.1. Needs Improvement extends to 4 seconds, 500 milliseconds, and 0.25 respectively. Values above those ranges are Poor.
Why can mobile and desktop results differ?
The selected strategy changes the Lighthouse test configuration, and page and origin field datasets are segmented by the data Google exposes. Mobile devices, networks, responsive assets, and interaction patterns often differ from desktop. Test both when both audiences matter and optimize against the slower important experience.
What should I do after a poor result?
Use the affected metric to guide diagnosis: improve server and critical-resource delivery for LCP, reduce long JavaScript tasks for INP or high TBT, and reserve stable layout space for CLS. Confirm changes in repeatable lab tests, then monitor field data because it updates over a longer window.
Why might the check return a quota or timeout error?
The API depends on Google PageSpeed Insights and waits up to 30 seconds. Google can throttle anonymous or keyed requests, exhaust a quota, fail to test an inaccessible page, or take too long. Retry later and do not interpret a request error as a performance score.
What data is sent when I run a Core Web Vitals check?
The public URL and selected mobile or desktop strategy are sent to the Web Aloha API, which forwards them to Google PageSpeed Insights. The form asks for no login or personal information, and the Web Aloha endpoint contains no application-storage step for the URL or returned report.

Free 48-Hour Website Audit

Not sure what to fix first on your own website? We'll review it and tell you, in plain English. Free & non-obligatory.

Need Better Core Web Vitals?

We help businesses improve real speed, mobile UX, Core Web Vitals, and conversion rates.