BigCommerce

Core Web Vitals for ecommerce: a practical guide to a faster store

A practical guide to Core Web Vitals for Shopify and BigCommerce stores: the thresholds, lab vs field data, common causes of a slow store and the fixes to make first.

Core Web Vitals are three Google measures of how a page feels to a real shopper: Largest Contentful Paint (LCP) for loading, Interaction to Next Paint (INP) for responsiveness and Cumulative Layout Shift (CLS) for visual stability. For an ecommerce store, "good" means LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less, measured at the 75th percentile of real visits. Most Shopify and BigCommerce stores that miss these targets do so for the same handful of reasons, and the fixes follow a predictable order.

What LCP, INP and CLS actually measure

Google's Web Vitals guidance on web.dev sets out the three metrics and their thresholds. INP replaced First Input Delay as a Core Web Vital in March 2024, so older audits that talk about FID are out of date.

Metric What it tells you Good Poor
LCP (Largest Contentful Paint) How long until the biggest thing on screen, usually the hero image or product photo, has appeared 2.5 seconds or less Over 4 seconds
INP (Interaction to Next Paint) How quickly the page responds visually when a shopper taps, clicks or types, across the whole visit 200 milliseconds or less Over 500 milliseconds
CLS (Cumulative Layout Shift) How much the layout jumps around unexpectedly while the page loads and is used 0.1 or less Over 0.25

Scores between good and poor are rated "needs improvement" by Google and "moderate" in Shopify's own reports. The thresholds apply to the 75th percentile, which means three out of four visits need to hit the target, not just the average visit. Measure mobile and desktop separately, because mobile is almost always the weaker of the two.

Lab data and field data: why your scores disagree

The two sets of numbers you see for the same page are both valid: they measure different things.

Lab data

When you run a page through PageSpeed Insights, the performance score out of 100 comes from Lighthouse running one simulated visit on a throttled connection. Google's PageSpeed Insights documentation describes lab data as collected in a controlled environment and useful for debugging. It is repeatable, so it is the right tool for checking whether a change helped. It is also only one visit on one simulated device, and it does not measure real interactions, so it cannot give you a true INP.

Field data

The section at the top of PageSpeed Insights, headed with your real users' experience, comes from the Chrome User Experience Report (CrUX). This is data from real Chrome users who have opted in, collected over the previous 28 days. Field data is what Google uses for the Core Web Vitals assessment, and it is what reflects your actual customers on their actual phones. Smaller stores or low traffic pages may not have enough visits to appear in CrUX at all.

Shopify merchants also have a web performance dashboard on the Themes page of the admin. It reports LCP, INP and CLS from real user data over the past 30 days, rated good, moderate or poor at the 75th percentile, with full reports by page URL and page type under Analytics.

The practical point: because field data is a rolling 28 day window, a fix you ship today will take weeks to show fully in CrUX. Use lab data to confirm the change worked, then watch field data for the following month.

What usually slows down a Shopify or BigCommerce store

The platforms are fast at the core. Slowness is nearly always added on top, and the causes fall into five groups.

Third-party tags

Analytics, advertising pixels, heatmaps, chat widgets, review widgets and affiliate scripts all run JavaScript in the shopper's browser. Each one competes with your own code for the main thread. Stores often carry tags from tools they stopped paying for years ago.

Heavy or late hero images

The hero image on the homepage, or the first product photo on a product page, is usually the LCP element. It is slow when it is oversized, served in an old format, lazy-loaded by mistake, or only discovered after JavaScript runs.

Layout shift from late content

Announcement bars, cookie banners, promotional strips and headers that are built in the browser after the page loads push everything below them down. Images without set dimensions and web fonts that swap in late do the same.

Apps

On Shopify in particular, each app can add its own scripts and styles to every page. Uninstalling an app does not always remove the code it added to the theme.

Too much JavaScript

Large bundles take time to download and even longer to run on a mid-range phone. Long tasks on the main thread are the main cause of poor INP: the shopper taps "add to bag" and nothing appears to happen.

Fixes in priority order

