liverpoolstyle.com loads fast for real visitors (LCP 1.9s) and responds well, but the page moves while it loads: Chrome's measure of layout shift for real shoppers is 0.43 on the homepage and 0.53 across the site, against a limit of 0.1. It is the only Core Web Vital the site fails. Google's test shows the hero block with "Discover More" and "Shop Now" moving, so shoppers tap where a button was a moment ago, on a page whose job is to send them into the collections.
First action
Record the homepage loading on a phone and note each element that moves.
How to measure it
CLS at the 75th percentile
- Now
- –
- Target
- under 0.1
- By
- 60 days
Steps
Find the shifts
PageSpeed and Chrome DevTools layout-shift regions on home, collection and product pages.
Shopify Developer 1 day
Fix the hero
Fixed aspect-ratio container and image dimensions.
Shopify Developer 1 day
Slot the banners
Reserved space for the announcement bar and app widgets.
Shopify Developer 2 days
Preload the font
Hero font with font-display set.
Shopify Developer 2 hours
Fix other templates
Collections and product pages.
Shopify Developer 3 days
Re-test
PageSpeed lab and field.
Shopify Developer 1 hour
Watch the field data
28-day Chrome UX Report.
Director of Ecommerce 4 weeks
Compare conversion
Mobile conversion before and after.
Director of Ecommerce 6 weeks
Why it works
Reserve the hero's space before it loads (fixed aspect ratio on the image or video container, width and height on images), give the announcement bar and any app banners (loyalty, cart, reviews) a fixed slot instead of injecting them above the content, and preload the hero font so text does not reflow. Then check the collection and product templates for the same pattern, because the site-wide score is worse than the homepage. Re-test with PageSpeed and watch the Chrome UX Report over 28 days.
A stable page means fewer mis-taps and a passing Core Web Vitals score on every template, which helps both conversion and search on a site that already loads quickly.
Ready to use
ChecklistLayout-shift fixes
[ ] Hero image/video: fixed aspect-ratio box [ ] Width and height on every img [ ] Announcement bar: fixed height from first paint [ ] Loyalty, cart and review widgets: reserved slots, no insertion above content [ ] Hero font preloaded [ ] Collection grid: image boxes sized before load [ ] Product page: gallery and price block sized before load [ ] Re-test home, one collection, one product
Risks and how to handle them
An app re-injects a banner after a theme update
Add a layout-shift check to every theme release.
Evidence
- Google PageSpeedHomepage (October 20, 2026): real Chrome visitors fail Core Web Vitals on layout stability only: CLS 0.43 at the 75th percentile (the limit is 0.1), while loading (LCP 1.9s) and responsiveness (INP 156 ms) pass. Across the whole site the Chrome UX Report shows CLS 0.53. In the lab the element that moves is the hero block with "DISCOVER MORE" and "SHOP NOW"; mobile score 32 (desktop 57), main content at 11.6s, 6.8 MB in 540 requests.Source
- Your websiteHomepage: a hero with "Discover More" and "Shop Now", four best sellers (Sherpa Trimmed Notch Collar Jacket $149, Kelsey Trouser $98, Bobbie Baby Boot $98, Fit and Flare Blazer $139), the Loyalist Club ($15 off) and a store-locator panel. The page has no social share image, and one homepage link is built from unrendered template code ("item.product_title"), which returns 404.Source
- Google PageSpeedThird-party load on the homepage: 35 third-party services, 3.9 MB of 6.8 MB. Largest: Rebuy 737 KB, Google Tag Manager 511 KB (364 ms blocking), True Fit 457 KB, Klaviyo 397 KB, Toki 331 KB, Facebook 226 KB, Searchspring 166 KB; also Stylitics, PostPilot and EqualWeb. Biggest fixes: efficient cache lifetimes (about 1.3s), unused JavaScript (1.4 MB, about 1.1s), render-blocking requests (about 1s). Product pages load both Okendo and Yotpo review code.Source