Why is my business website slow, and how do you fix it?

Why business websites are slow

Oversized images

A photo straight from a camera can be several megabytes. Served to a phone at full size, a few of them make a page crawl. They should be resized and served in modern formats like WebP or AVIF.

Too many scripts and plugins

Chat widgets, trackers, sliders, and plugins each add code that has to load before the page is usable. Many sites load dozens they no longer use. Third-party scripts are the worst offenders, because they load from someone else's server and you can't control how fast it answers. A chat widget or tracking tag that nobody checks anymore can add seconds on a phone.

Heavy themes and page builders

Drag-and-drop builders and all-in-one themes load a lot of code on every page, whether the page uses it or not. The page may only show a heading, three paragraphs, and a form, while the browser downloads the code for sliders, galleries, and animations used elsewhere on the site.

Slow hosting and no caching

Cheap shared hosting and no caching or CDN mean every visitor waits for the server to build the page from scratch. Caching stores a ready-made copy of each page, and a CDN keeps copies close to visitors around the world, so a customer in London isn't waiting on a server in Texas.

How website speed affects enquiries and Google

A slow website costs you in two ways. The first is visitors. Most people looking for a local service or comparing suppliers are on a phone, often on mobile data. If the page is still blank after a few seconds, many of them go back to the search results and click the next business. You never see those lost enquiries, because they never reach your contact form.

The second is Google. Google measures how fast your pages load for real visitors and uses it as part of how it ranks pages. Speed alone won't put a weak page on page one, but between two similar pages, the faster one has an edge. Faster pages also get crawled more efficiently, which helps larger sites get all their pages indexed.

That's why I treat speed as part of the build, not a fix at the end. It's far cheaper to keep a site fast than to rescue it later. On real projects, speed usually improves alongside other changes, so it's hard to credit it alone. But the pattern is consistent: the executive search site went from a Lighthouse performance score of 50 to 95+ in its rebuild, and enquiries rose from 7 to 20 in the first month.

Why a website is fast on a computer but slow on phones

This is the most common surprise. The site feels fine in the office, then a customer says it takes forever. Three reasons usually explain it:

• Weaker processors. Phones take longer to run the same code, so script-heavy pages suffer most.
• Mobile networks. A phone on patchy mobile data downloads far more slowly than an office connection.
• Desktop-sized images. Many sites send the same large images to phones as to big screens.

Google's speed targets are measured at the 75th percentile of real visits, so the slower quarter of your visitors, often phones on mobile data, decides whether a page passes. Always test the mobile result, and on a real phone away from office wifi.

How to check your website speed

Go to Google's PageSpeed Insights, paste your homepage URL, and look at the mobile result. Three numbers matter most:

• Largest Contentful Paint: how long the main content takes to appear. Under 2.5 seconds is good.
• Interaction to Next Paint: how quickly the page responds to a tap. Under 200 milliseconds is good.
• Cumulative Layout Shift: how much the page jumps around while loading. Under 0.1 is good.

If the report is hard to read, my free website health check runs the same Google test and explains each result in plain English, most important first.

Check your service or product pages too, not just the homepage. They're often slower, and they're where people decide. PageSpeed Insights shows two kinds of results: a lab test run once on a simulated phone, and field data from real visitors over the past month, if your site has enough traffic. When they disagree, trust the real-visitor numbers. The lab score is a guide for what to fix.

Real website speed fixes and their results

The aviation website kept every image; the fix was how they loaded. The consulting website kept its full Figma design, animations included.

How to fix a slow website

Work through it in this order, cheapest first:

• Resize and compress images, and switch to WebP or AVIF
• Remove plugins and scripts you don't use
• Load images and videos below the fold only when scrolled to
• Add caching and a CDN in front of the site
• Move to faster hosting if the server is the bottleneck

On a well-built site, these steps alone can get you most of the way. On a site built with a heavy theme or page builder, they often can't. The order matters because each step is cheaper than the next and often makes it unnecessary. Images are usually the biggest single weight on a page and the quickest to fix. Unused scripts come next, because they slow every page at once. Hosting comes last: paying for a faster server won't help much if every page is still sending megabytes of images and code. Measure again after each step, so you know what actually made the difference.

What fixing a slow website costs, and when to rebuild

It depends on where the weight is. Roughly, there are three levels:

• Quick fixes, like images, unused scripts, and caching: often a few days of work, and less than a redesign.
• A cleanup of a plugin-heavy site, including the theme and hosting: usually one to three weeks.
• A rebuild on the same pages and content, when the theme or builder itself is the problem: usually $7,000–18,000 over three to six weeks.

A short speed review, looking at your real-visitor data and the heaviest pages, tells you which level you're at before you spend anything. Speed also stays cheaper when it's protected: checking new images, plugins, and scripts before they go live stops the site from slowing down again a year later.

If the site is still slow after those fixes, the weight is usually baked into the theme or builder itself. A rebuild on the same URLs and content removes it at the source, and usually costs $7,000–18,000. See keep WordPress or rebuild and how much a website redesign costs.

Want to know what's slowing yours down? Send me the linkand I'll tell you what to fix first.