Why speed matters more than ever
Speed has always mattered. What's changed is the bar. As mobile internet infrastructure has improved and competitor sites have gotten faster, user expectations have shifted upward. A page that loaded acceptably on a 3G connection in 2018 is now abandoned on a 4G connection in 2026. The users who might have tolerated a four-second load time seven years ago now bounce within two.
The commercial cost is concrete and measurable. A one-second delay in page response reduces conversions by 7%. An e-commerce site making £50,000 a month in revenue that cuts its load time from three seconds to two seconds can expect, on average, £3,500 in additional monthly revenue from that one change alone. That's not a projection from a vendor trying to sell you something. It's consistent across studies and industries.
Speed is also a ranking factor. Google has incorporated Core Web Vitals into its ranking algorithm, which means a slow site doesn't just lose conversions; it also ranks lower, getting less traffic to begin with. The compounding effect of being slow is worse than most site owners realise.
Core Web Vitals explained
Largest Contentful Paint (LCP) measures how long it takes for the largest visible element, usually the hero image or main heading, to appear on screen. Google's threshold for "good" is under 2.5 seconds. Most of the sites we audit fail this, primarily because of unoptimised hero images and unoptimised web fonts.
Cumulative Layout Shift (CLS) measures visual stability, showing how much the page layout jumps around while loading. A low CLS score means content doesn't move after it first renders; a high CLS score means things shift, which is disorienting and causes users to click the wrong element. The main culprits are images without specified dimensions, ads, and web fonts that load and swap in.
Interaction to Next Paint (INP) measures responsiveness, specifically how long it takes the page to respond after the user interacts with it. A slow INP makes a site feel sluggish even if it loaded quickly. Heavy JavaScript is almost always the cause.
The real cost of a slow site
Beyond the conversion rate data, slow sites carry a cost that's harder to quantify but equally real: they damage brand perception. A visitor who waits three seconds for a page to load has already formed a negative impression before they've seen a word of your content. That impression affects whether they trust the brand, whether they complete a purchase, and whether they come back.
The businesses most often surprised by this are ones whose internal team accesses the site on fast office broadband, where load times are consistently under a second. They've never experienced their own website the way a customer on a mid-range mobile device with a fluctuating connection experiences it. Running a Lighthouse audit on a simulated mobile network is usually the moment this becomes real.
"Every second of load time your site costs your visitors is a direct tax on your conversion rate. It's one of the only conversion problems that has a clear, fixable root cause."
What actually slows sites down
In order of frequency in the sites we audit: unoptimised images (large file sizes, wrong formats, no lazy loading), render-blocking resources (JavaScript and CSS that the browser has to download and parse before it can show the page), third-party scripts (analytics, chat widgets, marketing pixels that each add latency), and no CDN (serving assets from a single origin server that might be geographically distant from the visitor).
The good news is that the first two account for the majority of the problem in most sites. Fixing images, including converting to WebP or AVIF, adding proper dimensions, and implementing lazy loading, often cuts load time by 30-40% on its own. Deferring or removing render-blocking scripts is the second high-impact fix.
How to fix it
Start with Google PageSpeed Insights and GTmetrix to get a baseline. Both tools will give you a list of specific issues ordered by their impact on load time. Fix the biggest items first. For most sites, the priority order is:
- Convert images to next-gen formats (WebP/AVIF) and compress them
- Add width and height attributes to all images to prevent CLS
- Defer or remove render-blocking JavaScript
- Implement a CDN if you don't have one
- Audit third-party scripts and remove any that aren't earning their latency cost
- Implement lazy loading for below-the-fold images and iframes
A site that addresses these six points consistently reaches a load time under 2 seconds on mobile. A site under 2 seconds on mobile converts measurably better than one that doesn't. The investment in getting there is almost always recovered in the first month of improved conversion rates.
Measuring performance continuously
Speed is not a one-time fix. Every new feature, new plugin, new tracking script, and new image added to the site has the potential to degrade performance. The sites that maintain fast load times are the ones that measure continuously, either through automated Lighthouse CI in their deployment pipeline or through regular manual audits. Set a performance budget, track against it, and treat regressions with the same urgency as conversion rate drops.