How do you make a D2C store load faster on mobile?
Practical steps to speed up a Shopify or WooCommerce D2C store on mobile and pass Core Web Vitals: images, apps, scripts, fonts, themes and testing.
Anadoris Digital · · 4 min read

Speed matters more for D2C brands than for most websites because so many visitors arrive on phones, from Instagram, on patchy mobile data. A page that shows a blank screen for a few seconds loses people who were interested enough to tap an ad you paid for. Speed is also one of the signals Google uses in its page experience assessment, through Core Web Vitals.
The good news is that the biggest causes of slowness are usually within your control and need no rebuild. This guide covers where speed is lost, how to measure it properly and the fixes that tend to matter most.
Measure the right way
Lab tools such as PageSpeed Insights and Lighthouse simulate a page load and give a score. They are useful for finding problems but can swing from run to run. Field data, collected from real Chrome users and shown in Search Console’s Core Web Vitals report and in PageSpeed Insights when enough data exists, tells you what shoppers actually experience. Use lab tools to diagnose and field data to judge.
- Largest Contentful Paint (LCP): how quickly the main content, often the hero or product image, appears.
- Interaction to Next Paint (INP): how quickly the page responds when someone taps, such as on a variant or add-to-cart.
- Cumulative Layout Shift (CLS): how much the page jumps around while loading.
Test your home page, a collection page and your best-selling product page, since each behaves differently. And test on a real mid-range Android phone on mobile data at least once; it reveals problems an office laptop on Wi-Fi hides.
Images: usually the biggest win
Product and banner images are often far larger than needed. A hero banner uploaded straight from a designer’s export can be several times the size it needs to be on a phone screen. Hosted platforms usually resize and convert images automatically if your theme uses their image settings correctly, but uploaded originals still matter.
- Compress images before upload and avoid huge originals.
- Use theme settings that serve responsive sizes and modern formats such as WebP.
- Do not lazy-load the main product image or hero; do lazy-load images further down.
- Set width and height on images so the page does not jump as they load.
- Replace autoplaying hero videos with a poster image and tap-to-play where possible.
Apps and third-party scripts
Every app that adds something to your storefront, such as reviews, chat widgets, pop-ups, upsells, trackers and heatmaps, may add JavaScript that the phone has to download and run. Individually they seem small; together they are a common reason D2C stores feel sluggish, especially on taps, which shows up in INP.
Audit your apps and scripts. Remove anything you no longer use, and check that uninstalled apps have not left code behind in the theme, which is a frequent problem. For tools you keep, ask whether they need to load immediately. Chat widgets, review carousels lower on the page and some trackers can often load after the main content or on interaction.
Themes, fonts and layout
Themes packed with features you never use still load the code for them. A lighter, well-maintained theme can be faster than a heavily customised one. Keep the number of custom fonts and font weights low, and use system fonts for body text if your brand allows. Avoid sliders with many large images at the top of the home page; a single strong hero usually performs and converts better.
Layout shift often comes from banners, cookie bars and pop-ups that push content down after it appears, or from images without set dimensions. Reserve space for these elements or show them in a way that does not move the page.
Speed scores are a means, not the goal. Prioritise fixes that improve what real shoppers experience and that protect conversions, rather than chasing a perfect lab score.
Speed checklist
- Search Console Core Web Vitals report reviewed for mobile.
- Home, collection and top product pages tested in PageSpeed Insights.
- Main images compressed and correctly sized; hero not lazy-loaded.
- Unused apps removed and leftover theme code cleaned up.
- Non-essential scripts delayed until after load or interaction.
- Fonts limited to a few weights.
- Banners and pop-ups do not shift the layout.
- Tested on a real mid-range Android phone on mobile data.
Keep it fast
Stores tend to slow down again over time as new apps, campaign banners and tracking tags are added. Make speed part of the process: before installing any new app, check what it adds to the storefront and test the page before and after. Review the Core Web Vitals report monthly, and look again after any major theme change or seasonal campaign.
Where to start
Run PageSpeed Insights on your best-selling product page and list the largest problems. Remove unused apps, compress the main images and fix the hero image loading first; these often deliver the most visible gains. Then retest and watch the field data in Search Console over the following weeks. If you want a second view, Anadoris Digital can review your store’s speed with you.
Related service: Websites & Commerce · More on this topic: Websites & Commerce articles
