Peepers' homepage loads a cached copy of the whole product catalogue, a 3.2 MB file, so features like search and the strength picker work instantly. In Google's mobile test the page fetched that same file 9 times (2.4 MB of a 9.2 MB page), with 7.8s of main-thread work and the main image at 10.0s. Real visitors already feel it across the site: responsiveness (INP) is 226 ms, above Google's 200 ms limit, even though loading is fast.
First action
Find every script that requests the catalogue file and point them at one loader.
How to measure it
INP at the 75th percentile
- Now
- –
- Target
- under 200 ms
- By
- 60 days
Steps
Trace the requests
List every feature that fetches the catalogue.
Shopify Developer 1 day
One loader
A single shared promise and cache.
Shopify Developer 2 days
Load later
After first render or on first use.
Shopify Developer 1 day
Slim the file
Only the fields features use.
Shopify Developer 2 days
Retest
PageSpeed on homepage, collection and product pages.
Shopify Developer 1 day
Watch real users
Chrome UX Report and Clarity.
Director of Ecommerce monthly
Measure sales
Mobile conversion before and after.
Director of Ecommerce monthly
Why it works
Make one shared loader: fetch the catalogue once, keep it in memory (and in browser storage between pages) and let every feature read from it. Load it only after the page has rendered or when a shopper opens search, the finder or the strength picker. Trim the file to the fields those features use (title, handle, strengths, colours, price, image), which should cut it to a fraction of 3.2 MB.
Less JavaScript and data work on a phone means faster taps on strength, colour and add to cart, the actions that decide a $25 sale, and passing INP protects search ranking.
Ready to use
ChecklistCatalogue loading fix
[ ] Every script that fetches the catalogue file listed [ ] One shared loader returning the same promise [ ] Stored between page views [ ] Loaded after first render or on first use [ ] File trimmed to the fields in use [ ] PageSpeed retest on 3 page types [ ] INP checked in Chrome UX Report after 28 days
Risks and how to handle them
Search feels slower on first use
Preload when the shopper focuses the search box.
A stale catalogue shows old stock
Keep the dated file name and refresh daily.
Evidence
- Google PageSpeedHomepage, mobile lab test (October 20, 2026): performance 47/100; the main content appears at 10.0s; 9.2 MB downloaded in 702 requests; 7.8s of main-thread work and 490 ms of blocking time; 443 KB of unused JavaScript. The page's code points to one cached product catalogue file (3.2 MB of JSON, about 268 KB compressed) and the test fetched that same file 9 times, 2.4 MB of the transfer.Source
- Google PageSpeedReal visitors (Chrome UX Report): the homepage itself passes Core Web Vitals (LCP 2.47s, INP 163 ms, CLS 0). Across the whole site, responsiveness misses Google's "good" limit: INP 226 ms at the 75th percentile against a 200 ms limit, while loading (LCP 1.3s) and layout (CLS 0.03) are good.Source
- Your websiteShopping tools: Virtual Try-On on every product page ("tap Try On"), a Perfect Pair Finder, a "What's my power" eye chart and a strength picker ("We'll remember it on every page"); "Not sure? Find my strength" in every menu.Source