If your online store loads slowly, customers leave before they ever see your products. Google measures that experience with three numbers called Core Web Vitals — LCP, INP and CLS — and they feed into how your store ranks in search. The good news is that you do not need to be a developer to understand them. This guide explains each one in plain language, what a good score looks like, and what to fix first.

I work with e-commerce websites every day, both on my own store and for clients, and Core Web Vitals come up in almost every performance review. They are not abstract scores. Each one describes something a real shopper feels: how long until the page looks ready, how quickly it responds when they tap something, and whether the page jumps around while it loads. Get those three right and the store feels fast, trustworthy and easy to buy from.

What Are Core Web Vitals?

Core Web Vitals are a small set of metrics Google uses to judge the loading experience of a web page. They are measured from real visitors, not just in a lab test, which means your score reflects what actual customers experience on their own devices and connections. Google has said these metrics are a ranking signal, but the more important reason to care is conversion: a slow, jumpy store sells less than a fast, stable one.

The three metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP) and Cumulative Layout Shift (CLS). Each measures a different part of the experience, and each has a threshold Google calls "good". A page needs to pass all three to be counted as passing overall.

LCP: How Fast the Page Looks Ready

Largest Contentful Paint measures how long it takes for the biggest visible piece of content to appear — usually the main product image, a hero banner, or the largest block of text. It is the visitor's first impression of speed. Google considers an LCP under 2.5 seconds good, between 2.5 and 4 seconds in need of improvement, and over 4 seconds poor.

On an e-commerce store, LCP problems usually come from a few familiar causes. Large uncompressed product images are the most common. A slow server response is another — if the server takes two seconds to answer, nothing else can be fast. Heavy scripts, such as chat widgets, tracking tags and sliders that load before the main content, also push LCP later.

To improve LCP, start with the images: compress them, serve them in a modern format, and make sure the main product image loads first. Then look at the server — a slow host or an uncached page is often the real bottleneck. My guide on how to speed up a slow website walks through these steps in detail.

INP: How Quickly the Page Responds

Interaction to Next Paint measures how long a page takes to respond after a visitor interacts with it — clicking a button, tapping a menu, or typing in a search box. Google considers an INP under 200 milliseconds good, between 200 and 500 milliseconds in need of improvement, and over 500 milliseconds poor.

INP matters enormously on a store, because shopping is a series of interactions: add to cart, choose a size, open the checkout, apply a coupon. If each tap takes half a second to register, the store feels sluggish and customers lose confidence. The usual causes are heavy JavaScript — too many scripts running on the page, third-party widgets, or code that blocks the browser while it works.

Improving INP is usually a developer task, but the owner can drive it. Ask your developer or theme provider which scripts load on product pages and whether any can be delayed or removed. Common wins include removing unused apps and plugins, delaying chat widgets until after the page loads, and simplifying oversized menus. Every script you remove is a little less work the browser has to do before it can respond to a tap.

CLS: Whether the Page Jumps Around

Cumulative Layout Shift measures how much the visible content moves while the page loads. A good CLS score is under 0.1; between 0.1 and 0.25 needs improvement, and above 0.25 is poor. You have felt this yourself: you are about to tap a button and the page shifts, so you tap an advert or the wrong link instead. On a store, that can mean a customer accidentally removes an item from the cart or taps the wrong product.

CLS is usually caused by images without set dimensions, web fonts that swap in late, and banners or pop-ups that appear after the page has started rendering. The fixes are straightforward: give every image explicit width and height so the browser reserves the right space, load fonts in a way that avoids sudden swaps, and reserve space for any banner or pop-up that appears above the content.

How to Measure Your Store's Scores

You do not need paid tools to check Core Web Vitals. Google's PageSpeed Insights is free: enter your store's URL and it reports LCP, INP and CLS for mobile and desktop, based on real visitor data where available. Google Search Console also has a Core Web Vitals report that shows how many of your pages pass or fail across the whole site, grouped by the issue.

Start with your most important pages: the homepage, your best-selling product pages, and the category pages that bring in search traffic. Fix the homepage and top products first — that is where the money is. A technical SEO audit is a good way to find these issues systematically if you want a full picture.

What to Fix First

If you can only do a few things this week, do these in order:

1. Compress and resize your images. Product photos are the biggest files on most stores, and fixing them helps LCP immediately.
2. Remove or delay unnecessary scripts. Audit the apps, widgets and tracking tags on your product pages and remove anything that is not earning its place.
3. Fix layout shift. Set image dimensions and reserve space for banners. This is often a quick theme setting or a small code change.
4. Check your hosting. If the server response is slow, no amount of front-end work will fix LCP. Talk to your host about caching and server performance.
5. Test on a real phone. Most of your customers shop on mobile, and mobile scores are usually worse than desktop. Test the way they experience the store.

Frequently Asked Questions

Do Core Web Vitals affect Google rankings?

Yes, they are a ranking signal, but a small one compared with relevance and content quality. Their bigger impact is on visitors: a fast store converts better and earns more repeat visits, which is what really grows rankings over time.

What is a good Core Web Vitals score for an online store?

Aim for LCP under 2.5 seconds, INP under 200 milliseconds and CLS under 0.1 on mobile. Passing all three on your key pages is a realistic and worthwhile target.

Why is my mobile score worse than desktop?

Mobile devices have less processing power and often slower connections, so the same page takes longer to load and respond. Google measures mobile first, so optimise for the phone your customers actually use.

Can I fix Core Web Vitals without a developer?

Partly. Image compression, removing unused apps and choosing a faster theme are owner-level fixes. Script optimisation and layout-shift fixes often need a developer, but a clear report from PageSpeed Insights gives them an exact list to work from.

Speed Is a Feature of Your Store

Core Web Vitals are not a technical chore to tick off — they describe how your store feels to the person trying to buy from you. A page that appears quickly, responds instantly and never jumps around builds trust, and trust is what turns a visitor into a customer. Measure your key pages this week, fix the biggest issue first, and re-test. Small, steady improvements add up to a store that feels noticeably better to every shopper.