Definition
Core Web Vitals are the three metrics Google uses to describe how a page feels to the people who load it: Largest Contentful Paint for loading, Interaction to Next Paint for responsiveness, and Cumulative Layout Shift for visual stability. They are assessed on real visits rather than in a laboratory, and a page or group of pages is judged at the seventy-fifth percentile of those visits, separately for mobile and desktop.
One store's field data by template
- Good threshold for Largest Contentful Paint
- 2.5 seconds or less at the seventy-fifth percentile
- Good threshold for Interaction to Next Paint
- 200 milliseconds or less
- Good threshold for Cumulative Layout Shift
- 0.1 or less
- Home page on mobile
- Passing all three
- Product pages on mobile
- Loading over threshold, traced to an uncompressed hero image and a review widget loading above the fold
- Category pages on mobile
- Responsiveness over threshold, traced to filter scripts running on the main thread
- Where the data comes from
- Real visits from browsers that report field data, which is why a change takes weeks to show up in full
Illustrative results in a real reporting shape. The thresholds are Google's published values; everything below them here is an example of how the same store can pass on one template and fail on another.
Why it matters
Core Web Vitals matter to an online store for two separate reasons, and the smaller one is search. They are part of Google's page experience signals, useful as a tiebreaker rather than as a way to outrank better content. The larger reason is revenue. A product page that takes too long to render its main image, or a category page whose filters do not respond to a tap, loses shoppers who would otherwise have bought. Because the metrics are collected from actual visits, they measure the experience of the store's real audience on the devices and connections it actually has, which makes them a far better guide than a score generated on a fast desktop.
Where it goes wrong
- Optimising for a laboratory score instead of the field data, when the assessment that counts comes from real visits and can disagree with a single test run
- Treating the store as one page, since templates behave differently and a product page failure is invisible in a site-wide average dominated by the home page
- Fixing the home page because it is the one everyone looks at, when most sessions from search and ads land directly on a product or a category
- Adding apps without measuring what they cost, since each one brings scripts that load, run and often fetch again, and the effect accumulates quietly
- Expecting an immediate change in reporting after a fix, because field data covers a rolling window and takes weeks to reflect the new experience
Questions about Core Web Vitals
Do Core Web Vitals affect ecommerce rankings?
They contribute, and they are not a substitute for relevance. Google has been consistent that page experience helps when other things are comparable, so it rarely lifts a page above a better answer. Where the effect is more visible is in conversion, since the same problems that fail the thresholds are the ones that make a shopper give up on a product page.
Which of the three metrics do ecommerce stores usually fail?
Loading and responsiveness are the common ones, for related reasons. Product pages carry large imagery and a stack of third-party widgets for reviews, chat and personalisation, which delays the main content and occupies the main thread. Layout stability is usually easier to fix, since most shifts come from images without reserved dimensions and from banners injected after the page has drawn.
How does a Shopify store improve its Core Web Vitals?
Start by finding which templates fail and why, then work on the largest contributors: image sizing and formats, deferring scripts that are not needed for the first view, removing apps that are no longer used, and loading third-party widgets only when a shopper reaches them. Theme quality matters more than most single settings, and every installed app should be able to justify what it costs the page.