What Are Core Web Vitals and Why Do They Matter?
Core Web Vitals are three metrics defined by Google: Largest Contentful Paint (LCP) measures how fast the main content loads, Interaction to Next Paint (INP) measures how quickly the page responds to user input, and Cumulative Layout Shift (CLS) measures how much the page layout shifts while loading. Google uses these as a ranking factor. Good scores are LCP under 2.5 seconds, INP under 200 milliseconds, and CLS under 0.1.
Core Web Vitals are three Google metrics that measure how users experience your website: load speed, interactivity, and visual stability. They affect your search rankings.
The three metrics explained
Largest Contentful Paint (LCP) measures how long it takes for the largest visible element on the page to load. This is typically a hero image, a large heading, or a background image. Google considers an LCP under 2.5 seconds good; above 4 seconds is poor. Interaction to Next Paint (INP) measures how responsive the page is when a user interacts with it: clicking a button, selecting a menu item, or typing in a form field. Good INP is under 200 milliseconds. Cumulative Layout Shift (CLS) measures visual stability: how much elements move around while the page is loading. If a button shifts just as you try to click it, that is a high CLS score. Good CLS is under 0.1.
Why Google uses them as a ranking factor
Google’s stated goal is to reward pages that deliver a good user experience. A page that loads slowly, responds sluggishly to clicks, or jumps around while loading frustrates users. Core Web Vitals give Google a consistent, measurable way to assess that experience at scale. They are not the only ranking factor, but poor scores can hurt your position, and good scores contribute positively alongside other signals like content relevance and authority.
How to measure your scores
PageSpeed Insights (pagespeed.web.dev) gives you both lab data from a simulated test and field data from the Chrome User Experience Report, which reflects real user measurements. Google Search Console has a Core Web Vitals report that shows which URLs on your site are failing, passing, or need improvement. You can also use Lighthouse in Chrome DevTools for detailed diagnostics with specific recommendations per issue.
Three practical improvement tips
To improve LCP: serve images in modern formats (WebP or AVIF), add explicit width and height attributes to your largest images, and use a CDN to serve static assets from a server close to your users. To improve INP: reduce the amount of JavaScript that executes on page load and defer scripts that are not needed for the initial render. To improve CLS: always specify image dimensions in your HTML so the browser reserves space before the image loads, and avoid injecting content above existing content after the page has rendered.
For context on broader website performance choices, see what is a Progressive Web App for how PWA architecture relates to performance.
Our tip: Run PageSpeed Insights on your three most important pages, not just your homepage. Product pages, landing pages, and blog articles often have worse scores because they carry more images and third-party scripts. Fix the pages that drive the most traffic first.
Frequently asked questions
How much do Core Web Vitals affect Google rankings?
Core Web Vitals are a confirmed ranking factor, but they are one of many. Pages with very poor scores can be penalized relative to competing pages with similar content. Pages with good scores gain a small positive signal. The primary ranking factors remain content relevance, backlinks, and technical SEO. Core Web Vitals matter most when competing pages are otherwise equivalent in quality: good scores can be the tiebreaker.
What is a good LCP score?
Google defines LCP under 2.5 seconds as good, between 2.5 and 4 seconds as needing improvement, and above 4 seconds as poor. LCP is measured from when the page starts loading to when the largest visible content element, typically a hero image or large heading, has finished rendering. LCP is one of the most impactful metrics because slow loading strongly correlates with users leaving the page before it finishes.
What causes high CLS?
CLS is caused by elements that load after the initial render and push existing content around. Common culprits include images without explicit width and height attributes (the browser does not reserve space for them), web fonts that cause text to reflow when they load, and ads or embeds injected into the page after load. The fix is to reserve space for all elements before they load, so the layout does not shift when content appears.
Where can I check my Core Web Vitals?
PageSpeed Insights (pagespeed.web.dev) shows both lab data and real-user field data for any public URL. Google Search Console has a dedicated Core Web Vitals report showing which URLs on your site pass, need improvement, or fail, based on real Chrome user data. Lighthouse, available in Chrome DevTools, provides detailed diagnostics and specific recommendations per issue.