Copied!
Free Tool โ€ข Google API Powered โ€ข No Registration

Core Web Vitals Checker

Test LCP, INP, CLS and performance scores with real user data

Try: โ€ข โ€ข โ€ข

Powered by Google PageSpeed Insights.

Why Use Our Core Web Vitals Checker?

โšก

Google API

Official PSI data

๐Ÿ“Š

All Scores

Perf, A11y, SEO

๐Ÿ“ฑ

Mobile+Desktop

Both strategies

๐Ÿ‘ฅ

Real Users

CrUX field data

๐Ÿ”ง

Fixes

Ranked by savings

๐Ÿ’พ

Export

JSON, CSV, copy

How to Check Core Web Vitals

1

Enter URL

Paste any website URL you want to analyze.

2

Select Device

Choose Mobile (recommended) or Desktop.

3

Analyze

Google API runs full Lighthouse audit + CrUX.

4

Fix & Export

Review issues, export report, improve scores.

Core Web Vitals Checker: Measuring LCP, INP, and CLS for Better Rankings

Google's page experience signals have permanently changed how search engine rankings are determined. At the center of these signals are Core Web Vitals โ€” three specific, user-centric metrics that quantify real-world loading performance, responsiveness, and visual stability. A core web vitals checker gives you precise data on where your website stands against Google's thresholds, what's causing poor scores, and how to fix specific issues. This tool uses the official Google PageSpeed Insights API to provide the same data Google itself uses when evaluating your pages for ranking purposes.

What Are Core Web Vitals and How Are They Measured?

Largest Contentful Paint (LCP) measures how long it takes for the largest visible content element to render. Good LCP is 2.5 seconds or less. Interaction to Next Paint (INP) replaced FID in March 2024 and measures the latency of all interactions throughout page life. Good INP is 200ms or less. Cumulative Layout Shift (CLS) measures unexpected visual shifts. Good CLS is 0.1 or below. When you test website core web vitals online, our tool measures all three plus additional Lighthouse metrics and fetches real Chrome user data when available.

Why Does the API Show a Quota Error Sometimes?

Google's free PageSpeed Insights API provides 25 requests per day without an API key. When this limit is reached, the tool shows alternative links to check your site directly on Google PageSpeed, GTmetrix, and WebPageTest โ€” all of which use similar underlying technology. Adding your own free API key (available from Google Cloud Console at no cost) increases the limit to 25,000 requests per day. The PHP configuration file includes clear instructions for adding API keys and supports rotating through multiple keys automatically.

How Does Field Data Differ From Lab Data?

Lab data comes from Lighthouse running a simulated page load. Field data comes from real Chrome users via the Chrome User Experience Report (CrUX). Google uses field data for rankings, not lab data. If your URL lacks sufficient traffic, CrUX data may be unavailable. This online real user metrics checker displays both sources separately, making it clear which data influences rankings and which is diagnostic. When field data is available, you see 75th percentile values and distribution charts showing the percentage of users experiencing good, needs-improvement, or poor performance.

Can This Tool Help Identify What's Causing Poor LCP?

Yes. The Optimization Opportunities section lists specific technical issues causing slow LCP, sorted by estimated milliseconds of savings. Common LCP culprits include render-blocking resources, unoptimized images, slow server response times (TTFB), and large CSS files loaded synchronously. The diagnostics section reveals secondary issues that may not have direct savings estimates but affect the overall performance score. Use this free core web vitals audit tool to prioritize fixes that will produce the largest measurable improvement.

Do Core Web Vitals Directly Impact Google Rankings?

Yes. Google officially confirmed Core Web Vitals as ranking signals. Pages passing all three thresholds at the 75th percentile earn a "good" page experience designation. Google has stated that when content relevance is equal between competing pages, page experience can serve as a tiebreaker. This makes checking core web vitals for SEO an essential part of any technical optimization strategy, particularly in competitive niches.

Frequently Asked Questions

Three Google ranking metrics: LCP (loading speed), INP (interactivity), and CLS (visual stability). All measured at the 75th percentile of real user sessions.

Google's free API allows 25 requests per day. When this limit is reached, use the alternative links provided to check your site on PageSpeed, GTmetrix, or WebPageTest. Resets daily at midnight Pacific Time.

2.5 seconds or less is good (green). 2.5โ€“4s needs improvement (yellow). Above 4s is poor (red).

200ms or less is good. 200โ€“500ms needs improvement. Above 500ms is poor. INP replaced FID in March 2024.

0.1 or less is good. 0.1โ€“0.25 needs improvement. Above 0.25 is poor.

Yes, toggle between ๐Ÿ“ฑ Mobile and ๐Ÿ–ฅ๏ธ Desktop before running. Google uses mobile-first indexing, so mobile is most important for SEO.

Field data is from real Chrome users over 28 days (CrUX). Lab data is a simulated Lighthouse audit. Google uses field data for rankings.

Yes, completely free. Uses Google's public PageSpeed Insights API (25 requests/day without key).

Yes, Google confirmed they are ranking signals. Passing all three thresholds earns a "Good" page experience, which can give a ranking advantage.

After any code deployment, monthly for routine monitoring, and when you notice ranking drops. CrUX field data updates every 28 days.