Core Web Vitals in Plain English: Why Site Speed = Money
Someone clicked on your site from search results, saw a blank white screen, and two seconds later went back to your competitors. You will never know it happened - in analytics it just shows up as “didn’t convert.” And the reason had nothing to do with price or product. The site took too long to load, and the customer didn’t wait.
Google sees stories like this by the millions. And it learned long ago how to measure them - with a set of metrics called Core Web Vitals.
What Are Core Web Vitals
Core Web Vitals are three indicators Google uses to evaluate a real person’s experience on a page. Not “how does the design look” or “how many keywords are in the text,” but the feel of the interaction: did it load quickly, does it respond to clicks, does everything jump around under your fingers.
And this is an official ranking factor. Meaning Google directly uses these numbers when deciding who to show higher in search results. Take two sites with similar content - the one that is faster and more stable gets the advantage.
There are three metrics:
- LCP - how quickly the main visible block loads.
- INP - how quickly the page responds to an action.
- CLS - how much the layout shifts during loading.
Let’s go through each one: what it measures, what threshold is considered good, and what to do about it.
LCP - Speed of Loading the Main Element
LCP (Largest Contentful Paint) answers a simple question: how many seconds does it take for a person to see the main content? Usually this is the largest element in the upper part of the screen - a large product image, a background photo, or a heading.
A good score is under 2.5 seconds. If you fit within that window, visitors barely notice the loading. If you don’t - they sit and stare at an empty or half-assembled screen. Then instinct kicks in: go back, try the next result in search.
What usually slows down LCP and how to fix it:
- A heavy main image. Compress it and convert it to the modern WebP format - the file size drops dramatically without quality loss. Load the first-screen image with priority so the browser handles it first.
- Slow hosting. A cheap, overloaded server takes half a second to respond to each request. Proper hosting and a CDN - a network that serves the site from the server closest to the visitor - helps.
- Blocking scripts. Extra libraries and widgets load before content appears. They need to be removed or deferred.
INP - Speed of Response to Actions
INP (Interaction to Next Paint) measures how long it takes for the page to respond to a user action: clicking a button, tapping a menu, typing in a field. In 2024 this metric replaced the old FID and became stricter - now all interactions are counted, not just the first one.
A good score is under 200 milliseconds. This is the threshold below which a response feels instant. When INP is high, you get that familiar frustration: you pressed “Buy” and nothing happens. You press again, again, start getting annoyed - and close the tab.
Most often, INP is hurt by overloaded JavaScript. The browser is trying to chew through heavy code and in that moment can’t keep up with responding to clicks. What to do:
- Reduce and split JavaScript. Large chunks of code are broken into pieces so the browser processes them in portions and stays responsive.
- Remove unnecessary third-party scripts. Every chat widget, analytics pixel, and counter adds load. Keep only what actually works for the business.
CLS - Layout Stability
CLS (Cumulative Layout Shift) shows how much the layout jumps around during loading. A familiar situation: you’re reading text, an image or banner loads at the top - and all the content suddenly shifts down. Or you’re aiming at a button, at the last moment an ad appears above it, and your finger lands in the wrong place.
A good score is under 0.1. The closer to zero, the calmer the page behaves. High CLS means missed button clicks, accidental ad clicks, and a general feeling that the site was put together carelessly.
It’s fixed by being careful in layout:
- Set dimensions in advance. For each image and video, specify width and height. Then the browser reserves space immediately, and content doesn’t jump when media finishes loading.
- Reserve space for banners and ads. If the page will have ads, an empty block of the right size is allocated for it in advance.
- Load fonts carefully. An improperly loaded font redraws text on the fly and shifts neighboring blocks. This is configured at the loading level.
Why This Is About Money, Not Just SEO
It’s easy to decide that Core Web Vitals are an SEO concern. In reality these numbers hit revenue from two sides at once.
The first side - rankings. A slow, jerky site Google ranks lower. Lower ranking means fewer clicks from search, fewer clicks means fewer leads. This arithmetic works every day, even if you can’t see it.
The second side - conversion. Say someone did make it to the site. But if LCP is high, they leave without waiting for it to load. If INP is high, they can’t properly click a button. If CLS is high, they miss and get frustrated. At each of these steps some people drop off - and this has nothing to do with search, it’s about how many of those who arrived actually submit a request.
It’s a double hit. First, a slow site brings in fewer people because it ranks lower in results. Then it loses some of those few who made it through. Speed is not a technical nitpick - it’s directly connected to money.
How to Measure and Where to Start
The good news: you can check your numbers for free in a couple of minutes.
- PageSpeed Insights from Google - paste a page URL and get a score for all three metrics. The tool shows both lab data (a test under ideal conditions) and field data - real statistics from live Chrome users.
- Search Console - in your site’s account there is a dedicated Core Web Vitals report. It groups pages by issue and shows trends over time.
- Audit on seonerve.com - the Performance section based on Lighthouse gives a speed score along with the rest of the SEO checklist, in one clear report.
Where to start in practice: run your homepage and a couple of key pages through PageSpeed Insights. Red and yellow metrics are your to-do list. Usually the fastest win comes from working on first-screen images: one heavy photo is often the cause of a slow LCP.
Check your site’s speed at seonerve.com - the audit will show which of the three metrics are in the risk zone and what to fix first. And if there’s no time to deal with optimization or it’s unclear where to start - we’ll speed up your site for you. We’ll bring Core Web Vitals into the green zone so visitors don’t leave from an empty screen, but become customers.