How Website Speed Affects E-commerce Conversion Rates (And How to Fix It)

Key Takeaways

• A 100ms delay in page load time can reduce e-commerce conversion rates by up to 1%, according to Deloitte research commissioned by Google.
• Google data shows that as page load time increases from 1s to 3s, the probability of a mobile visitor bouncing increases by 32% — and by 90% when load time rises to 5 seconds.
• UK e-commerce is worth over £130 billion annually (ONS Retail Sales 2024), meaning even a fractional improvement in conversion rate has a significant revenue impact for established stores.
• The most impactful speed improvements for most e-commerce sites are: image optimisation, eliminating render-blocking scripts, and upgrading to a faster hosting tier — often achievable without a full rebuild.

Why Website Speed Is a Revenue Issue, Not Just a Technical One

When e-commerce businesses talk about improving conversions, the conversation usually goes straight to copywriting, product photography, or checkout flow. Rarely does it start with page load time. That's a mistake.

Speed is not a nice-to-have feature. It is the precondition for every other conversion optimisation strategy. If your page takes five seconds to load on a mobile network, your customers are not reading your product descriptions or evaluating your trust signals — they've already left.

The relationship between speed and conversion is well-documented, but the numbers are still striking when you see them clearly. Deloitte, working with Google, analysed the performance of 37 retail and travel brand websites and found that a 0.1-second improvement in site speed improved conversion rates by 8% for retail sites. That's not a marginal improvement — that's a meaningful revenue shift from a sub-second change.

This guide explains how speed affects e-commerce conversions, what metrics matter, and what you can actually do about it — without necessarily rebuilding your entire site.

What Is the Relationship Between Page Speed and Conversion Rate?

The Core Mechanics

When a customer lands on a slow e-commerce page, several things happen:

1. Bounce rate increases — customers leave before the page finishes loading
2. Engagement drops — even customers who wait are less likely to scroll, add to cart, or complete a purchase
3. Trust erodes — a slow site signals unreliability, particularly on payment pages
4. Return visits decrease — a bad first experience reduces the likelihood of a return visit

The compounding effect matters. A customer who bounces from a slow product page never sees your USPs, never trusts your checkout, and may actively leave a negative review mentioning "the website was slow." The cost of that lost sale is not just the immediate transaction — it's the lifetime value of that customer.

What Does the Data Say for UK E-commerce?

UK shoppers are increasingly mobile-first. Statista data for 2024 shows that over 60% of UK online retail browsing now happens on mobile devices, and mobile conversion rates consistently lag desktop by 30–40% in most sectors.

Mobile networks — even 4G and 5G — introduce latency that desktop connections do not. A page that loads in 1.5 seconds on a fibre broadband connection may take 3.5 seconds on a 4G mobile connection. The performance gap between desktop and mobile is almost entirely a speed problem.

For UK e-commerce businesses, this means the mobile speed problem is also the conversion problem. Fixing one fixes the other.

Which Speed Metrics Actually Matter for E-commerce?

Not all performance metrics are equally important for conversions. Focus on these four:

What Is Time to First Byte (TTFB)?

TTFB measures how long it takes for the browser to receive the first byte of data from the server after making a request. It is a measure of server responsiveness.

For e-commerce sites, a TTFB above 800ms is a red flag. The causes are usually: slow hosting, database queries without caching, or unoptimised server-side rendering. TTFB is invisible to the user — they see a blank screen — but it is the foundation of every other metric.

A good TTFB target for e-commerce is under 400ms for cached pages, under 800ms for dynamic pages (e.g., personalised product recommendations).

What Is Largest Contentful Paint (LCP)?

LCP measures how long it takes for the largest visible element on the page to render — typically a product hero image or a banner. Google uses LCP as one of its Core Web Vitals, and it is the most user-visible of the speed metrics.

For e-commerce, LCP is almost always an image problem. Large, uncompressed product images or hero banners that are not preloaded are the most common culprits. Google considers an LCP under 2.5 seconds "good" — above 4 seconds is "poor."

Read our full explanation of Core Web Vitals for a deeper breakdown of how these metrics are measured and what they mean for search rankings.

What Is Cumulative Layout Shift (CLS)?

CLS measures visual instability — how much the page layout shifts as it loads. On e-commerce sites, this commonly happens when fonts, banners, or cookie consent notices load late and push content down the page.

CLS is particularly damaging to conversions because it causes customers to accidentally tap the wrong element (especially on mobile). A customer reaching for "Add to Cart" who accidentally taps an ad or a competing link has a frustrating experience that rarely ends in a purchase.

What Is Interaction to Next Paint (INP)?

