Why Your Website Speed Is Costing You Customers

What the delay actually costs

The widely cited figure is that each additional second of load time costs roughly seven percent of conversions. Treat that as an order of magnitude rather than a law — it varies enormously by what you sell and how badly someone wants it. What holds across every study is the direction and the shape: the damage is worst in the first few seconds, and it compounds on mobile.

The number that matters more than the average is the one at the edges. Your analytics will report a mean load time that looks tolerable. The people abandoning are in the slow tail — older phones, weaker connections, further from your server. Optimising for the average leaves them exactly where they were.

Measure the right thing

Google grades three things, and only one of them is really about speed.

• Largest Contentful Paint — how long until the biggest thing on screen appears. Aim under 2.5 seconds. This is almost always an image problem.
• Interaction to Next Paint — how long the page takes to respond when someone taps. Aim under 200 milliseconds. This is almost always a JavaScript problem.
• Cumulative Layout Shift — how much the page jumps around while loading. Aim under 0.1. This is almost always a missing width and height attribute.

Test on a throttled mid-range Android over 4G, not on your own laptop on office wifi. The gap between those two is the entire problem.

The three fixes that account for most of the gain

We have run this checklist on enough builds to be confident about the order. In almost every case, three things account for the bulk of the improvement, and everything else is refinement.

First, images. On a typical business site images are the majority of page weight, and most of that is waste — a 2000-pixel-wide photograph displayed in a 600-pixel column, served as a PNG when it should be a JPEG or WebP. Serve responsive sizes, use modern formats, and lazy-load anything below the fold. This is usually the single biggest win available and it requires no architectural change.

Second, render-blocking resources. Fonts and stylesheets in the document head stop the page painting until they arrive. Fonts are the common offender: a stylesheet request to a third-party host, which then requests the font files, all before any text appears. Preconnect to the font host, use font-display: swap, and get the request off the critical path.

Third, JavaScript you are not using. Analytics, chat widgets, tag managers, A/B testing tools, three social embeds. Each was added for a reason and none were removed when the reason expired. Audit what actually loads and defer everything that is not needed for the first paint.

The layout shift nobody notices until they measure it

Cumulative Layout Shift is the cheapest of the three to fix and the most commonly ignored. Every image and video needs explicit width and height attributes — not CSS dimensions, the HTML attributes — so the browser can reserve the space before the file arrives.

Without them the text renders, the image arrives, and everything below it jumps down. If someone was mid-tap when that happened, they just tapped the wrong thing. That is the actual user cost of a metric that sounds abstract.

When speed is not your problem

Worth saying plainly: if your site loads in two seconds and converts badly, speed is not what is wrong. We have watched people spend weeks shaving milliseconds off a page whose real problem was that it never said what the company did.

Speed is a floor, not a lever. Below the floor it costs you customers you never see. Above it, the returns fall away quickly and your attention is better spent on the offer, the copy and the checkout.