# Why CLS is the hardest Core Web Vital to fix on Shopify | Storefront Speed Journal

Source: https://storefrontspeedjournal.com/blog/2026-09-23-shopify-cls-hardest-vital.html

Sep 23, 2026 - Storefront Speed Journal


Of the three Core Web Vitals, Cumulative Layout Shift is the one most Shopify stores fail, and the one least amenable to a quick theme setting. The reasons are structural: apps inject content late, fonts swap after render, and images arrive without reserved space.

## What CLS actually measures

CLS scores how much visible content moves around after it first renders. A product grid that jumps down half a second after the page appears, pushing the buy button out from under a tapping thumb, is the canonical example. Google wants a CLS score under 0.1; anything above 0.25 is poor. Unlike LCP, which is mostly about loading one big thing fast, CLS is about everything arriving in an orderly way, which is a coordination problem.

## Why Shopify themes are CLS-prone

The first offender is app embeds. Reviews widgets, upsell carousels, chat bubbles, and announcement bars typically inject their markup after the page has rendered, shoving content down. Each app is developed in isolation, so none of them coordinates with the others on layout. The theme cannot reserve space for content it does not know is coming.

The second is fonts. A theme that loads a display font late causes a flash of unstyled text followed by a reflow when the real font lands, and different font metrics mean different line breaks. The third is images without dimensions: hero banners and product images that load without width and height attributes collapse to zero height, then expand and push everything below them.

## The fix order that works

Start with what you control in the theme. Set explicit width and height on images, or use aspect-ratio boxes, so space is reserved before the image loads. Use font-display: swap with a well-matched fallback so the swap changes metrics as little as possible. These two changes fix a surprising share of theme-caused shift.

Then tackle app embeds. For each app that injects visible content, check whether it offers a placeholder or a reserved-height setting. If a reviews widget always ends up roughly 300 pixels tall on product pages, reserve 300 pixels and let the widget fill it. If an app cannot be tamed, question whether it earns its place on the page at all. The slowest, shiftiest app is often the one with the weakest business case.

## Measure in the field, not just the lab

CLS is a field metric, and lab scores can be misleading: a test run on a fast connection with an empty cart sees a different page than a real shopper on a phone. Use CrUX field data, via PageSpeed Insights or the CrUX API, to see which templates actually fail for real users. Fix the worst template first, because template-level fixes compound across every page that uses them.

## A practical check

* Record a video of the page loading on a mid-range phone and watch what moves.
* Attribute each shift to theme code, font loading, or a specific app.
* Fix theme-caused shifts first, then negotiate with or remove offending apps.
* Re-check field data after two weeks before declaring victory.

## Source

Primary reference: [web.dev CLS guidance](https://web.dev/articles/cls). Reviewed Sep 23, 2026.