INP measures responsiveness — how quickly the page reacts when a user taps a button or interacts with a filter or dropdown. For e-commerce sites with product filtering, variant selection (size, colour), and quantity inputs, INP is directly tied to the usability of the shopping experience.

Google replaced First Input Delay (FID) with INP as a Core Web Vital in March 2024. An INP below 200ms is considered good.

What Are the Most Common Speed Problems on E-commerce Sites?

Unoptimised Product Images

Product photography is the lifeblood of e-commerce. It is also the most common source of page weight. A single product image saved from Photoshop as a 4MB JPEG and dropped straight into a product listing page can add seconds to load time.

Next.js, which we use for Brambla client projects, handles much of this automatically via the `<Image>` component — serving WebP/AVIF, applying lazy loading, and preventing layout shift out of the box.

Render-Blocking JavaScript and CSS

Most e-commerce sites accumulate third-party scripts over time: analytics, chat widgets, affiliate tracking, retargeting pixels, consent management platforms. Each script that loads in the `<head>` of your HTML blocks the browser from rendering the page until it has been downloaded and parsed.

No Content Delivery Network (CDN)

If your e-commerce site is hosted on a single server in London and a customer in Edinburgh requests your homepage, that request travels from Edinburgh to London and back. At scale, across thousands of concurrent visitors, server proximity matters.

A CDN distributes your static assets (images, CSS, JavaScript) across a global network of edge servers, so customers load assets from a server close to them. For UK e-commerce with customers across the country — and potentially across Europe — a CDN reduces asset load time significantly.

Cloudflare's free tier is adequate for most small to medium e-commerce sites. Vercel and Netlify include CDN distribution as part of their hosting infrastructure.

Slow Hosting

Shared hosting — where your site shares server resources with hundreds or thousands of other sites — is cheap for a reason. Under traffic load, shared hosting servers throttle performance to prevent any single site from monopolising resources. The result is high TTFB and unpredictable performance under load.

For e-commerce sites with meaningful traffic, managed hosting or cloud hosting (AWS, Google Cloud, Vercel, Kinsta) provides dedicated resources and predictable performance. The cost difference is often £20–50 per month — a fraction of the revenue impact of lost conversions.

Our SiteCare plans include managed hosting on infrastructure built for performance, not just availability.

Excessive App and Plugin Load (Shopify and WooCommerce)

Shopify and WooCommerce both allow you to extend functionality through apps and plugins. The problem is that many apps add their own JavaScript to every page — including pages where the app's functionality is irrelevant.

A Shopify store with 15 active apps may be loading 15 additional scripts on every product page. Each script adds network requests, parse time, and execution overhead.

For a deeper comparison of platform performance trade-offs, see our guide to Shopify vs WooCommerce vs custom build.

How Do You Measure E-commerce Speed Performance?

Free Tools

Google PageSpeed Insights (pagespeed.web.dev) — runs your page through Google's Lighthouse engine and returns LCP, CLS, INP scores alongside actionable recommendations. Test your homepage, a key category page, and a product page — they often have different performance profiles.

Google Search Console — the Core Web Vitals report shows real-world performance data for your URLs, grouped into Good, Needs Improvement, and Poor. This is field data (real users, real devices) rather than lab data — it's what Google actually sees.

WebPageTest (webpagetest.org) — allows you to test from specific locations and connection speeds, including a simulated 4G mobile network from a UK data centre. Invaluable for understanding mobile performance.

Lighthouse — built into Chrome DevTools (F12 > Lighthouse tab). Run it in incognito mode to avoid extension interference.

What Are the Quick Wins for E-commerce Speed?

If you need to improve performance without a full rebuild, prioritise these in order of impact — for a full walkthrough of every optimisation technique available, see our complete page speed optimisation guide:

1. Image optimisation — Compress and convert images to WebP. Use Squoosh for manual optimisation or configure your CMS to automate conversion. Expected impact: 30–60% reduction in page weight.

2. Enable browser caching — Configure your server to set cache headers so returning visitors load your site from their browser cache rather than making new server requests. Expected impact: near-instant page loads for return visitors.

3. Minify CSS and JavaScript — Remove whitespace, comments, and redundant characters from your CSS and JS files. Most build tools (Webpack, Vite) do this automatically; older sites may need it configured manually.

4. Remove unused scripts — Audit your `<head>` for third-party scripts you're no longer actively using. Each removal reduces network requests and parse time.

5. Upgrade hosting — If you're on shared hosting, moving to a managed cloud host is often the single highest-impact change you can make for TTFB.

6. Implement lazy loading — Add `loading="lazy"` to below-the-fold images. This is a one-line HTML change that can meaningfully reduce initial page weight.

