WooCommerce Site Speed & Revenue Lost: The Real Numbers

I built the Revenue Leak Detector because this specific question kept coming up in WooCommerce groups and nobody could give a straight answer: how much money is my slow site actually costing me?

The research is there — Deloitte, Akamai, Shopify have all measured it. But the numbers are scattered across white papers and blog posts that never quite do the multiplication for a real store. This page does the multiplication.

The short version: a WooCommerce store doing $10,000/month and hosting on slow shared infrastructure is probably losing $200–300/month in abandoned conversions. Not "maybe." The published research says this is the floor.

Where the number comes from

The 0.4% conversion loss per 100ms of TTFB is the conservative end. It comes from multiple independent studies:

Deloitte Digital found 2.1% conversion lift per 100ms on desktop, 3.1% on mobile — for retail sites. That's the mid-range estimate, not the floor.

Shopify measured real revenue changes when they optimized merchant theme performance. Speed wasn't a UX perk — it was a conversion lever with a dollar sign on it.

Akamai found 7% conversion drop per 100ms of load time and a complete experience breakdown at 2 seconds.

Portent showed conversions falling off a cliff past 5 seconds of load time. The 1–3 second range is where most WooCommerce stores live — and where most of the revenue leak happens.

And now Google Core Web Vitals — LCP, INP, CLS — are ranking signals. So slow WooCommerce sites lose organic traffic before the visitor even lands on the page. That's a second revenue hit stacked on top of the first.

The actual math for a real store

Here's a WooCommerce store doing what thousands of stores do — 5,000 visitors a month, 2.5% conversion rate, $85 average order. Monthly revenue: $10,625.

Same store. Same products. The only thing that changed is which server answered the first request. At the conservative floor, that's $3,570/year walking out the door. The Deloitte numbers put it closer to $12,000–18,000/year.

Why WooCommerce makes this worse

Not every slow platform loses the same way. WooCommerce has specific patterns that pile up:

Add-to-cart is a server round-trip. Every "Add to Cart" button triggers an AJAX call to the backend. On a fast host, this feels instant. On slow shared hosting, customers start clicking twice — or leaving.

Checkout stacks page loads. Address → shipping → payment = three full-page reloads for most themes. At 500ms each, that's 1.5 seconds of pure waiting that a Shopify checkout doesn't have. The customer who bailed at step 2 never shows up in your analytics as a "failed checkout."

INP is the new silent killer. Google replaced First Input Delay with Interaction to Next Paint in 2024. 43% of sites fail INP. On WooCommerce stores, it usually hits the filtering, quantity updates, and checkout validation — moments where you need the server to respond fast.

Plugins compound the problem. Every plugin adds JavaScript. A WooCommerce store running a slider, a page builder, three analytics tools, and a popup is loading more code than the average single-page app. The server has to deliver all of it before the browser can do anything.

The cart fragment call. This is the one most store owners never see. WooCommerce makes an AJAX call to /?wc-ajax=get_refreshed_fragments on every single page load — product pages, blog posts, even the homepage — just to update the cart icon in the header. On a slow host, that call alone adds 200–400ms to every page view, and it happens whether the visitor has anything in the cart or not. You can verify this yourself: open your store, open DevTools Network tab, filter by "get_refreshed" and watch it fire on every navigation.

Checkout does full reloads, not AJAX. Unlike Shopify's single-page checkout, WooCommerce's default checkout submits the address form, waits for a full page reload, then shows shipping options, then reloads again for payment. That's three server responses at minimum. If your TTFB is 500ms, checkout alone takes 1.5 seconds of pure server wait time before the customer even sees the credit card field. Some themes and plugins (like Elementor's checkout widget) try to AJAX-ify this, but they often make INP worse by triggering DOM updates on every keystroke in the address fields.

What to do about it

I want to be honest about this: not every fix is free, and not every fix is worth the money for every store. The order below is what I'd prioritize based on ROI, not cost.

Measure before you fix. Run PageSpeed Insights on your product pages and WebPageTest on your checkout. If your TTFB is under 200ms, the host isn't the problem — it's theme/plugins. If it's over 600ms, the host is the problem and no amount of plugin optimization will fix it.

The first line is the one most store owners skip because it means changing the bill. But a $15/mo increase that recovers $200/mo in lost conversions isn't a cost — it's the highest-ROI move you'll make all year.

Further reading

• Cloudways vs SiteGround TCO — real 3-year cost comparison including revenue impact
• Best WooCommerce Hosting 2026 — the full ranking of 8 hosts by speed and cost
• Fastest WooCommerce Hosting TTFB — real-world TTFB benchmarks for 8 hosts
• How Slow Hosting Costs You Sales — the general TTFB → revenue math
• What Is Price-Lock Hosting? — hosts that don't spike at renewal
• Hostinger Renewal Price Shock — budget host renewal math
• IONOS Renewal Price Shock — the steepest jump we measured: $1 to $14