Here is a number that should keep you up at night: a one-second delay in page load time can reduce conversions by 7%. For a site doing $100,000 per day in revenue, that is $2.5 million in lost sales per year. From one second.
Speed is not a technical detail. It is a business metric. And most companies treat it like a technical detail, which is why most companies have slow websites.
What the Data Actually Says
The relationship between page speed and conversions is not theoretical. It has been measured extensively, and the results are consistent across industries.
Google's Core Web Vitals program formalized the metrics that matter: Largest Contentful Paint (how fast the main content appears), Interaction to Next Paint (how responsive the page feels), and Cumulative Layout Shift (how visually stable the page is). These are not arbitrary benchmarks. They are based on years of research correlating user behavior with measurable performance indicators.
The pattern is straightforward:
- Pages that load in under 2 seconds have an average bounce rate around 9%
- At 5 seconds, bounce rates climb above 38%
- Beyond 6 seconds, you are losing more than half your visitors before they see your content
Google's industry benchmarks show that as page load time goes from 1 to 3 seconds, the probability of bounce increases 32%. From 1 to 5 seconds, it increases 90%. The curve is exponential, not linear. Every additional second of delay hurts more than the last.
Mobile Is Where Speed Matters Most
Desktop users on fast connections are relatively forgiving. Mobile users are not. They are on variable connections, smaller screens, and less powerful hardware. And they are increasingly the majority of your traffic.
Mobile devices now account for over half of all web traffic globally. But most sites are still designed and tested on desktop first, then responsively adapted for mobile. The result is sites that feel snappy on a developer's MacBook Pro and painfully slow on a mid-range Android phone on a 4G connection.
The performance gap between desktop and mobile is significant. A page that loads in 1.5 seconds on desktop might take 4-6 seconds on mobile due to larger JavaScript bundles, unoptimized images, and render-blocking resources. That is the difference between a converting visitor and a bounce.
What Actually Makes Sites Slow
Most slow sites are slow for predictable reasons. The usual suspects:
- Unoptimized images: A 3MB hero image that could be 200KB as a properly sized WebP file. This is the single most common performance issue on the web.
- Too much JavaScript: The HTTP Archive's Web Almanac reports that the median website ships over 500KB of JavaScript. Most of it is frameworks, analytics, chat widgets, and other third-party code that blocks rendering.
- No CDN: Serving assets from a single origin server means every user pays a latency tax based on their distance from that server. A CDN puts your content on edge nodes worldwide.
- Render-blocking resources: CSS and JavaScript files that must be downloaded and parsed before the browser can show anything. Moving non-critical resources to async loading can dramatically improve perceived performance.
- Server response time: A slow backend adds latency before the browser even starts rendering. Database queries, API calls, server-side processing... all of it adds up.
Measuring Performance the Right Way
You cannot improve what you do not measure, but you also cannot improve what you measure wrong. Synthetic tests (running Lighthouse from your office) tell you how fast the site is in ideal conditions. Real User Monitoring (RUM) tells you how fast it is for actual visitors.
Both matter, but RUM is closer to reality. Google's Core Web Vitals field measurement guidelines recommend tracking real-user performance data to understand how your site performs across different devices, networks, and geographies.
Key metrics to track:
- Largest Contentful Paint (LCP): Should be under 2.5 seconds. This is when the main content becomes visible.
- Interaction to Next Paint (INP): Should be under 200 milliseconds. This measures responsiveness to user input.
- Cumulative Layout Shift (CLS): Should be under 0.1. This measures visual stability; things jumping around as the page loads.
- Time to First Byte (TTFB): Should be under 800 milliseconds. This measures how quickly the server responds.
Practical Fixes That Move the Needle
Performance optimization does not have to be a massive overhaul. Often, a handful of targeted fixes deliver the majority of improvement.
Start with images. Convert to WebP or AVIF format. Use responsive image sizes so mobile users are not downloading desktop-sized images. Lazy-load images below the fold. This alone can cut page weight by 50% or more.
Audit your JavaScript. Remove unused libraries and polyfills. Defer or async-load third-party scripts. Consider whether that animated carousel really needs a 100KB JavaScript library or whether CSS animations would do the job. Every kilobyte of JavaScript has to be downloaded, parsed, compiled, and executed. None of those steps are free.
Use a CDN. Services like Cloudflare, Fastly, or Vercel's edge network put your content close to users worldwide. The performance improvement from a CDN is often the single biggest win for the least effort.
Preload critical resources. Tell the browser about important fonts, CSS, and above-the-fold images early so it can start fetching them before it discovers them in the HTML.
Consider your architecture. Static sites and pre-rendered pages eliminate server processing time entirely. Frameworks like Astro ship zero JavaScript by default, only hydrating interactive components. The result is dramatically faster pages without sacrificing developer experience.
Speed Is a Competitive Advantage
Your competitors' slow sites are an opportunity. When a potential customer is comparing three vendors and your site loads in under a second while the others take four seconds, you have already made a better first impression before they read a single word of your copy.
Speed also compounds. Faster pages get better search rankings because Google uses Core Web Vitals as a ranking signal. Better rankings mean more traffic. More traffic on a fast, converting site means more revenue. It is a virtuous cycle that starts with taking performance seriously.
The investment in performance pays for itself. Not eventually... quickly. If your site is slow and you fix it, the conversion improvement is usually visible within weeks. That makes it one of the highest-ROI improvements you can make to any website.
If you suspect your site speed is costing you conversions, let's run a performance audit and find the quick wins.