Skip to content
Guide

Core Web Vitals explained in plain English, and what to fix first

By the Vertex Stacks team · 5 min read · Updated

Core Web Vitals are Google's three measurements of how a page feels to a real person: how quickly the main content appears, how quickly the page responds when you tap or click, and whether things jump around while loading.

They are one signal among many, and great content still matters most. But a slow or jumpy site also loses visitors directly, whatever any search engine thinks.

The three numbers

  • Largest Contentful Paint (LCP): how long until the biggest thing in the first view (often a headline or hero image) is visible. Good is 2.5 seconds or less.
  • Interaction to Next Paint (INP): how long the page takes to react after a tap, click or key press. Good is 200 milliseconds or less. It replaced First Input Delay as the responsiveness metric in 2024.
  • Cumulative Layout Shift (CLS): how much content moves unexpectedly while loading. Good is 0.1 or less.

Google assesses these at the 75th percentile of real visits, which means three out of four of your visitors need a good experience, not just the fastest connections.

Why this matters to a business, not just to Google

A page that takes too long to show anything, reacts slowly to a tap, or shifts under a visitor's thumb as they try to press a button loses people before they read a word. Many of those people never come back, and most of them never tell you why.

That is why we treat these numbers as a usability check first and a search signal second. Fixing them helps every visitor, from every channel, including the ones who arrive from a link a friend sent.

Measure real visits, not just lab tests

PageSpeed Insights shows two things: a lab test run on a simulated phone, and field data from real Chrome users over the previous 28 days. The field data is what counts. A brand new site may show no field data for a few weeks because there are not enough visits yet. Search Console's Core Web Vitals report groups your real pages by status.

Fixes that usually improve LCP

  • Make sure the main image or heading is not hidden behind an animation or script. Anything that starts invisible delays the moment it counts as painted.
  • Serve images at the size they are shown, in a modern format, and do not lazy-load the image in the first view.
  • Reduce server response time with caching or static generation for pages that do not change per visitor.
  • Avoid chains of render-blocking files; load only the fonts and styles the first view needs.

Fixes that usually improve INP

  • Ship less JavaScript. Remove libraries you barely use and load heavy widgets (chat, maps, 3D) only when needed.
  • Break up long tasks so the browser can respond between them.
  • Keep heavy animation off the main thread, and respect the reduced-motion setting.

Fixes that usually improve CLS

  • Give every image, video and embed a width and height (or an aspect ratio) so space is reserved before it loads.
  • Reserve space for banners, cookie notices and ads instead of pushing content down when they appear.
  • Use fonts with a fallback that matches their size, so text does not reflow when the real font arrives.

Fix one metric at a time and re-measure. Large gains usually come from removing unnecessary work, not from adding more tools.

A simple plan for this week

  • Run PageSpeed Insights on your three most important pages and write down LCP, INP and CLS for each.
  • Find the single biggest problem on your slowest page. It is usually one oversized image, one slow script or one image with no reserved size.
  • Fix that one thing, deploy, and measure again. Repeat until the page passes.
  • Check the Core Web Vitals report in Search Console after about four weeks, because field data takes time to update.

Do not chase a perfect score of 100. A page that passes all three metrics for real visitors is doing its job, and further gains are usually invisible to people.