A product page can look ready to shop, then suddenly move just as your customer taps a size, reads a price, or reaches for the Add to Cart button. That movement is called cumulative layout shift (CLS). It makes your store feel less dependable and can lead to frustrating mistakes, especially on mobile.
To reduce cumulative layout shift on ecommerce pages, start by finding what moves, then give images and other content a predictable amount of space before they load. Product galleries, promotional banners, reviews, recommendations, and third-party widgets are common places to look. This guide shows you how to diagnose those shifts, fix the most likely causes, and check whether the changes work for real shoppers.
What CLS measures—and what score should you aim for?
CLS is a Core Web Vitals metric that measures unexpected movement of visible page content. It does not measure how long a page takes to load. A page can load quickly and still have a poor CLS score if its layout jumps around during loading or later in a shopper’s visit.
For Core Web Vitals, a CLS score of 0.1 or less is considered good; a score above 0.25 is considered poor. The result reported for a page or group of pages typically reflects the 75th percentile of real-user visits, so one smooth test on your own laptop is not enough to establish that the problem is solved.
Not every movement counts against CLS. For example, shifts that happen shortly after a user interaction are generally excluded. But that does not make every moving interface a good experience: a menu, variant selector, or cart drawer can still be confusing if it behaves unpredictably.
Find the layout shifts that matter most
Start with pages that shoppers actually use: your homepage, a collection page, a high-traffic product page, and the cart. Check both mobile and desktop layouts. A banner that looks stable on a wide screen may push half a product page downward on a phone.
- Check field data. Use PageSpeed Insights to see whether real-user Core Web Vitals data is available for a URL or its origin. Google Search Console’s Core Web Vitals report can help you identify groups of URLs with similar issues. Field data reflects past visits, so it will not change immediately after a fix.
- Reproduce the shift. Open the page in Chrome DevTools, record a load in the Performance panel, and inspect the reported layout shifts. Test with a mobile-sized viewport and a slower connection so late-loading elements are easier to spot.
- Watch the page as a shopper would. Load it without scrolling, then select a variant, open a cart drawer, and continue down to reviews and recommendations. Note what moved and what appeared immediately beforehand.
- Prioritize by impact. Fix shifts near prices, variant controls, and purchase buttons first. Then address components repeated across many pages, such as a site-wide promotional bar.
Lab tests help you diagnose a particular load; field data tells you how visitors experience the page across different devices and connections. Use both. If field data looks poor but your test looks fine, try a fresh browser session, a slower device, different products, and any banners or widgets shown only to certain visitors.
Reserve space for product and collection images
Images are often the first place to investigate. If the browser does not know an image’s proportions before it downloads, it may initially leave too little space. When the image appears, the price, product details, and buttons move.
Give images stable dimensions
Make sure product, collection, and promotional images have defined dimensions or a consistent aspect ratio in your theme. The browser can then reserve the right shape while the image loads. Responsive images can still scale to fit the screen; the important point is that their expected proportions are known in advance.
Check the entire gallery, not just its first image. If switching thumbnails changes the gallery’s height, the content below it may jump. A consistent image area is usually easier to shop than a gallery that resizes with each product photo. Choose a crop that shows the product clearly rather than stretching or distorting images to force them into place.
On collection pages, inspect product cards with unusually long names, sale badges, or missing images. A reliable card structure keeps prices and buttons from bouncing between rows while preserving readable product information.
Be careful with image-loading settings
Loading images only when they are needed can help avoid unnecessary downloads, but it does not remove the need to reserve their space. Check whether your theme or an app applies lazy loading to the main product image or a prominent above-the-fold banner. If that image appears late, it may create a noticeable blank area or shift other content. Test the change rather than assuming one loading setting is right for every image.
Stop banners, apps, and dynamic content from pushing the page down
Ecommerce pages often change after their initial HTML appears. A free-shipping message, review widget, payment option, inventory notice, or recommendation carousel may arrive a moment later. If it inserts itself above content the shopper is viewing, it can cause a layout shift.
- Promotional bars: If a bar sits above your navigation, allocate its space from the start. Check what happens when the message is dismissed and on smaller screens where the text wraps.
- Reviews and recommendations: Reserve a sensible area for components that load after the main page. Avoid an oversized empty box; use the space your usual content needs and test edge cases.
- Stock and delivery messages: Place them in a predictable section near the purchase controls. If the message changes by variant or postcode, check whether it pushes the Add to Cart button out of place.
- Cookie notices and pop-ups: An overlay may avoid shifting the page, but it must not hide essential shopping controls or make the page difficult to use.
Third-party apps deserve particular attention because they can change without a theme update. If a widget is responsible for a shift, review its placement and loading options. If you cannot control its dimensions, ask the provider what space its embed requires or consider whether the widget earns its place on that page.
Keep fonts and interactive elements predictable
A custom font can change the width and height of text when it replaces a fallback font. On a product page, that can turn a one-line title into two lines and move everything below it. Use a fallback font with similar proportions, keep font files and weights to those you need, and test key headings and buttons as the font loads.
Also check elements that expand: accordions, size guides, variant options, and cart messages. Movement caused directly by a click may not be included in CLS, but shoppers still need a clear response. Keep the selected control visible where possible, and avoid unexpectedly moving the purchase button just as someone is using it.
A practical workflow for fixing CLS without disrupting your store
You do not need to rebuild your storefront to make progress. Work through one page template at a time:
- Record a baseline. Note the field-data CLS result where available, and capture a repeatable lab test for representative mobile and desktop pages.
- Identify the moving element and its trigger. The element that visibly moves is not always the cause. Look above it for an image, banner, font, or widget that loaded or changed size.
- Fix the layout expectation. Define image proportions, reserve appropriate space for delayed content, or change where a dynamic element appears.
- Test real shopping paths. Check product variants, sale prices, long titles, sold-out items, logged-in states, and any location-specific messages your store uses.
- Monitor after release. Recheck lab tests promptly, then watch field data over time as new visits are collected. Revisit the page when you change themes, install apps, or launch campaigns.
If you use a hosted ecommerce platform, your options may depend on the theme and apps you have installed. Start with theme settings and app configuration before editing templates. When code changes are needed, give your developer a specific example of the shift, the page URL, device size, and steps to reproduce it. That is more useful than a request to “improve Core Web Vitals.”
Make stability part of your merchandising process
CLS is not only a launch-day technical check. New campaign banners, product photography, badges, and app embeds can reintroduce shifts on a previously stable page. Add a quick mobile layout check to your routine whenever you publish a new page design or major promotion.
Start with the elements closest to a purchase decision: the product image, price, options, and Add to Cart button. Give them stable positions, verify the result in testing, and keep an eye on real-user data. A calmer page is easier for shoppers to navigate—and easier for your team to maintain.
Frequently asked questions
Does a good CLS score guarantee better conversions?
No. Reducing unexpected movement removes a source of friction, but conversions also depend on factors such as product fit, pricing, trust, and checkout usability. Treat CLS as one part of a better shopping experience, not a guaranteed revenue lever.
Can a popup or cookie banner cause CLS?
Yes, if it is inserted into the page and pushes existing content aside. A fixed overlay may not shift the layout, but it can still obstruct important controls. Test both layout stability and usability.
Why does PageSpeed Insights show a different CLS result from my local test?
Your local test represents a particular page load under particular conditions. Field data reflects visits from real users across different devices, connections, and page states over time. Use the local test to investigate causes and field data to monitor the broader experience.
What should I fix first on a product page?
Check the main product image and gallery, then any late-loading content near the price and Add to Cart button. These elements are prominent, frequently used, and relatively straightforward to inspect for unexpected movement.