Why Is My Website Slow? The Five Causes and the Fixes That Actually Matter

You know the site is slow because you have watched customers wait for it, and because you have waited for it yourself in a parking lot on your phone. What you do not know is why, because the designer says it is fine on their computer and the hosting company says the server is fine. Both are probably telling the truth, and the site is still slow.

Here are the five things that make small business websites slow, in the order we find them when we audit a site, how to check each one yourself, and which fixes are worth the money. If you want the short version first, our free website grader gives a 0 to 100 speed score with the main problems listed, in about a minute.

Why it matters

Two reasons. Visitors on a phone leave slow pages, and most of your visitors are on a phone. And Google measures page speed for real visitors and uses it as a ranking signal, so a slow site ranks below a fast one with the same content. A site that takes six seconds to show anything is losing customers twice.

1. Images that are far too big

This is the cause on most slow sites, and it is the cheapest to fix. A photo straight from a phone is 3 to 5 megabytes and 4,000 pixels wide. The space it fills on the page is 800 pixels wide and should weigh 80 kilobytes. Upload ten of those photos to a homepage and the page is 40 megabytes, which on a cell connection is a long wait for a hero image.

Check: right click a photo on your homepage and open it in a new tab. If the image is bigger than your screen, it is too big.

Fix: resize every image to the size it is displayed at, save it in a modern format such as WebP, and load the ones below the fold only when the visitor scrolls to them. On the sites we build this is automatic: every image is served at several sizes and the browser picks the smallest one that fits.

2. Too many plugins and scripts

Each plugin on a WordPress site, and each third party script anywhere, adds code the visitor's phone has to download and run: a slider, a form builder, a chat widget, a social feed, three analytics tags, a fonts service, an accessibility overlay, a popup tool. Individually small, together they are often the biggest thing on the page, and several load before anything is visible.

Check: count the plugins on the site. Over fifteen is a warning. Then open the page and count the spinning, sliding and popping things.

Fix: remove what is not earning its place. Most sites can lose a third of their plugins with no visible change. Load the rest after the page is visible, not before. Be especially suspicious of anything that promises to make the site faster, which usually adds another script.

3. A heavy theme or page builder

Many WordPress sites are built on a theme designed to do everything, with a drag and drop builder on top. The result is a page that carries the code for hundreds of features it does not use, and a layout wrapped in a dozen layers of containers. The site looks fine and loads like a truck.

Check: if the site was built with a page builder, this is probably part of the problem. If the page still feels slow after images and plugins are fixed, this is the rest.

Fix: this one often cannot be patched. A theme that is slow by design stays slow. The honest fix is a rebuild on a lighter foundation, which is why speed is usually the best argument for a redesign, and why we build many sites static now. The comparison is in WordPress vs. a static website.

4. Slow hosting

Cheap shared hosting puts hundreds of sites on one server. At busy times, yours waits. Even when it does not, the server can take a second or more to begin responding, before a single byte of your page is sent.

Check: look for "time to first byte" in a speed test. Over about 600 milliseconds, and especially over a second, is the host.

Fix: better hosting, or a content delivery network that serves your pages from a server near the visitor. The sites we host are served this way. Our hosting and maintenance plan is $200 a month and keeping the site fast is part of it.

5. No caching and no compression

Without caching, a WordPress site rebuilds every page from the database for every visitor. Without compression, it sends text files at several times the size they need to be. Both are settings, not rebuilds.

Check: if the site is on WordPress and nobody has set up caching, it is not set up.

Fix: a caching layer, text compression and long cache lifetimes for images and scripts. On a static site this is largely built in, because there is nothing to rebuild: the pages are already files.

The things that do not help much

A faster computer in your office. Another plugin that promises speed. Upgrading the hosting while leaving 40 megabytes of images on the homepage. Turning off the one slider while leaving the page builder. Speed comes from having less to load. Everything else is rearranging the wait.

How to test properly

1. Test on a phone, over a cell connection, not on the office Wi-Fi. That is your customer's experience.
2. Use the free website grader for the plain score and the main problems, and Google's PageSpeed Insights for the full technical list. Pay attention to the mobile result, not the desktop one.
3. Note the number, make one change, test again. Start with images, because it is the cheapest fix with the biggest gain.
4. If the site is still slow after images, plugins and caching, the theme or the host is the rest, and those are the two that usually mean a rebuild or a move.

If you would rather have someone else find out, send us the site's address. We will tell you what is slowing it, what is fixable in place and what is not, in writing, and Jason replies in under 24 hours. Keeping a site fast after that is part of what maintenance should include.