How to Speed Up Your Shopify Store (and Why It Lifts Conversion)

The fastest way to speed up a Shopify store is to remove what you don't need: uninstall dead apps and their leftover script tags, compress and lazy-load images, defer third-party scripts, and trim fonts. Do those four things and most stores see a meaningful improvement in load time, and because speed and conversion are tightly linked on mobile, the payoff shows up in revenue, not just in a PageSpeed score.
This guide walks through how to measure speed properly, the usual Shopify culprits, and the fixes in priority order so you spend effort where it counts.
Why Speed Equals Revenue in Mobile Commerce
Most e-commerce traffic is mobile, and mobile shoppers are impatient by necessity: they're on slower connections, weaker hardware, and shorter attention spans. Every second of delay gives someone a reason to bounce before your product even renders.
Speed compounds through the funnel:
- Discovery: Google uses page experience signals in ranking, so slow stores get less organic traffic to begin with.
- Engagement: Faster collection and product pages mean more pages viewed per session and more products considered.
- Trust: A laggy add-to-cart button or janky checkout feels broken, and shoppers don't enter card details on sites that feel broken.
In our own client work at Keplaris, Shopify builds that cut load times roughly in half have delivered conversion lifts of up to 40%. Speed isn't a vanity metric; it's one of the highest-leverage conversion levers you control.
How to Measure Speed Properly
Before changing anything, get a baseline, and make sure you're measuring the right thing.
Core Web Vitals: the metrics that matter
- LCP (Largest Contentful Paint): How long until the main content (usually your hero or product image) renders. Target: under 2.5 seconds.
- CLS (Cumulative Layout Shift): How much the page jumps around as it loads. Target: under 0.1.
- INP (Interaction to Next Paint): How quickly the page responds when shoppers tap, click, or type. Target: under 200 milliseconds.
Lab data vs. field data
Lab tools like Lighthouse run your page in a controlled, simulated environment. They're great for debugging, but they don't reflect what real shoppers experience. Field data (from the Chrome User Experience Report, visible in PageSpeed Insights and Google Search Console) shows how actual visitors experience your store across devices and networks.
The rule: diagnose with lab data, judge success with field data. A store can score 90+ in Lighthouse and still feel slow to real users on mid-range Android phones, which is exactly who you're losing.
Test your money pages, not just the homepage: a representative product page, a collection page, and the cart.
The Usual Shopify Culprits
Nearly every slow Shopify store we audit suffers from some combination of the following.
| Culprit | Typical impact | How to spot it |
|---|---|---|
| App bloat and leftover script tags | Extra JS on every page, slower INP | App list audit + theme code search |
| Oversized images | Slow LCP, wasted bandwidth | Network tab, PageSpeed image warnings |
| Heavy themes | Large CSS/JS bundles, slow first render | Lighthouse treemap, theme file sizes |
| Render-blocking third-party scripts | Delayed first paint, main-thread blocking | Waterfall view in DevTools |
| Too many fonts | Render delays, layout shift | Font requests in the network tab |
A few notes on the worst offenders:
- App bloat: Every app you install can inject scripts and stylesheets sitewide, even on pages where the app does nothing. Worse, many apps leave code behind after you uninstall them, so the cost lingers.
- Oversized images: A 4000-pixel-wide hero image served to a 390-pixel phone screen is pure waste, and it's usually your LCP element.
- Page builders and heavy themes: Drag-and-drop builders trade performance for convenience, often shipping enormous CSS and JS payloads to support flexibility you'll never use.
Fixes in Priority Order
Work top-down. The early items deliver the most improvement for the least effort.
1. Audit and remove dead apps
List every installed app and ask: does this make money or save real time? Uninstall the rest. Then search your theme code (look in theme.liquid and snippets) for leftover script tags and snippets from apps you removed long ago. This single pass often eliminates hundreds of kilobytes of JavaScript.
2. Optimize and lazy-load images
- Serve appropriately sized images using Shopify's image URL parameters and responsive
srcsetattributes. - Use modern formats (WebP/AVIF), which Shopify's CDN handles for you.
- Lazy-load everything below the fold, but never lazy-load your LCP image; give it priority instead.
- Set explicit width and height on images to prevent layout shift.
3. Theme-level fixes
Trim unused theme features, reduce CSS and JS bundle size, and preload critical assets like your hero image and primary font. If your theme is several years old and heavily modified, a rebuild on a modern, performance-focused theme architecture (such as Online Store 2.0 with lean sections) is often cheaper than endless patching.
4. Defer and audit third-party scripts
Analytics, chat widgets, review apps, heatmaps, and ad pixels all compete for the main thread. Load them with defer, delay non-essential scripts until after first interaction, and ask of each one: is the data or feature worth the milliseconds? Often the answer is no.
5. Limit fonts
Two font families, a couple of weights each, is plenty. Self-host or preload your primary font and use font-display: swap to avoid invisible text.
6. Be careful with page builders
If you use one, keep it to landing pages rather than templating your whole store with it, and test the performance cost of every new section before publishing.
When a Custom or Headless Build Makes Sense
Theme-level optimization has a ceiling. If you've done everything above and your field data still misses Core Web Vitals targets, or your roadmap demands experiences a theme can't deliver, it's time to consider a custom storefront.
Headless Shopify (a custom frontend, often built with Hydrogen or Next.js, talking to Shopify's APIs) gives you full control over what ships to the browser: no theme overhead, no app-injected scripts, and rendering strategies tuned to your catalog. The trade-off is real engineering investment, so it makes sense for stores where traffic and revenue justify it. We've seen this pay off directly: our Shopify Commerce case study covers a build where roughly 2x faster load times helped drive a significant conversion lift.
A custom build is the right call when:
- You've exhausted theme optimization and still miss your targets in field data.
- Your store has high traffic, where each fraction of a second compounds into revenue.
- You need storefront experiences (custom merchandising, complex bundles, internationalization) that fight against theme constraints.
Your Shopify Speed Checklist
- Baseline field data (PageSpeed Insights / Search Console) for product, collection, and cart pages
- Uninstall unused apps; remove leftover script tags from theme code
- Compress images, add
srcset, lazy-load below the fold, prioritize the LCP image - Set image dimensions to eliminate layout shift
- Defer or delay all non-critical third-party scripts
- Reduce font families and weights; preload the primary font
- Re-test after each change and track field data monthly
- If targets still aren't met, scope a custom or headless build
Conclusion
Speeding up a Shopify store isn't a mystery; it's a discipline. Measure with field data, remove what you don't need, optimize what you keep, and re-test relentlessly. The stores that win on mobile are the ones that respect their shoppers' time.
If you'd rather have experts handle it, Keplaris builds and optimizes Shopify storefronts for exactly this outcome. Take a look at our Shopify E-commerce service and let's talk about what a faster store would mean for your revenue.
Frequently asked questions
Start by removing unused apps and their leftover script tags, compress and lazy-load images, defer non-critical third-party scripts, and limit custom fonts. Measure with Core Web Vitals before and after each change so you know what actually moved the needle for real shoppers.
Yes. Slow pages cause shoppers, especially on mobile, to abandon before content loads, and sluggish interactions erode trust through the cart and checkout flow. Faster stores consistently convert better because more visitors reach product pages, add to cart, and complete checkout without friction.
Google considers Largest Contentful Paint (LCP) good at 2.5 seconds or less, measured at the 75th percentile of real user visits. For e-commerce, aim for your product and collection pages, not just the homepage, to hit that threshold on mid-range mobile devices.
They can. Each app may inject JavaScript and CSS into your theme, and many leave script tags behind after uninstalling. Audit your installed apps quarterly, remove anything you don't actively use, and check your theme code for orphaned snippets from old apps.
Consider headless when you've exhausted theme-level optimization and still need faster performance, or when you need custom storefront experiences a theme can't deliver. Headless adds engineering overhead, so it pays off most for high-traffic stores where small speed gains compound into real revenue.
Get in touch.
Whether you have questions or just want to explore what's possible, we're here to help.
