core web vitals: the scorecard your store gets silently judged on
No popup, no warning: a slow store just quietly loses visitors and ranking. Here’s what these three metrics measure, and the mistakes that break them most often.
Core web vitals aren’t an abstract technical term, they’re three concrete measurements of how a real visitor experiences your store: how fast something becomes visible, how fast it responds to a click, and how stable the page stays while it loads.
what do the three core metrics actually measure?
Largest Contentful Paint measures how long it takes for the largest visible element, usually a product photo, to fully load. Interaction to Next Paint measures the delay between a click and the response to it. Cumulative Layout Shift measures how much the page jumps around while elements are still loading, like an “add to cart” button that shifts right as you try to click it.
which mistake shows up most often on stores?
A hero image of several megabytes sent unchanged to a phone, when the screen needs a fraction of that resolution. That single file often single-handedly decides whether your Largest Contentful Paint falls within a healthy range or not.
and the mistake nobody blames on the theme?
Apps. Every app adds at least one script that has to load before the page feels interactive. Reviews, upsells, tracking pixels and chat widgets all add up, even when only one of them is actually needed on a single page. That mostly hits Interaction to Next Paint: the page is there, but responds slowly to the first click.
| metric | what it measures | most common cause on stores |
|---|---|---|
| largest contentful paint | how fast the largest element loads | oversized, unoptimized images |
| interaction to next paint | delay between a click and the response | a pile-up of app scripts |
| cumulative layout shift | how much the page jumps around while loading | images and banners with no fixed dimensions |
where to start if you want to tackle this yourself
- ✸Open devtools on your busiest product page and count how many scripts load before the page is interactive
- ✸Compress and resize hero images to the actual screen size, not the original photo size
- ✸Set fixed dimensions on images and banners, so they don’t claim space that hasn’t loaded yet
- ✸Evaluate each app: what does it cost in load time, what does it earn, does anyone still use it
- ✸Measure on a real device, not just a simulation on a fast office laptop
frequently asked questions about core web vitals
do core web vitals affect my google ranking?
Yes, it’s one of the ranking factors, though content and relevance still weigh more heavily. Slow load times can, however, cancel out an advantage you earned with good content.
can I fix this with a new theme?
Usually not. In practice the problem sits more often in apps and images than in the theme code itself.
how often should I measure this?
Every time you add an app or upload a large batch of new product photos, plus a standard check every quarter.
which tool do I use to measure this?
Google’s PageSpeed Insights and Chrome devtools both give a concrete report based on real measurements, not just an estimate.
is mobile or desktop more important to measure?
Mobile, since most store traffic now comes from phones and mobile connections leave less room for error.
“A rescue always costs less than the rebuild you were quoted instead.”