Core Web Vitals Explained for Founders and Product Teams
A non-technical introduction to Core Web Vitals — what LCP, CLS, and INP mean, why they affect SEO and conversions, and how to find out if your product is failing them.
Core Web Vitals measure loading, visual stability, and responsiveness. Understanding the three metrics helps product teams interpret performance reports and decide what engineering work to prioritize.
What Are Core Web Vitals?
Core Web Vitals are a set of three metrics Google uses to measure the real-world user experience of a web page. Google introduced them as ranking factors, meaning pages that perform better on these metrics may rank higher in search results than equivalent pages that perform poorly.
More importantly, they measure things that matter independently of Google: how fast your main content appears, whether your page layout is stable, and how quickly your page responds to user interaction. A page that fails Core Web Vitals is, by definition, delivering a poor experience to a meaningful portion of its visitors.
The three Core Web Vitals are:
- LCP — Largest Contentful Paint: measures loading speed
- CLS — Cumulative Layout Shift: measures visual stability
- INP — Interaction to Next Paint: measures responsiveness
Each metric has a "good" threshold, assessed at the 75th percentile of field measurements. Passing requires each of the three metrics to meet its threshold; this does not mean the same 75% of visits pass all three simultaneously.
LCP: Does Your Page Load Visibly Fast?
Largest Contentful Paint measures how long it takes for the main content of your page to appear on screen. In practice, this is almost always your hero image, your headline, or your featured photo.
Think of LCP as the moment a visitor stops seeing a blank or partially-loaded page and sees what they actually came for.
Good: 2.5 seconds or under Poor: above 4.0 seconds
Why it matters to your business: visitors who see a slow-loading page abandon it. Google's research shows that as page load time goes from 1 second to 3 seconds, the probability of a user bouncing increases by 32%. Check whether loading delays coincide with abandonment in your own analytics.
What causes poor LCP: usually a large hero image that takes too long to download, a slow server, or JavaScript blocking the page from rendering.
CLS: Does Your Page Stay Still While Loading?
Cumulative Layout Shift measures how much the content on your page moves around while it is loading. Have you ever tried to click a button on a page and had the page jump right as your finger reached it, causing you to click the wrong thing? That is a layout shift.
CLS is scored on a scale from 0 (no shifting) to a higher number representing more shifting. The unit is abstract, but the experience is concrete: a high CLS page feels unstable and unpolished.
Good: 0.1 or under Poor: above 0.25
Why it matters: layout shifts cause mis-clicks, mis-taps, and user frustration. On e-commerce pages, a shift that causes a user to accidentally add the wrong item or miss the checkout button has a direct conversion cost. On ad-supported content pages, a shift that causes a user to inadvertently click an ad (causing them to leave your site) erodes trust.
What causes poor CLS: images without reserved space, web fonts that swap in after the fallback renders, cookie banners that push content down, and ads that inject without reserved slots.
INP: Does Your Page Feel Responsive?
Interaction to Next Paint measures how quickly your page responds to user input — clicks, taps, keyboard interactions — throughout the entire lifetime of the page. It replaced a previous metric (First Input Delay) in 2024 because FID only measured the first interaction, and a page that responds well to its first click but sluggishly to subsequent ones was still failing users.
For a page visit, INP generally reports the slowest interaction, excluding one high-latency interaction per 50 interactions. Site-level reporting then uses the 75th percentile of page loads, separately for mobile and desktop. See Google's INP definition.
Good: 200 milliseconds or under Poor: above 500 milliseconds
Why it matters: INP is what separates a page that feels snappy from one that feels sluggish. A 500ms delay between clicking a button and seeing a result is noticeable to every user. On interactive products — dashboards, configurators, checkout flows, search results — INP directly affects task completion rates.
What causes poor INP: too much JavaScript running on the main thread, third-party scripts blocking the browser, large React or UI framework re-renders, and unoptimised event handlers.
How to Check Your Core Web Vitals Right Now
You do not need technical access to check your scores.
PageSpeed Insights: Go to pagespeed.web.dev and enter your URL. This shows both lab scores (simulated) and field data from real users if your site has enough traffic. The field data section ("Field Data") is what Google uses for ranking.
Google Search Console: If you have Search Console set up, the Core Web Vitals report under Experience shows how many of your URLs are in good, needs improvement, or poor status — broken down by mobile and desktop.
Chrome browser: Open any page, right-click, select Inspect, and go to the Lighthouse tab. Run an audit to see lab scores for that specific page.
If your field data shows "poor" or "needs improvement," that is your baseline. Lab scores help diagnose causes, but field data is what Google sees.
What Passing Core Web Vitals Actually Takes
Image handling, font loading, JavaScript execution, and caching can all affect Core Web Vitals. Use field data to identify the failing metric, then investigate its causes with lab tools.
The good news: many of the highest-impact fixes are one-time configuration changes: image format conversion, adding a CDN, setting explicit image dimensions in the HTML, adjusting how scripts load. They do not require re-architecting your product.
The harder cases involve deeply embedded problems: JavaScript-heavy applications that run too much code on the main thread, CMS-managed sites where editors routinely upload unoptimised images, and ad-supported pages with multiple third-party scripts competing for browser resources.
Knowing which situation you are in — a quick fix or a structural problem — is the first step. A proper performance audit tells you exactly where the issues are and what they will take to fix.