Core Web Vitals Explained: What Business Owners Need to Know

Core Web Vitals are a set of three Google-defined metrics that measure how fast your website loads, how quickly it responds to user interactions, and how visually stable it is during load. They became a confirmed Google ranking signal in 2021. Poor scores can suppress your rankings in competitive search results. Passing scores do not guarantee top rankings, but failing them is a disadvantage your competitors can use against you.

What Are Core Web Vitals?

Core Web Vitals are three specific performance metrics that Google uses to measure user experience on the web. They assess how quickly a page's most important content loads (Largest Contentful Paint), how fast the page responds to the first user interaction (Interaction to Next Paint), and how much the page visually shifts during load (Cumulative Layout Shift).

Google introduced Core Web Vitals as a confirmed ranking signal through the Page Experience Update in 2021. They are measured using real-world Chrome user data collected from actual visitors, not from a simulated lab environment. That distinction matters: a fast connection in your office may produce good scores in a testing tool while your actual visitors on mobile connections experience slower load times.

The three metrics are assessed as Good, Needs Improvement, or Poor. Google has specific numerical thresholds for each classification.

What Is Largest Contentful Paint (LCP)?

Largest Contentful Paint measures how long it takes for the largest visible element on the page, typically a hero image or a large text block, to fully render in the viewport. It is a proxy for how fast the page feels to a user: even if other elements load quickly, a slow LCP means the most visually prominent part of the page is delayed.

Google's thresholds: Good is 2.5 seconds or faster. Needs Improvement is 2.5 to 4.0 seconds. Poor is slower than 4.0 seconds.

The most common causes of poor LCP scores: unoptimized images (large file sizes, no WebP format, no lazy loading), slow server response times, render-blocking CSS or JavaScript that delays the page from starting to display, and lack of a content delivery network (CDN) for geographically distributed visitors.

For most small business websites, the primary LCP culprit is unoptimized hero images. A 3MB JPEG where a 150KB WebP would serve the same visual purpose is a common and easily fixable problem.

What Is Interaction to Next Paint (INP)?

Interaction to Next Paint measures how quickly a page responds when a user clicks, taps, or types. It replaced First Input Delay (FID) as the official Core Web Vitals interactivity metric in March 2024.

INP captures the worst-case interaction delay across the full page session, not just the first interaction. A page that responds instantly to most clicks but has one slow interaction (such as a menu click that triggers heavy JavaScript) will have a poor INP score reflecting that slowest interaction.

Google's thresholds: Good is 200 milliseconds or faster. Needs Improvement is 200 to 500 milliseconds. Poor is slower than 500 milliseconds.

The most common causes of poor INP: heavy JavaScript executing on user interaction, third-party scripts (chat widgets, analytics tags, ad scripts) competing for browser resources, and unoptimized event handlers. INP issues are typically harder to diagnose and fix than LCP issues, because they require identifying which specific interaction is the bottleneck.

What Is Cumulative Layout Shift (CLS)?

Cumulative Layout Shift measures visual stability during page load. It captures how much the page's visible content moves unexpectedly while loading. The classic example: you are about to click a "Contact Us" button, an image or ad loads above it, and the button shifts down. You click the ad instead of the button.

Google's thresholds: Good is a CLS score of 0.1 or less. Needs Improvement is 0.1 to 0.25. Poor is above 0.25.

The most common causes of poor CLS: images and videos without specified dimensions in the HTML (so the browser does not reserve space for them during load), dynamic content injected above existing content, and web fonts that cause a flash of unstyled text that shifts the layout when the correct font loads.

CLS is often easier to fix than LCP or INP. Specifying image dimensions explicitly in the HTML, reserving space for ads and dynamic content blocks, and using font-display: swap for web fonts addresses the most common CLS sources.

Do Core Web Vitals Actually Affect Google Rankings?

Yes, but the magnitude of the effect is often misrepresented. Google has confirmed that Core Web Vitals are a tiebreaker signal, meaning they come into play when other signals (relevance, authority, content quality, backlinks) are roughly equal between competing pages.

For a small business competing for local service keywords with low-to-medium competition, failing Core Web Vitals is a disadvantage but rarely the primary reason a page is not ranking. If your Core Web Vitals are poor but your competitor's are also poor, the signal cancels out. If your competitor has strong vitals and you do not, the disadvantage is real.

The practical framing: fix Core Web Vitals because they represent genuine user experience quality, not purely as a ranking tactic. A page that loads slowly and shifts during load produces a worse experience and higher bounce rates regardless of the ranking effect. The ranking benefit from improvements is a secondary outcome.

Google Search Console's Core Web Vitals report shows you how real visitors experience your pages, separated into mobile and desktop categories. The mobile scores are typically worse, and they matter more for most search queries since the majority of searches now come from mobile devices.

How Do You Check Your Core Web Vitals Scores?

Google Search Console is the primary source for real-user Core Web Vitals data. The report is under the Experience section and shows how your pages are classified (Good, Needs Improvement, Poor) based on actual Chrome user data from the past 28 days.

PageSpeed Insights (pagespeed.web.dev) provides both lab data and field data for individual URLs. The field data comes from Chrome User Experience Report (CrUX) data and reflects real user experience. The lab data comes from a simulated test environment and is useful for diagnosis but does not represent actual visitor conditions.

Lighthouse (available in Chrome DevTools under the Audits tab) runs a local lab test and produces a detailed diagnostic with specific recommendations for each issue. Use Lighthouse to understand what to fix, and use Google Search Console to understand the real-world impact.

A note on mobile versus desktop: your desktop Core Web Vitals are almost always better than mobile. Prioritize fixing mobile scores because Google primarily uses mobile data for mobile-first indexing, which applies to most websites.

How Do You Fix Poor Core Web Vitals Scores?

Most Core Web Vitals issues fall into three categories.

Image optimization addresses the majority of LCP and CLS problems. Convert images to WebP format (20 to 30% smaller file size than JPEG at equivalent quality), specify image dimensions explicitly in HTML, and compress images to the smallest file size that maintains visual quality. For WordPress sites, plugins like Imagify, ShortPixel, or Cloudflare Images handle this automatically.

JavaScript and CSS optimization addresses INP and LCP issues caused by render-blocking resources. Deferring or asynchronizing non-critical scripts, removing unused CSS, and reducing the number of third-party scripts loading on page initialization are the core interventions. Third-party scripts (live chat, analytics, ad pixels) are common INP culprits and frequently receive less scrutiny than first-party code.

Hosting and delivery infrastructure affects LCP through server response time. A slow hosting provider that takes 400ms or more to deliver the first byte of HTML is contributing to poor LCP regardless of how well-optimized the rest of the page is. Moving to managed WordPress hosting or implementing a CDN (Cloudflare is the common choice for small business sites) typically produces 30 to 50% improvements in server response time.

For a complete technical SEO review that includes Core Web Vitals in the broader context of site health, see our technical SEO services and the technical SEO checklist resource.