Site speed is a revenue lever, not a technical nicety. On an e-commerce store, faster pages mean more of the people who arrive actually reach checkout — Google and Deloitte’s “Milliseconds Make Millions” study found that a 0.1-second improvement in mobile load time was associated with an 8.4% lift in retail conversions and a 9.2% increase in average order value (as of 2020). The fastest wins are usually the same three things: shrink your images, cache aggressively, and put your content closer to the user with a CDN. Everything else is refinement on top of those.
This guide covers what actually makes an e-commerce site slow, which metrics to measure, why the thresholds matter for ranking, and how to fix speed in priority order — including which hosting and delivery choices are worth paying for.
Key takeaways
- Speed drives conversions. Small load-time improvements compound into measurable revenue on high-traffic stores.
- Measure Core Web Vitals: aim for LCP under 2.5s, INP under 200ms, and CLS under 0.1 (Google’s “good” thresholds, as of 2025).
- Images and unoptimized media are the usual culprit. Fix them first — it’s the highest return for the least effort.
- A CDN plus caching plus good hosting handles the majority of speed problems for most stores.
- Test with field and lab data. PageSpeed Insights, GTmetrix, and WebPageTest each tell you something different.
What actually makes an e-commerce site slow?
Most slowness traces back to a short list of causes, and knowing which one you have saves you from optimizing the wrong thing. The usual offenders are oversized images and video, slow server response time (a weak host or an overloaded database), render-blocking scripts and heavy third-party tags, and too little caching so the server rebuilds the same page on every visit. E-commerce platforms make this worse than average because product pages pull in reviews, recommendation widgets, chat, and analytics — each an extra request that delays the moment the customer sees something usable.
The practical takeaway: don’t guess. A speed test will tell you whether your bottleneck is the image payload, the server, or the scripts, and each has a different fix.
Which metrics should you measure?
Track the metrics that reflect what a shopper actually experiences, not vanity numbers. Two categories matter.
Core Web Vitals — the ones Google ranks on
LCP (Largest Contentful Paint) measures loading: how long until the main content is visible. Target under 2.5 seconds. INP (Interaction to Next Paint) measures responsiveness: how quickly the page reacts to a tap or click. Target under 200 milliseconds. CLS (Cumulative Layout Shift) measures visual stability: how much the layout jumps as it loads. Target under 0.1. These are Google’s “good” thresholds as of 2025, assessed at the 75th percentile of real visits — meaning most of your traffic, not your best-case lab run, has to clear the bar.
Diagnostic metrics — the ones that tell you why
Time to First Byte (TTFB) exposes server and hosting speed; a slow TTFB points at the backend, not the front end. Total page weight and request count reveal how much you’re shipping and how many round-trips it takes. Watch these to locate the problem after Core Web Vitals tell you a problem exists.
Why Core Web Vitals matter beyond the score
Core Web Vitals are part of Google’s ranking signals, so a slow store can rank lower and get less organic traffic before a single conversion is even in play. But the ranking angle undersells it. The same thresholds that satisfy Google map onto real human patience: a page that paints fast, responds instantly to taps, and doesn’t shift under the shopper’s thumb simply feels trustworthy. A layout that jumps — pushing the “Add to cart” button just as someone reaches for it — erodes confidence and causes mis-taps. Hitting the vitals is where SEO and UX stop being separate projects and become the same work.
How do you make an e-commerce site faster?
Work in this order — it’s roughly highest-impact-per-effort first, so you bank the big wins before the fiddly ones.
- Optimize images and media. Compress every image, serve modern formats (AVIF/WebP), size them to their display slot, and lazy-load anything below the fold. On most stores this is the single biggest gain.
- Add a CDN. A content delivery network serves your static assets from a server near each visitor, cutting latency for shoppers far from your origin.
- Cache aggressively. Enable browser caching and full-page or object caching so the server stops rebuilding identical pages on every request.
- Upgrade hosting if TTFB is slow. If the backend is the bottleneck, no front-end tweak will fix it — move to faster, e-commerce-grade hosting.
- Trim and defer scripts. Minify CSS and JavaScript, remove render-blocking resources, and audit third-party tags — every marketing pixel and widget has a cost.
- Reserve space to stop layout shift. Set explicit dimensions for images, ads, and embeds so content doesn’t reflow as it loads, which protects your CLS.
Which speed tools should you use?
Use more than one, because each answers a different question. Google PageSpeed Insights combines lab data with real-world field data from the Chrome UX Report and grades you against the Core Web Vitals thresholds — start here. GTmetrix and WebPageTest give deeper lab diagnostics: waterfall charts that show exactly which asset delays the page and how requests stack up. Field data (real visits) tells you what customers actually endure; lab data (a controlled test) is repeatable and better for isolating a specific fix. Check both, and re-test after every change so you can prove the change helped rather than assuming it did.
Which delivery and hosting setup is worth paying for?
Match the investment to your traffic and where your customers are.
Shared or entry hosting + a free/low-cost CDN — best for: Small stores with modest, mostly local traffic. Lowest cost; fine until concurrency or distance starts hurting TTFB. Managed e-commerce hosting + a CDN — best for: Growing stores where downtime and slow response cost real sales. You pay more for performance, caching, and support tuned to commerce. Choose the upgrade when your TTFB is consistently slow under normal load or your customers are geographically spread; stay lean when traffic is light and local and image optimization plus caching already has you inside the vitals. Spend where the data says the bottleneck is — buying premium hosting won’t fix a page that’s slow because of a 5 MB hero image.
Frequently asked questions
What is a good page load time for e-commerce?
Rather than a single “load time” number, aim for Google’s Core Web Vitals: Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1 (as of 2025). Hitting these at the 75th percentile of real visits is the practical target because it reflects most of your shoppers, not just the fastest ones.
Does site speed affect SEO?
Yes. Core Web Vitals are part of Google’s ranking signals, so a faster, more stable store can rank better and earn more organic traffic. Speed also improves conversion once visitors arrive, so the SEO benefit and the revenue benefit reinforce each other.
What’s the fastest way to speed up my store?
Start with images — compress them, serve modern formats, size them correctly, and lazy-load below-the-fold media. Image weight is the most common bottleneck on e-commerce sites and usually the easiest big win. Then layer on caching and a CDN.
What causes cumulative layout shift?
CLS happens when content moves as the page loads — images without set dimensions, ads or embeds that push content down when they appear, or fonts that reflow text. Reserving explicit space for these elements before they load keeps the layout stable and protects the shopper from mis-tapping a button that jumped.