Slow website? Find what's slow before you upgrade the server

When a website gets slow, the first thing I usually hear is: "Should we just upgrade the server?" Sometimes that's right. But in most cases I see, the server isn't the bottleneck. After the upgrade the hosting bill doubles and the pages are just as slow.

Before spending money, answer one question: where is it slow? There are different kinds of slow, and each one has a different fix.

Is it the browser or the server?

Open the page in Chrome, press F12, pick the Network tab and reload. Look at the first row, the HTML page itself:

• If that row takes 2–3 seconds before anything comes back, the server is slow: the code, the database, or an overloaded machine.
• If the HTML arrives quickly but the page stays blank for a while, the browser side is slow: heavy images, too many scripts, fonts loaded from elsewhere.

The fixes are completely different, so this is always step one.

If the browser side is slow

The usual suspects, in order:

1. Images that are far too heavy. A 4–5 MB phone photo dropped straight onto the home page. Compressing it and switching to WebP usually saves a lot, with no visible difference.
2. Too many plugins and scripts. Chat widgets, ad pixels, sliders, pop-ups, each adding a little. Remove whatever nobody uses any more.
3. No browser caching and no compression. Check that the server has gzip or brotli turned on, and sends cache headers for images, CSS and JavaScript.

A quick free check: PageSpeed Insights. Don't chase a score of 100; read the "Opportunities" section to see what's heaviest.

If the server is slow

This is where people guess wrong most often.

• A missing database index. The orders table was a few thousand rows at launch and fast; a few years later it's millions of rows and crawling. The right index can fix the whole problem without touching the server.
• One query run hundreds of times for a single page. Very common in code written in a hurry: every product in a list triggers its own database call.
• No server-side caching. The home page rarely changes, yet every visit rebuilds it from scratch.
• The server really is short of resources. Watch RAM and CPU at busy times. If memory is always full and the server is swapping, then an upgrade helps.

Slow at the same time every day

If the site is only slow in the evening or at the start of the month, find out what runs then: a backup, a cron job, a big report, or simply your busiest hour. Moving heavy work to a quiet time can be enough.

The order I recommend

1. Measure, don't guess: server response time, PageSpeed score, the slowest queries.
2. Do the cheap fixes first: compress images, drop unused plugins, turn on caching.
3. Fix the database: indexes, repeated queries.
4. Only then think about a bigger server, and by then you know exactly what needs upgrading.

If you'd like to know where your own site is slow, I offer a free quick scan from the outside: SSL, page speed, security headers. For a proper look at the code and database, there's the 2–4 day Health Check.