When Is a Full Rebuild the Right Answer?

Quick wins have limits. If your e-commerce platform is fundamentally slow — if the theme is bloated, the architecture is outdated, or the platform itself imposes structural performance constraints — incremental fixes will only take you so far.

Signs that a rebuild may be warranted:

• PageSpeed Insights consistently scores below 40 on mobile despite implementing standard optimisations
• Your TTFB is above 1.5 seconds on good hosting
• Your platform (e.g., a heavily customised WooCommerce install from 2017) can't support modern image formats or lazy loading without significant workarounds
• Your developer's response to every speed question is "that's just how this platform works"

A custom-built e-commerce site — or a properly architected Shopify/Next.js Commerce build — can achieve LCP under 1.5s and PageSpeed scores above 90 on mobile. If you're considering a purpose-built solution, take a look at our e-commerce web design service. If your current site is scoring 28, the gap between you and your competitors is not a marketing problem. It's a technical one.

A website audit is the right starting point — it gives you a clear picture of what's holding your speed back and whether it's fixable or rebuild-worthy. For sites where the performance issues are signs of broader problems, our guide on signs your website is costing you customers covers the full picture.

The UK E-commerce Speed Benchmark

Based on HTTP Archive data for 2024, the median UK e-commerce site has an LCP of approximately 3.8 seconds on mobile — squarely in Google's "Needs Improvement" range.

That means if your e-commerce site loads in under 2.5 seconds on mobile, you are already outperforming the majority of your UK competitors on this metric. If your site loads in under 1.5 seconds, you are in the top tier — and that speed advantage will show in conversion rates, bounce rates, and search rankings.

Speed is one of the few competitive advantages that is entirely within your control, doesn't require a marketing budget, and compounds over time.

Frequently Asked Questions

How much does website speed actually affect my revenue?

The Deloitte/Google research found that a 0.1-second improvement in page speed correlated with an 8% increase in conversion rate for retail sites. For a business turning over £500,000 in online revenue, that's a potential £40,000 revenue uplift from a sub-second speed improvement. The exact figure varies by sector and traffic volume, but the direction is consistent: faster equals more revenue.

What is a good PageSpeed score for e-commerce?

Aim for 75+ on mobile in Google PageSpeed Insights as a realistic target for e-commerce sites (which are inherently heavier than brochure sites due to product images and dynamic content). Above 90 is excellent. Below 50 on mobile is a meaningful conversion and ranking risk.

Does website speed affect Google rankings?

Yes. Page speed is a confirmed ranking factor for both mobile and desktop search. Google's Core Web Vitals (LCP, CLS, INP) are used as ranking signals. A site with "Poor" Core Web Vitals may rank below a slower-growing competitor with better technical performance, all else being equal.

Is Shopify slower than a custom-built site?

Shopify's infrastructure is excellent — TTFB is fast, CDN is global, and uptime is reliable. The speed problem on Shopify is usually at the theme and app layer, not the platform layer. A lean Shopify theme with few apps can be very fast. A heavily customised theme with 20 apps loading on every page will be slow regardless of the platform. Custom builds, done well, offer more control over the full performance stack.

How often should I check my site speed?

Check your Core Web Vitals in Search Console monthly as a baseline. Run a full PageSpeed Insights audit quarterly, and after any significant site changes (new theme, new apps, new third-party integrations). Speed tends to degrade gradually as sites accumulate scripts and content — regular monitoring catches the drift early.

Can I improve speed without a developer?

Some optimisations are available to non-developers: compressing images before upload, removing unused apps, and enabling built-in caching features in your CMS. But the higher-impact fixes — minifying code, configuring CDN, implementing server-side rendering, or refactoring slow database queries — require developer involvement. A website audit will tell you which category your issues fall into.

Related Reading

• Core Web Vitals Explained: What They Are and Why They Matter
• Shopify vs WooCommerce vs Custom: Which Platform Is Right for Your Business?
• Signs Your Website Is Costing You Customers
• How Much Does a Website Cost in the UK?
• Page Speed Optimisation: The Complete Guide

Want a Faster E-commerce Site That Actually Converts?

Speed is not a technical problem sitting separate from your business goals — it is your business. Every second of load time that you shave off is potential revenue recovered, customers retained, and rankings improved.

At Brambla, we build e-commerce websites that are engineered for performance from the ground up — not retrofitted with speed fixes after the fact. Every web design project we deliver is tested against Core Web Vitals before launch. If you want to understand exactly what's holding your current site back, start with a website audit — or if you're ready to discuss a rebuild, get in touch, or view our pricing to find the right package.