Core Web Vitals in Plain English: LCP, INP and CLS for Business Owners

If you've looked at Google Search Console or run a PageSpeed Insights test, you've probably seen the terms LCP, INP and CLS, often next to a worrying red or orange label. These are Google's Core Web Vitals, and they're one of the clearest ways to understand how your website feels to real visitors.

This guide explains each metric in plain English, gives you Google's official targets and covers the most common fixes.

What are Core Web Vitals?

Core Web Vitals are a small set of metrics from Google's Web Vitals initiative, designed to measure three aspects of user experience: loading, interactivity and visual stability. They're based on how real people experience your pages, measured in Chrome, not just lab tests. (web.dev)

The three current metrics and their "good" thresholds are:

Google recommends measuring at the 75th percentile of page loads, separately for mobile and desktop. A page "passes" when it meets all three targets for at least 75% of visits. (web.dev)

The three metrics, explained

LCP: "Has the important stuff loaded yet?"

Largest Contentful Paint measures how long it takes for the biggest visible element, usually a hero image, a video thumbnail or a large heading, to appear on screen. It's the closest single metric to the feeling of "the page has loaded."

Common causes of slow LCP: - Large, unoptimized hero images - Slow server response times - Render-blocking CSS and JavaScript - The main image being lazy-loaded (it should load immediately)

Typical fixes: compress and resize the hero image, serve modern formats (WebP/AVIF), preload the main image, use page caching and a CDN, and defer non-critical scripts.

INP: "Does the page respond when I use it?"

Interaction to Next Paint measures how quickly the page visually responds after someone interacts with it, such as clicking a menu, tapping a button or typing in a form. A high INP is the "I tapped it and nothing happened" feeling.

INP officially replaced the older First Input Delay (FID) metric as a Core Web Vital on March 12, 2024. (web.dev, 2024) If you're reading an older checklist that mentions FID, it's out of date.

Common causes of poor INP: - Heavy JavaScript running on the main thread - Too many third-party scripts (chat widgets, trackers, ad tags) - Complex page builders and sliders - Event handlers that do too much work at once

Typical fixes: remove unused scripts, delay non-essential third-party tags, break up long JavaScript tasks and simplify heavy interactive components.

A real example: redBus, a bus ticketing site, worked on INP by debouncing scroll handlers, fetching fewer results per request and reducing unnecessary re-renders. One key page interaction improved by 72%, and the company reported a 7% increase in overall sales. (web.dev case study)

CLS: "Why did that button just move?"

Cumulative Layout Shift measures unexpected movement of page content while it loads. You've experienced it when you go to tap a link and an image or ad loads above it, pushing everything down so you tap the wrong thing.

Common causes: - Images and videos without width and height attributes - Ads, embeds and iframes without reserved space - Banners or cookie notices that push content down - Web fonts that swap in and change text size

Typical fixes: always set image dimensions (or CSS aspect ratios), reserve space for ads and embeds, show banners as overlays rather than pushing content and use font-loading strategies that minimize shifts.

Do Core Web Vitals affect SEO?

Yes, but keep it in perspective. Google states that "Core Web Vitals are used by our ranking systems" and recommends achieving good scores. It also cautions that good scores don't guarantee top rankings, and that chasing a perfect score purely for SEO may not be the best use of your time. Relevance and helpful content still matter most. (Google Search Central)

A useful way to think about it: Core Web Vitals are less a ranking trick and more a measure of whether visitors have a good experience. And that affects conversions directly, as covered in Website speed and conversions.

How does the web as a whole perform?

Not as well as you might hope, which is an opportunity. The HTTP Archive's Web Almanac 2025 found that 48% of mobile websites and 56% of desktop websites achieved good Core Web Vitals, based on Chrome real-user data from July 2025. That's up from 44% and 55% in 2024. (HTTP Archive Web Almanac, 2025)

In other words, roughly half of mobile sites still don't pass. Getting your key pages into the "good" range can genuinely set you apart from competitors.

How to check your scores

• PageSpeed Insights (pagespeed.web.dev) shows real-user (field) data when available, plus a lab test with diagnostics.
• Google Search Console has a Core Web Vitals report that groups your URLs by status, based on real visitor data.
• Chrome DevTools helps developers diagnose specific issues.

One nuance: lab tests (like the Lighthouse score in PageSpeed Insights) simulate a page load, while field data reflects real visitors. Lab tools can't measure INP directly because there's no real user interacting, so they use Total Blocking Time as a proxy. When the two disagree, field data is what Google uses for Core Web Vitals assessments. (web.dev)

A practical improvement plan

1. Start in Search Console. Identify which page groups are "Poor" or "Needs improvement," and on mobile or desktop.
2. Prioritize by value. Fix templates that power your most important pages: homepage, service pages, product pages and landing pages.
3. Fix the biggest offender first. Usually LCP (images, server speed) or INP (scripts).
4. Fix at the template level. A fix to a shared template improves every page that uses it.
5. Validate and wait. Field data is based on a rolling window of real visits, so improvements take a few weeks to show fully.

The bottom line

Core Web Vitals boil down to three simple questions: does the page load quickly, does it respond quickly and does it stay still? Aim for LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less on your key pages, measured on real mobile visitors. Your visitors, and your conversion rate, will notice.