How to Fix a Slow Website: The Checks to Run, in Order

Your website is slow, and everyone has a different theory. The host blames your images, the theme blames your host, and the advice online tells you to fix everything at once. That approach burns time and money, because most slow sites are slow for two or three specific reasons, and the rest of the usual fixes change nothing. The checks below run in a deliberate order: measure first, then separate server problems from page problems, then fix the heaviest things the report actually names.

Check 1: Measure the page, on a phone, before you touch anything

Start with a number, not a feeling. Open the Website Speed Test and run your homepage, then run the page that matters most to your business, the one that takes bookings, sells the product or carries your contact form. Run the mobile test as well as the desktop one. Most of your visitors arrive on phones, and a page that feels fine on your office connection can crawl on a mid-range phone using mobile data.

Write down the score and, more importantly, the list of problems the report names. That list is your fix list. Every later check in this post exists to explain one of those items, and anything that is not on the list can safely wait its turn.

Check 2: Work out whether the server or the page is slow

A page load has two halves. First the server has to answer at all, then the browser has to download and assemble the page. A slow first half points at the server: overloaded shared hosting, no caching in place, or a database weighed down by plugins and old data. A fast answer followed by a slow page points at the page itself, meaning too much weight arriving after that quick first response.

This distinction decides where your money goes. If the server is the slow half, image work will not save you; caching or a better hosting plan will. If the server answers quickly, upgrading hosting changes nothing and the fix lives in the page. The speed report shows the server response time as its own figure, so read that line before anything else.

Check 3: Weigh the page, and start with the images

Images are the heaviest part of most pages, and the most common single cause of a slow site. The usual story is a photograph uploaded at full camera size, several megabytes, then displayed in a slot a fraction of that size. The browser downloads the whole file anyway. Resize each image to the largest size it is ever shown at, compress it, and let your platform serve modern image formats where it offers them.

After the images, count the extras. Every slider, popup, chat widget, social feed and tracking script adds files the browser must fetch and run before the page settles. You do not have to remove them all, but each one should be earning its place. Removing one heavy plugin often does more than a week of small tweaks.

Check 4: Hunt for the one broken thing

Sometimes a site is not heavy, it is stuck. One failing script that keeps retrying, an embedded video or map loaded on every page whether visitors use it or not, or a chain of redirects sending every visitor through two or three hops before the page even starts. Faults like these hide inside a generally healthy page, which is why the site feels slow in a way nobody can quite explain.

The speed report helps here as well: look at the largest and slowest individual items it lists, not just the totals. A single item that dwarfs everything around it is your suspect. Fix or remove that one thing, then retest before you move on to anything else.

Check 5: Retest the same page in the same way

After each fix, run the same test on the same page and compare it with the numbers you wrote down at the start. Change one thing at a time. If you change five things at once and the score improves, you will not know which change mattered, and if the score gets worse you will not know which one hurt. One fix, one retest sounds dull, but it is how a fix list actually gets finished instead of abandoned halfway.

What to do first

Run the speed test on your homepage today, mobile first, and write down the three biggest problems it names. Decide whether your trouble is the server half or the page half, then work through the three named items in order, retesting after each one. If the figures show the server is at fault, take them to your host and ask the question with evidence in hand. And once the site is fast again, an Uptime Monitor watching over it means the next slowdown or outage reaches you as a report, not as a customer complaint.