Why is my website so slow? The three causes, and what fixing each one costs

Almost every slow small-business website we are asked to look at has one of three problems: images that are far bigger than they need to be, too many plugins and third-party scripts running on every page, or cheap hosting with a slow server. Occasionally it is a fourth thing, a heavy theme or page builder, and that one matters because it is the only one that tuning cannot fix. Knowing which you have is worth more than any plugin, so here is how to tell.

First, measure it properly

Do not judge speed from your own office computer. You have visited the site a thousand times, your browser has most of it cached, and you are probably on a fast connection. Your customers are on a phone, on mobile data, often in a car park or a kitchen.

Open Google’s PageSpeed Insights, paste your address, and look at the mobile tab. Ignore the big score for a moment and look at two things: the “Largest Contentful Paint” time, which is how long the main content takes to appear, and the list under “Diagnostics”. If LCP is over 2.5 seconds on mobile, your site is slow in Google’s eyes, and Google’s eyes are the ones that decide where you rank.

Cause one: images

This is the most common and the cheapest to fix. A photograph straight off a phone is 3,000 to 4,000 pixels wide and several megabytes. Your website displays it at perhaps 800 pixels. Every visitor downloads the whole thing anyway, and on a 4G connection that is seconds per image. A page with a hero photo, a team photo and six service tiles can easily be sending 15 megabytes to a phone.

How to spot it: in PageSpeed Insights, look for “Properly size images” and “Serve images in next-gen formats” in the diagnostics. If either shows savings measured in megabytes, this is you.

The fix is to resize every image to the largest size it is actually displayed at, compress it, and serve it in a modern format like WebP or AVIF, which is a fraction of the size at the same visible quality. On WordPress this can be automated for every future upload, which is the part people forget.

Cause two: plugins and scripts

Every plugin you install may add its own stylesheet and script to every page, whether or not that page uses it. A contact form plugin, a slider, a social feed, a pop-up, two analytics tools, a chat widget, a fonts service, a review widget: each is a few requests and a bit of code, and together they are the reason the page “hangs” after the text appears.

How to spot it: PageSpeed Insights will say “Reduce unused JavaScript”, “Reduce unused CSS” and “Eliminate render-blocking resources”, and the list underneath will be full of plugin folders and third-party domains.

The fix is partly housekeeping, deactivating and removing what you do not use, and partly technical: combining and deferring what remains so that the visible content is not waiting on a chat widget to download. Third-party scripts deserve a hard look. A Facebook pixel, a Hotjar recording, a Google Tag Manager container with twelve tags inside it: each is a call to another company’s servers before your page is finished.

Cause three: hosting

The time between a visitor’s browser asking for the page and the first byte arriving back is called Time to First Byte. Everything else waits on it. On a good host it is under half a second. On the cheapest shared hosting it can be two or three seconds, and it gets worse at busy times because you are sharing a server with hundreds of other sites.

How to spot it: PageSpeed Insights flags “Reduce initial server response time”. If that alone is over a second, images and plugins are not your main problem.

The fix is either a caching layer, so the server hands over a ready-made copy instead of building the page every time, or a better host, or both. If your server is on another continent from your customers, a content delivery network in front of it matters as much as the server itself.

The fourth thing: the theme

Some themes and page builders load so much machinery that a blank page takes three seconds before anything you added is counted. If PageSpeed shows a long list of files with the theme’s or builder’s name on them, and the fixes above only move the number a little, the honest answer is a rebuild on something lighter rather than another round of tuning. Anyone selling you a speed fix should tell you this before taking your money, not after.

What it costs to fix

Our website speed fix is $450 flat and covers all three common causes: images, scripts and caching, with the hosting checked and a recommendation if it is the bottleneck. We measure Core Web Vitals on your key pages on mobile before we start and again when we finish, and you get both reports. If the baseline shows the theme is the problem, we say so and quote a redesign instead, and you are not charged for the fix. Performance tuning is also included in our Standard and Priority care plans, so a fixed site stays fixed as you add content.