Why Your Website Is Slow (And the 5 Things That Usually Fix It)

"My site is slow." Every host's support team hears it daily. After looking at enough slow sites, the same patterns emerge. Nine times out of ten, it's one of these five things.

1. Oversized images (the runaway winner)

By a country mile, the most common reason a website is slow is that it's serving multi-megabyte images. We've seen homepages with a single hero image weighing 8 MB. On a phone over 4G, that's seven seconds before the page is usable.

Quick check: open your site, right-click an image and "open in new tab." If the file is over 500 KB, you've found the problem.

2. Too many plugins (or one badly behaved plugin)

Each WordPress plugin runs code on every page load. Some are tiny; some are entire applications. We've seen sites with 60+ plugins and 5 second response times that we got to under 1.5 seconds simply by removing the eight that weren't actually being used.

Tools like Query Monitor and the New Relic plugin will show you exactly which plugins are eating your response time.

3. No caching (or broken caching)

Every request to a WordPress site without caching does:

1. Boot PHP
2. Load WordPress core
3. Load every active plugin
4. Query the database multiple times
5. Render HTML

That's a lot of work to do the same thing for every visitor when 99% of your pages don't change between requests. A caching plugin saves the rendered HTML and serves it like a static file. Done well, page generation drops from 1500ms to 50ms.

4. An old PHP version

If your site is on PHP 7.2 or 7.4, you're running an unsupported version of PHP — and missing out on real performance gains. PHP 8.2 is roughly 25–30% faster on typical WordPress workloads. Most hosts will let you switch in one click. If yours doesn't, that's a sign to find a better host.

5. Cheap, oversubscribed shared hosting

"Unlimited everything for $1/month" comes from one place: stuffing thousands of sites onto a single underpowered server. When one of those sites gets a traffic spike, every other site on that server slows down. We see this all the time when a client moves to us from a discount host — same site, same code, same plugins, just a server that's not at 99% CPU all day.

How to actually diagnose your site

The free tools you need are:

• PageSpeed Insights — Google's view of your site, includes Core Web Vitals.
• GTmetrix — gives you a waterfall view so you can see what's loading and when.
• WebPageTest.org — more detailed, can test from different locations and connection speeds.

Run one or two of these. The waterfall tells you instantly whether you've got an image problem, a JavaScript problem, or a server problem. Image problems show as a tall stack of large bars in the network timeline. JavaScript problems show as a long "scripting" section after files have loaded. Server problems show as a long Time to First Byte (TTFB) — meaning the server took ages to respond at all.

The 80/20 fix list

If you have an hour and want most of the gains:

1. Compress and resize your top five images.
2. Deactivate any plugin you haven't used in three months.
3. Install a caching plugin and turn on page caching.
4. Switch PHP to 8.2 or 8.3 in your hosting control panel.
5. If TTFB is still over 800ms, the host is the bottleneck — start shopping.

Most slow websites can be made fast in an afternoon. The remaining 5% are genuinely complex and may need a developer. Don't assume you're in that 5% before you've tried the easy fixes.

If you're still stuck after working through these, our support team is happy to run a free audit and tell you exactly where your seconds are going. We do this for clients regularly — no obligation to switch.