Core Web Vitals for stores

Core Web Vitals are Google's attempt to measure how a page actually feels to a real shopper, not how fast it looks in a lab. Three metrics make up the set, and each maps to a different moment in the loading experience: how quickly the main content appears, whether the layout jumps around while it loads, and how promptly the page reacts to a tap or click. For an online store, those three moments sit squarely between a shopper who reaches checkout and one who bounces back to the results.

The three metrics, and their thresholds

Google publishes a clear pass mark for each metric, measured at the 75th percentile of real visits — so a quarter of your traffic can be slower and you still pass. Aim for these:

• Largest Contentful Paint (LCP) — how long until the biggest element in the viewport, usually your hero or product image, is painted. Good is 2.5 seconds or less.
• Cumulative Layout Shift (CLS) — how much visible content moves unexpectedly as the page loads. Good is 0.1 or less.
• Interaction to Next Paint (INP) — how quickly the page responds to taps, clicks and keystrokes across the whole visit. Good is 200 milliseconds or less. INP replaced First Input Delay as a Core Web Vital in March 2024, and it is stricter, because it measures every interaction rather than just the first.

Improving LCP

On a product or category page the LCP element is almost always an image. The fastest wins: serve it in a modern format like WebP or AVIF, size it for the device instead of shipping a 3000px file to a phone, and mark it fetchpriority high so the browser loads it before less important assets. Strip out render-blocking scripts and lazy-load everything below the fold, but never lazy-load the LCP image itself. A solid CDN and a quick server response (Time to First Byte) matter too. Our image SEO guide covers the formatting side in depth.

Improving CLS

Layout shift is what makes a shopper tap the wrong button because a banner or ad pushed the page down at the last second. The cure is to reserve space for anything that loads late: set explicit width and height, or an aspect-ratio, on every image and embed, avoid injecting content above what the visitor is already reading, and preload fonts so text does not reflow when the custom typeface arrives. Cookie banners and promo bars are frequent CLS offenders on stores.

Improving INP

INP is usually a JavaScript problem. When a shopper taps Add to cart, the browser must finish whatever script is running before it can respond. Heavy third-party tags, chat widgets, review apps and analytics all compete for the main thread. Break long tasks into smaller pieces, defer non-essential scripts, and be ruthless about how many marketing tags you load. On Shopify and WooCommerce in particular, an over-stuffed app stack is the single most common cause of poor INP.

How to measure it properly

There are two kinds of data, and they answer different questions. Field data — the Chrome User Experience Report, shown in Search Console and PageSpeed Insights — is what Google actually uses for ranking, because it comes from real Chrome users. Lab data (Lighthouse) is a controlled simulation you run on demand to debug, but it will not always match the field. Trust the field for scoring, and use the lab to diagnose. Field data is a rolling 28-day average, so changes take weeks to surface; be patient after a fix.

• Read field scores in Search Console, page by page and by template type.
• Use Lighthouse or PageSpeed Insights to pin down the cause on a slow template.
• Fix the template, not the single URL — one product template can drive thousands of pages.
• Re-check after 28 days, once real-user data has caught up.

Where Core Web Vitals fit

Be realistic about weight. Core Web Vitals are a genuine ranking signal, but a modest one; they rarely lift a page from position 20 to position 3 on their own. What they reliably do is protect conversions and act as a tie-breaker between pages of similar relevance — and passing them is far cheaper than losing sales to a sluggish, jumpy page. They overlap heavily with raw page speed and with mobile-first SEO, since Google scores the mobile experience. If the whole stack needs untangling, our technical SEO service handles it end to end.