What studies say about page speed, abandonment and conversions, how to calculate what a slow site costs you, and what to fix first, with free tools to measure it in five minutes.

When someone taps the link to your site on their phone and nothing happens for a few seconds, they usually don’t wait. They close it and try another result. You never find out: in your analytics they don’t show up as a lost customer, they show up as one more visit that “didn’t convert”.
This article gathers what studies say about speed and abandonment, shows you how to calculate what a slow site may be costing you, how to measure it for free in five minutes, and what’s worth fixing first.
In short: a significant share of mobile visits leave if the page takes more than 3 seconds, and speed improvements are associated with more conversions. Before spending money, measure your site with PageSpeed Insights. Most often the problem is oversized images, third-party scripts and slow hosting, and all three can be fixed.
The most cited numbers come from Google research and a study with Deloitte. Worth knowing them, and reading them with nuance.
Abandonment. A 2016 Google study found that 53% of mobile visits are abandoned if the page takes more than 3 seconds to load.
Bounce. Another Google analysis from 2017, done on mobile online stores, calculated how much the probability of someone leaving without doing anything increases with load time:
| Load time on mobile | Increase in bounce probability |
|---|---|
| 1 to 3 seconds | +32% |
| 1 to 5 seconds | +90% |
| 1 to 10 seconds | +123% |
Conversions. The Milliseconds Make Millions study, carried out by Google and Deloitte with 37 brands in Europe and the United States, associated a 0.1 second improvement in mobile speed with 8.4% more retail conversions and 10.1% more in travel. On lead-generation sites (contact forms), the same improvement was associated with 21.6% more people reaching the form page.
How to read this data: these are large-sample studies with limitations. Many are from 2016 to 2019, they focus on stores, travel and mobile, and they show associations, not guarantees. It doesn’t mean speeding up your site will raise sales by an exact percentage. It does indicate that slowness has a real cost and is worth measuring.
The formula is simple:
Monthly visits × conversion rate × value per customer = revenue the site generates
An example with made-up numbers, just to illustrate:
| Slow website | Faster website | |
|---|---|---|
| Monthly visits | 1,000 | 1,000 |
| Conversion (inquiries that become customers) | 2% | 2.4% |
| Customers per month | 20 | 24 |
| Average value per customer | $200 | $200 |
| Monthly revenue | $4,000 | $4,800 |
A relative 20% improvement in conversion (from 2% to 2.4%) equals 4 more customers a month, about $800. It’s not a promise: it’s a way to put your own numbers on the table and decide how much it makes sense to invest in fixing speed. If your customer is worth $2,000 instead of $200, the math changes completely.
Google sums up the loading experience in three metrics called Core Web Vitals:
| Metric | What it measures | Good | Needs improvement | Poor |
|---|---|---|---|---|
| LCP (Largest Contentful Paint) | How long the main element takes to appear, usually the image or heading at the top | Up to 2.5 s | 2.5 to 4 s | Over 4 s |
| INP (Interaction to Next Paint) | How long the page takes to react when you tap or click | Up to 200 ms | 200 to 500 ms | Over 500 ms |
| CLS (Cumulative Layout Shift) | How much elements “jump” while loading | Up to 0.1 | 0.1 to 0.25 | Over 0.25 |
The first is most related to “takes too long to load”. The second and third explain that clumsy feel: buttons that don’t respond or text that moves right as you try to tap something.
You can also check the Core Web Vitals report in Google Search Console, which shows which pages on your site have problems.
| Cause | How it shows up | What to do |
|---|---|---|
| Oversized images | Photos that appear in pieces or take a while to display | Resize them to the size they’re actually displayed at, compress them and use modern formats like WebP or AVIF |
| Too many plugins or scripts | A site built with many extensions that always load | Remove what you don’t use and replace several plugins with one that does the essentials |
| Third-party scripts | Chats, ad pixels, maps and embedded videos | Review which ones add value and load the rest only when needed |
| Slow or overloaded hosting | The server takes a while to respond even though the content is light | Change plan or provider |
| No cache or content delivery network (CDN) | Every visit generates the page from scratch again | Enable caching and use a CDN, which serves content from a server close to the visitor |
| Too many fonts | Text that takes a while to appear or changes appearance as it loads | Stick to one or two families and few styles |
| Autoplay video | Heavy load the moment you land | Load the video only when the visitor asks for it |
It’s worth starting with what delivers the most for the least effort. The order and impact are indicative and vary from site to site.
| Action | Difficulty | Usual impact |
|---|---|---|
| Compress and resize images | Low | High |
| Remove plugins and scripts you don’t use | Low to medium | Medium to high |
| Defer images that aren’t visible on load (without applying it to the main image at the top) | Low | Medium |
| Review third-party scripts | Medium | Medium to high |
| Enable caching and a CDN | Medium | High |
| Change hosting if the current one is slow | Medium | High, if the server is the bottleneck |
| Reduce fonts | Medium | Low to medium |
If your site was built with WordPress or another content management system, much of this can be solved with settings and without rebuilding anything. It’s the kind of review that should be part of good website maintenance.
In most cases optimizing is enough. It’s worth considering a rebuild when:
Ask whoever reviews it for a written diagnosis: what problems they found, how much each one costs to fix and what improvement to expect. If they tell you it all has to be rebuilt without showing data, get a second opinion.
As a reference, Google considers an LCP of up to 2.5 seconds good. The less, the better, especially on mobile and with average connections. Rather than chasing a specific number, aim for the page to be usable quickly on your customers’ phones.
Google has said that page experience signals, including Core Web Vitals, are part of its ranking systems. Even so, content relevance carries more weight. A fast site with little useful content doesn’t rank better than a slower but highly relevant one, though speed helps break ties and, above all, helps you avoid losing visits.
Some things, yes: compress images, remove plugins you don’t use or disable an autoplay video. For caching, CDN, hosting changes or third-party scripts, it’s worth getting technical help, because a mistake can break the site.
After any important change (new design, plugin or integration) and, as a routine, every few months. Websites get heavier over time without anyone noticing.
A slow website rarely announces that it’s costing you customers. Measuring it takes five minutes, and the first improvements (images, plugins and scripts) are usually the cheapest and the most noticeable. If your site is already live, start there before thinking about a redesign.
In the next article we look at how to make your business show up when someone searches for what you offer in their area: local SEO for beginners.
Want me to check your website’s speed and tell you what to fix first? Write to me and we’ll take a look.
Abandonment and bounce data: Google research from 2016 and 2017. Conversion data: Google and Deloitte, Milliseconds Make Millions. These are large-sample studies, but they don’t guarantee the same effect for every business.
Subscribe to our newsletter!