Google's real-visitor data for bloomchic.com shows shoppers already get a fast page: largest paint at 1.6 s and responsiveness at 140 ms both pass. The site still fails Core Web Vitals on one metric, layout shift, at 0.11 against a limit of 0.1, and PageSpeed names the element that moves: the sitewide promotional announcement bar. It appears after the page starts drawing and pushes the hero, the menu and the products below it down, so a shopper reaching for a category or a product can tap the wrong thing.
First action
Record a throttled-mobile Performance trace of the homepage in Chrome DevTools and confirm the announcement bar is the source of the shift.
How to measure it
Field CLS, 75th percentile
- Now
- –
- Target
- 0.05 or lower (passing is under 0.1)
- By
- 60 days
Steps
Reproduce the shift
Throttled mobile traces of the homepage, one collection and one product page; list every element that moves.
Shopify Developer 1 day
Reserve the space
A fixed min-height on the announcement bar container; rotating messages change text, never height.
Shopify Developer 1 day
Render the first message in Liquid
So nothing is injected above the content after load.
Shopify Developer 1 day
Check app banners
Email capture, app download and shipping notices either overlay or use a reserved slot; none may push content.
Head of E-commerce 2 days
Size images and video
Width and height or aspect-ratio on the hero video and product grid images.
Shopify Developer 2 days
Release and re-test
PageSpeed on the three templates; lab CLS should be near zero.
Shopify Developer 1 day
Watch field data
Search Console Core Web Vitals report weekly until the origin passes.
Head of E-commerce 4 weeks
Why it works
Render the announcement bar in the theme with its height reserved from the first paint: a fixed min-height on the container, with the first message written in the theme's Liquid instead of injected by script. Rotating messages then swap text inside a box that never changes size. Apply the same rule to any app banner above the fold (email capture, app download, shipping notices) and to collection and product templates, which share the header. Then watch real-visitor layout shift fall below 0.1 over the next 28-day Chrome data window.
Layout shift is the only Core Web Vital the site fails, and it misses by 0.01. A fix on the shared header moves every page at once. A stable page stops mis-taps on phones, and passing all three vitals removes a negative page-experience signal in Google Search during the months when promotions bring the most traffic.
Ready to use
ChecklistLayout-shift fix list
[ ] Announcement bar: fixed min-height, first message rendered in Liquid [ ] Rotating messages swap text only, never height [ ] App banners (email, app download, shipping) overlay or use a reserved slot [ ] Hero video and grid images have width/height or aspect-ratio [ ] Web fonts preloaded so text doesn't reflow [ ] PageSpeed re-run on home, collection and product templates [ ] Search Console Core Web Vitals checked weekly for 4 weeks
Risks and how to handle them
A fixed bar wastes space on small phones
Keep it to one line and turn longer messages into a link.
New pop-ins reintroduce the shift
Add "no layout shift" to the launch checklist for every banner or app.
Evidence
- PageSpeedHomepage test, November 3, 2026: real Chrome visitors pass largest paint (LCP 1.6 s) and responsiveness (INP 140 ms) but fail Core Web Vitals on layout shift (CLS 0.11; good is 0.1 or less). The element that shifts is the sitewide promotional announcement bar. Mobile lab score 52 (desktop 56); lab LCP 25.6 s, where the largest element is the hero background video; the page weighs 8.2 MB over 449 requests.Source
- PageSpeedSame test: savings from unused JavaScript (1.1 MB, about 2.6 s), cache lifetimes (874 KB, about 1.9 s), image delivery (1.1 MB, about 1.3 s) and render-blocking requests (1.2 s); 37 third-party services add 3.8 MB; accessibility score 72, with a viewport tag that blocks or limits pinch-zoom, 33 images without alt text and links search engines cannot crawl.Source