What makes a WordPress site slow?

Most often: oversized images, page-builder output, too many plugins, heavy fonts, and third-party scripts like sliders, maps, chat widgets, and trackers. Hosting that makes every page wait for the server adds to it. The page weight piles up before the first useful content appears.

Will a caching plugin fix it?

Sometimes, partly. Caching helps when the site is fundamentally healthy and just badly tuned. It does not help much when the page is structurally heavy, because you are caching a heavy page faster, not making it light.

How fast should my site be?

On a normal phone, the first useful content should appear in a second or two, not after a spinner and a layout shift. A practical target is a page weight measured in hundreds of kilobytes, not megabytes, and a handful of requests before the hero is visible.

Should I optimise or rebuild?

Optimise when the site is basically healthy: good theme, sensible plugins, clear layout, just badly tuned assets. Rebuild when the site is structurally heavy, where every page is a page-builder composition carrying old CSS, plugin scripts, unused blocks, and a database roundtrip.

Guide

Why is my WordPress site so slow?

The usual suspects

The reasons are not exotic, and that is good news. Huge images that were never resized for mobile. Page-builder output that wraps every element in three extra layers. Too many plugins, each loading its own scripts. Heavy fonts in five weights. Sliders, maps, chat widgets, cookie banners, and tracking scripts that all want to load first. And hosting that makes every page wait for the server before anything renders.

Any one of these is survivable. Stacked together, they bury the content.

The fastest diagnosis

Open the site on a normal phone, not your laptop on office Wi-Fi. If the first screen takes ages, look at these five things.

How many megabytes the page loads. How many network requests happen before the hero is visible. Whether the hero image is correctly sized for mobile. Whether the fonts block the first render. And whether third-party scripts load before the content does.

You do not need to be technical to feel the answer. If the page makes you wait, your visitors are waiting too, and most of them will not.

Optimisation or rebuild

Optimisation is worth it when the site is basically healthy. A good theme, a sensible plugin stack, a clear layout, just badly tuned assets. Resize the images, drop the unused plugins, fix the fonts, and the site can get meaningfully faster.

A rebuild is smarter when the site is structurally heavy. If every page is a page-builder composition carrying old CSS, plugin scripts, unused blocks, and a database roundtrip, squeezing it harder is not the best use of money. At that point you are tuning the wrong machine.

The Aloha Smile approach

We keep the useful content and rebuild the surface. The result is a smaller page, fewer requests, a cleaner mobile layout, and a site that does not need a maintenance plan just to stay upright. The Orfanus rebuild went from 11 MB and 131 requests to roughly 0.2 MB and 11 requests. That is the kind of change visitors feel before they read a single word.

Want a real diagnosis?

Send your URL. We will tell you whether your WordPress site needs tuning or a clean rebuild.