Why Your Website Is Slow — And What It Costs You

1. Uncompressed images — the single most common cause

This is the top offender by a wide margin. Someone uploads photos straight off a phone or camera, each 3 to 8 MB, and the browser downloads all of them before the page finishes.

It is worth being concrete about scale. On this site, before we fixed it, the built asset folder was 23.5 MB — one logo alone was 7.3 MB, and the favicon, an icon displayed at 32 pixels, was 302 KB. After resizing each image to the size it is actually displayed at and recompressing, the whole folder came to 1.68 MB. Same images, same design, 93% less to download.

Fixing it needs no redesign: resize each image to the dimensions it is actually shown at, compress it, and serve modern formats such as WebP. Nothing about the page looks different afterwards.

2. Cheap oversold hosting

The cheapest shared hosting plans put hundreds of sites on one server competing for the same CPU and memory. Your pages then wait in a queue before the server even begins to respond.

The number to look at is Time To First Byte — how long the server takes to send anything at all. If that is already over a second, no amount of front-end work will save you, because the browser has not received a single byte yet. That is a hosting problem, and it is one of the cheaper things on this list to fix.

3. Plugin and script bloat

This one accumulates quietly. A chat widget, two analytics tools, a popup builder, a slider, a font library, a social feed — each seemed small, and together they are larger than the actual website.

Third-party scripts are especially costly because each one means a fresh DNS lookup and TLS handshake to another domain before it even starts downloading. Open your site and list every third-party feature on it. Anything you cannot name a business reason for should go.

4. No caching

Without cache headers, returning visitors re-download your logo, stylesheet and scripts on every single visit, even though nothing changed.

Configured properly, files with content-hashed names are cached for a year while the HTML itself is never cached, so deploys still reach people immediately. This is a configuration change, not development work, and it makes repeat visits dramatically faster.

How to check your own site in five minutes

• Run your URL through Google PageSpeed Insights and read the mobile score, not the desktop one — mobile is what Google ranks on
• Look at Largest Contentful Paint: under 2.5 seconds is good, over 4 is a problem
• Look at Cumulative Layout Shift: if it is high, your images are missing width and height attributes
• Check Time To First Byte — if that is slow, start with hosting
• Open your site on a phone on mobile data, not office WiFi. That is what your customers actually experience

What to fix first

Do images first. It is the cheapest fix with the biggest effect, and on most sites it alone moves the score from red to amber or green.

Then add width and height attributes to every image, which stops the layout jumping as things load. Then caching headers. Then audit third-party scripts. Only after all of that is it worth discussing hosting, and only if Time To First Byte says so.

Notice that a redesign is nowhere on this list. Slow sites are rarely slow because of how they look, and rebuilding a site to fix speed usually means paying for a new design to solve a problem the old one did not have.