Work in this order. The early steps are cheap and often deliver most of the gain.

  1. Audit and cut third-party tags. List every script that loads, who owns it and whether anyone still uses the data. Remove what is unused. For what remains, load marketing and analytics tags after the page is usable rather than competing with the first render.
  2. Fix the LCP image. Make sure the hero is correctly sized and compressed, is in the initial HTML and is not lazy-loaded. web.dev's guide to optimising LCP says never to lazy-load your LCP image and suggests fetchpriority="high" on it. Apply it to the first hero only: the same guide notes that setting a high priority on more than one or two images makes it unhelpful.
  3. Reserve space for everything above the fold. Give images and embeds width and height, render announcement bars and headers with the page instead of injecting them later, and set a minimum height for anything that loads in, such as review stars or banners.
  4. Review apps. Remove apps you do not need, then check the theme for leftover code from apps already removed.
  5. Reduce and split JavaScript. Break up long tasks, defer code that is not needed for the first screen and keep click handlers light so the page can respond straight away. This is where INP improves.
  6. Improve server response and caching. On standard Shopify and BigCommerce themes the platform handles hosting. On headless builds, server response time is your responsibility, and edge caching makes a large difference.

A real example: L'azurde

L'azurde is a jewellery retailer selling across Saudi Arabia, the UAE and Egypt in Arabic and English, on a headless BigCommerce store with a Next.js front end. When we started, the homepage scored 42 on mobile and 48 on desktop in the PageSpeed Insights lab test, and the main content (the lab Largest Contentful Paint) took 8.1 seconds to appear.

On a headless build like this, the platform is no longer rendering and caching pages for you, so the later items in the priority list above carry the most weight: serving a complete first screen from the server, caching pages close to the shopper, keeping marketing tags out of the first render and prioritising a single hero image.

The homepage lab score went from 42 to 93 on mobile and from 48 to 100 on desktop, and main content time fell from 8.1 seconds to 3.1 seconds. To be clear about what those numbers are: they are lab results for the homepage, and 3.1 seconds is still above the 2.5 second LCP target, so there is more to do. We do not attribute any revenue or conversion change to this work. You can read more in the L'azurde case study.

How to measure before and after

Speed work is easy to get wrong if you do not measure it properly. A simple routine:

  • Pick a fixed set of pages. The homepage, one busy collection or category page and one top product page cover most journeys.
  • Record a baseline. Run each page through PageSpeed Insights three to five times on mobile and desktop and note the middle result, because lab scores vary between runs. Save the field data figures too, if your store has them.
  • Change one thing at a time where you can, so you know what helped.
  • Re-test in the lab straight after each release, using the same pages.
  • Check field data over the next four weeks in PageSpeed Insights, Search Console's Core Web Vitals report or, on Shopify, the web performance dashboard.

Core Web Vitals checklist for ecommerce

Check Helps Effort
Remove unused tags, pixels and widgets INP, LCP Low
Load marketing tags after the page is usable INP, LCP Low to medium
Hero image correctly sized and compressed LCP Low
Hero image not lazy-loaded, high priority on that image only LCP Low
Width and height set on images and embeds CLS Low
Header and announcement bar rendered with the page, not injected later CLS, LCP Medium
Space reserved for review stars, banners and late widgets CLS Low
Unused apps removed and leftover app code cleaned from the theme INP, LCP Medium
Long JavaScript tasks broken up, non-essential code deferred INP Medium to high
Server rendering and edge caching on headless builds LCP High
Baseline and after figures recorded for the same pages Proof Low

If you want help working through this list, our site speed optimisation service covers both Shopify and BigCommerce.

FAQs

What is a good PageSpeed score for an ecommerce site?

Google treats a lab score of 90 or above as good, and it is a useful debugging guide, but the Core Web Vitals assessment is based on field data. Aim for LCP within 2.5 seconds, INP of 200 milliseconds or less and CLS of 0.1 or less for at least 75% of real visits, on mobile as well as desktop.

Why does my score change every time I test?

Lab tests are a single simulated visit, and network and server conditions vary slightly between runs. Run several tests and use the middle result, and judge real progress on field data.

How long until fixes show in Google's data?

Field data in CrUX covers the previous 28 days, so a fix takes up to four weeks to be fully reflected. Lab tests show the effect immediately.

Do I need a headless build to have a fast store?

No. Many Shopify and BigCommerce theme stores can pass Core Web Vitals by cutting tags and apps, fixing the hero image and preventing layout shift. Headless gives more control but also makes server performance your responsibility.

How Superior can help

We are a London agency that designs, builds and supports Shopify Plus and BigCommerce stores, and speed is part of every build. If you would like to know where your store stands, start with our free starter audit, which will show you the biggest issues and what to fix first.

All insights

Start a project

Want help with this?

Tell us about your store. We reply within one working day with next steps.

Prefer email? hello@superiorecom.com