A slow website does not announce itself. Nobody emails to say they left because a page took five seconds. The cost accumulates quietly in lost sales, wasted advertising spend, and search positions that drift down over months.
This article puts numbers to that cost, explains what is usually responsible, and sets out the fixes in order of return so you can start with the ones that matter.
What speed actually costs
The relationship between load time and abandonment is steep at the beginning. Moving from one to three seconds sharply increases the proportion of mobile visitors who leave, and by five seconds a large share are gone. Crucially, they leave before seeing your offer, so nothing else on the page gets a chance to work.
Three compounding effects follow:
Lost conversions. If a thousand people reach your site each month and 2 percent convert, that is twenty enquiries. A speed problem costing you a quarter of your mobile visitors is removing several of those before they read a word.
Wasted advertising. Paid traffic that bounces is money spent for nothing. You pay the same for a click that leaves in two seconds as for one that buys.
Search visibility. Core Web Vitals are a ranking factor. Their weight relative to content quality is modest, but they act as a tiebreaker between comparable pages, and mobile performance is assessed on the version Google indexes.
The measurements that matter
Three metrics tell you most of what you need:
- Largest Contentful Paint (LCP) is when the main content becomes visible. Target under 2.5 seconds. This is the number that correlates most closely with how fast the site feels.
- Interaction to Next Paint (INP) measures responsiveness when someone taps or clicks. Target under 200 milliseconds. Heavy JavaScript is the usual cause of failures here.
- Cumulative Layout Shift (CLS) measures how much the page jumps while loading. Target under 0.1. This is the reason people tap the wrong button on mobile.
Test with Google PageSpeed Insights, on mobile, on a page that matters commercially rather than only the homepage. Where available, look at field data from real visitors rather than the lab score alone.
What is usually responsible
Images, almost always
The most common single cause. A photograph straight from a phone can be several megabytes and four thousand pixels wide, displayed in a space eight hundred pixels across. Serving it at display size in a modern format such as WebP routinely cuts the file by eighty to ninety percent with no visible difference.
Third-party scripts
Analytics, chat widgets, heat mapping, advertising pixels, social embeds, review widgets, font services. Each is small in isolation; together they frequently outweigh the entire site. Every one of these also makes a request to another company’s server, and you inherit their response time.
Audit them honestly. Most sites carry at least one script installed for a campaign that ended two years ago.
Page builders and unused plugins
Visual builders load stylesheets and scripts for every feature they offer, whether or not the page uses them. Combined with a dozen plugins each loading their own assets on every page, this produces sites that download a great deal before showing anything.
Hosting
Cheap shared hosting places hundreds of sites on one server. When a neighbor has a traffic spike, your response time suffers. Server response time above roughly 600 milliseconds usually points here, and no amount of front-end optimization compensates for a slow server.
Web fonts
Fonts loaded from an external service add a connection to another domain and often delay text rendering. Self-hosting fonts and preloading the essential weights removes that delay entirely, and in the EU it also removes a data transfer that requires consent.
Fixes in order of return
- Compress and resize images, and serve modern formats. Usually the largest single improvement available, and it can often be done in an afternoon.
- Remove scripts you no longer use, and defer the ones you keep so they load after the content.
- Enable caching and a content delivery network. Serves repeat visitors and distant visitors far faster with modest configuration.
- Set explicit width and height on images and reserve space for embeds, which fixes most layout shift.
- Self-host fonts and preload the ones used above the fold.
- Lazy-load images below the fold, while explicitly not lazy-loading the main hero image, a common mistake that makes LCP worse.
- Upgrade hosting if server response time remains slow after the above.
- Reduce plugin count and reconsider the page builder if the site is still heavy. This is the largest job and belongs last.
When optimization is not the answer
Sometimes a site is slow because of how it was built, and each fix buys a little time before the next problem appears. Signals that a rebuild is the cheaper path: the page builder cannot be removed without rebuilding every page anyway, plugin conflicts break the site on updates, the theme has not been maintained in years, or you have already paid for optimization twice.
We look at the underlying build before recommending either route, and we will say when repair is the better value.
Frequently asked questions
What is a good load time?
Under 2.5 seconds for Largest Contentful Paint on mobile, measured on a mid-range device and a normal mobile connection rather than office wifi on a new laptop.
Does speed really affect Google rankings?
Yes, though less than content relevance. Think of it as a tiebreaker: between two pages that answer the question equally well, the faster one has an advantage. The larger effect is on conversion, which happens regardless of ranking.
Can I fix this myself?
Partly. Compressing images, removing unused plugins, and enabling a caching plugin are within reach of most site owners and often deliver a substantial share of the improvement. Server configuration, render-blocking resources, and JavaScript execution generally need a developer.
How long does a speed project take?
On a typical business site, one to two weeks covers images, scripts, caching, and layout shift. A rebuild is a different scale of project, but it resets the foundation instead of buying another year.
Start with a measurement
Run your most commercially important page through PageSpeed Insights on mobile and write down the three numbers. That takes two minutes and tells you whether this is a real problem or one you can leave alone. For a broader view covering speed alongside the rest of your technical setup, run the same page through SEO Lens.
Every site we build targets these thresholds as a delivery requirement rather than an optimization phase afterwards. See what that involves on the business website page, or send us your URL and we will tell you what is slowing it down and what we would fix first.
