Core Web Vitals for WooCommerce: what LCP, INP and CLS reveal about your shop

Sooner or later it happens to every shop owner: Search Console reports "Core Web Vitals: poor", PageSpeed Insights shows orange and red circles, and the agency says "we need to optimize that". But: what exactly is broken here — and is it costing you revenue, or just peace of mind?

The Core Web Vitals are three measurements Google uses to grade the real user experience of your site. The convenient part: each of the three metrics measures a concrete moment in the buying process. Once you've translated them into shop language, you know fairly precisely where things are stuck.

The three metrics in shop language

LCP — "When do I see the product?"

Largest Contentful Paint measures when the largest element in the visible area has finished loading. In a shop that's almost always your hero or product image. Google's threshold: under 2.5 seconds is good, above 4 seconds is poor.

LCP is the metric that most directly matches "the shop feels slow" — and the one with the strongest revenue link: even 0.1 seconds faster load time measurably lifts retail conversions. An LCP of 4 seconds on mobile means: part of your visitors are gone before they ever saw your product.

INP — "Does the shop react when I click?"

Interaction to Next Paint measures how quickly the page visibly responds to clicks and inputs — across the whole visit, not just during load. In March 2024, INP replaced the old FID metric, and that matters for shops: FID was almost always green, INP mercilessly exposes JavaScript blocking the page. Good is under 200 milliseconds.

In shop language: INP is the moment your customer clicks "Add to cart" and… nothing happens. Half a second later the cart icon number hops. That half second is INP — and it feels like "broken", not like "slow".

CLS — "Does the page jump away under my finger?"

Cumulative Layout Shift measures how much content jumps around while loading. Good is under 0.1. The shop classic: you're about to tap "Buy", at that moment a cookie banner or a "today only −20%" strip loads in at the top, everything slides — and your finger lands on the newsletter popup. Everyone knows it, everyone hates it, and Google measures it.

Ranking or revenue — why the Vitals really matter

Two things, honestly weighed:

For ranking, the Core Web Vitals are a confirmed but moderate factor — more of a tie-breaker between similarly good results than a rank-1 guarantee. If you expect SEO miracles from the Vitals, you'll be disappointed.

For revenue, they're far more direct: the Vitals measure exactly the moments where buying interest turns into a purchase — seeing the product (LCP), adding to cart (INP), tapping through to checkout (CLS). That's why the optimization pays off even if you didn't care about ranking at all. The numbers are in the headless article with real before/after values.

Field vs. lab data — why PageSpeed has two opinions

The point where nearly all confusion starts: PageSpeed Insights shows two different measurements that can contradict each other.

• Field data (top): real Chrome users of your site, collected over the last 28 days (CrUX). This is the number that counts for Google — graded at the 75th percentile, i.e. by what three quarters of your visitors experience at minimum.
• Lab data (bottom): a single simulated run on a throttled device. Good for debugging, but not what Google grades.

Practical consequences: a shop can shine in the lab and fail in the field (your real customers have older phones than your office WiFi suggests). And: after an optimization it takes up to 28 days for field data to catch up — don't get nervous. Smaller shops sometimes have no field data at all; then Google grades origin-level values for the whole domain. Your overview lives in Search Console under "Core Web Vitals" — it shows which page groups are affected.

The typical WooCommerce causes — per metric

LCP red? In this order:

1. TTFB too high — the server needs a second before anything can even start loading. That's a hosting issue or a bloated database.
2. Product images too large or the wrong format — 2 MB JPEGs instead of properly sized WebP/AVIF.
3. Render-blocking CSS/JS — the theme loads 15 files before it shows the hero image.

INP red? Almost always JavaScript:

1. Theme/page-builder weight — Elementor and friends attach extra script work to every click.
2. Too many plugins loading everywhere — the plugin inventory is the most effective step here.
3. Cart fragments and checkout recalculations — WooCommerce recalculates server-side on input, especially at checkout.

CLS red? Everything that loads late and shoves:

1. Images without fixed dimensions — the browser doesn't know how much space to reserve.
2. Banners, cookie notices, popups snapping in at the top after load.
3. Late-loading webfonts that reflow the text.

The monthly routine for shop owners

You don't need to become a performance expert. This routine is enough:

1. Once a month, open Search Console → Core Web Vitals. Green? Done, back to business.
2. On orange/red: measure the affected page group in PageSpeed Insights and match it against the cause list above.
3. After every change (new plugin, new theme, new slider): measure once. Regressions creep in — usually as "just one more plugin".

When everything stays red despite optimizing

There's a point where WordPress on-board tools can't save the Vitals anymore: the theme structurally ships too much JavaScript (INP), and server-side rendering keeps LCP above the threshold no matter how much hosting you buy. From there it's not an optimization issue but an architecture issue — a static storefront in front of your existing WooCommerce serves pre-built pages, bringing LCP under 1 second and INP deep into green, without rebuilding your shop.

Where do your Vitals stand? Measure it in 30 seconds

I built a free WooCommerce speed check for exactly this: enter your shop URL and you get LCP, performance and more for mobile and desktop — measured with the same Google tooling as in this article, plus an honest assessment of which of the causes above applies to your shop.

---

Want the next performance and build guides — including all the pitfalls? Subscribe to the "Built with AI" newsletter.

Prefer done-for-you? Drop me a line — making slow WooCommerce shops fast is my day job.