Core Web Vitals are three measurements Google uses to judge how your pages feel to real visitors: how fast the main content appears, how quickly the page responds to a tap and whether the layout jumps around. If you run a store or a business site, they explain a confusing situation many owners hit: PageSpeed shows a score of 90, yet Search Console says your pages failed.
This guide explains the three metrics in plain language, shows how to test them for free and lists the usual causes and fixes on business sites. It does not repeat the server response, redirect and mobile indexing checks from our 7-point ranking audit, so read that one first if your site is not ranking at all.
The three Core Web Vitals and their 2026 thresholds
| Metric | What it measures | Good | Poor |
|---|---|---|---|
| LCP (Largest Contentful Paint) | How fast the main content loads | 2.5 seconds or less | Over 4 seconds |
| INP (Interaction to Next Paint) | How quickly the page responds when someone taps or clicks | 200 milliseconds or less | Over 500 milliseconds |
| CLS (Cumulative Layout Shift) | How much the layout jumps while loading | 0.1 or less | Over 0.25 |
A page passes when at least 75% of real visits are “good” on all three.
Two corrections to things you may have read:
- FID is gone. First Input Delay was replaced by INP in March 2024. Any guide that still lists FID is outdated.
- Google did not lower the LCP threshold to 2.0 seconds in 2026. That claim is circulating, but Google’s documentation still lists 2.5 seconds.
You can read Google’s definitions on web.dev.
Why PageSpeed shows 90 but Core Web Vitals says failed
This is the most common confusion, and it comes from two different kinds of data:
- Lab data is a single simulated test on a throttled device. It is what produces the big score at the top of a report.
- Field data is what real Chrome visitors experienced on your site, collected over a rolling 28 days. This is what Search Console reports and what counts for Core Web Vitals.
Because Google looks at the 75th percentile, your slowest quarter of visits decides the result. If many of your customers browse on mobile data or older phones, their experience sets your score, not the fast test on your laptop.
A fix also takes time to show. After you improve a page, expect up to 28 days before the report clears.
How to test your Core Web Vitals for free
- PageSpeed Insights. Open PageSpeed Insights, paste your URL and check the “Discover what your real users are experiencing” section. That is field data.
- Search Console. Open the Core Web Vitals report. It groups similar pages and shows Poor, Needs improvement and Good for mobile and desktop.
- Lighthouse in Chrome. Use it to find causes on a page, not to decide whether you pass.
If PageSpeed says there is not enough field data, your site simply does not get enough Chrome traffic yet. In that case, use the lab test to find problems and apply the same fixes.
Core Web Vitals assessment failed: what usually causes it
| Metric | Common cause on business and store sites | What to do |
|---|---|---|
| LCP | A large hero banner or product image that is uncompressed or lazy-loaded, or a slow server | Compress and size the main image, do not lazy-load the first image on the page, use caching and check your server response time, as covered in our 7-point ranking audit. See also our guide to web hosting in Pakistan |
| INP | Too many scripts: chat widgets, tracking pixels, sliders, pop-ups, review apps | Remove what you do not use, load the rest later and test again. Tracking is a common culprit, so keep your Pixel and Conversions API and GA4 setup clean |
| CLS | Images and banners with no set size, pop-ups that push content, fonts that swap late | Give images fixed dimensions, reserve space for banners and ads, and delay pop-ups |
On Shopify, unused apps are a frequent cause of INP problems. Our Shopify SEO guide covers the store-specific checks. On WordPress, plugins and heavy themes play the same role.
Do Core Web Vitals affect SEO and sales?
They are part of Google’s page experience signals, but most sources describe the ranking effect as small. Think of it as a tie-breaker. Strong content and relevance still matter more.
The better reason to care is your customers. A page that loads late, jumps when someone is about to tap or ignores their taps costs you orders. Fix the metrics for visitors first, and any ranking benefit is a bonus.
Fix it yourself or hire help?
You can handle simple wins yourself: compress the hero image, remove unused apps or plugins, set image sizes and reduce pop-ups. Bring in a developer when INP stays high after cleanup, when your theme is heavily customized or when you do not know which script is the problem. Ask for a before and after report that uses field data, not only a lab score.
Frequently asked questions about Core Web Vitals
Q1. What are Core Web Vitals?
Three metrics Google uses to measure real user experience: LCP for loading, INP for responsiveness and CLS for visual stability.
Q2. What are good Core Web Vitals scores?
LCP at or under 2.5 seconds, INP at or under 200 milliseconds and CLS at or under 0.1, measured at the 75th percentile of real visits.
Q3. What replaced FID in Core Web Vitals?
INP, in March 2024.
Q4. How do I run a Core Web Vitals test?
Use PageSpeed Insights for field and lab data, and the Core Web Vitals report in Search Console for your whole site.
Q5. Why did my Core Web Vitals assessment fail even though my PageSpeed score is high?
The score is lab data. The assessment uses field data from real users over 28 days at the 75th percentile.
Q6. How long does it take to see improvements?
Up to 28 days, because the report uses a rolling 28-day window.
Q7. Do Core Web Vitals affect Google rankings?
They are a real but small signal, more like a tie-breaker. Their bigger effect is on user experience and conversions.
