A slow WordPress site is rarely one big problem and almost always several small ones. Start by measuring, because optimising the wrong thing takes time and shows no result. Once you know where the time goes, the order of repairs is obvious.
Run the site through PageSpeed Insights and look at mobile and desktop separately. Pay attention to three numbers. How long the first server response takes, how long the largest content element takes to paint and how much the page jumps around while loading. These point to three different problems with three different fixes.
| Symptom | What it tells you | What to address |
|---|---|---|
| The server response is slow | The problem is on the server or in the database | Caching, the PHP version, the hosting tier |
| The page loads but paints slowly | The images or fonts are too heavy | Image compression and size |
| Content jumps while loading | Images are missing dimensions or ads push content around | Fixed dimensions on images |
An image uploaded straight from a camera or a stock library can be 4000 pixels wide and several megabytes, even though it is displayed at 800 pixels. The browser still downloads the whole file. Scale images to the size they are displayed at, save them as WebP and give every image a width and a height. This is often the single change that shows immediately.
Every plugin adds code that runs on every page load, and many load their own stylesheets and scripts on all pages even when they are needed on only one. Go through the plugin list and disable the ones that are not genuinely used. Two plugins doing the same job is a common finding, for example two caching plugins interfering with each other.
A cache stores the finished page so the server does not have to build it again for every visitor. The effect is large, but it does not fix heavy images or a broken site. It only hides part of the problem. Nordweb hosting comes with LiteSpeed Cache built in, so a separate caching plugin is neither needed nor advisable. Two caches at once produce faults that are hard to trace.
If the first server response takes more than a second even on an empty page, optimising inside the site will not help. Check the PHP version. A newer version is typically clearly faster than one from a few years back. Check the disk type as well. An NVMe disk and an old shared hard drive are different worlds for database queries. Read more about what makes hosting fast.
Do not install three optimisation plugins one after another hoping one of them helps. They overlap, break the layout and make the real cause harder to find. Make one change at a time and measure after each one.
We measure where the time actually goes and fix the causes in order of importance, rather than installing plugins blind. Speed optimisation is typically 2 to 4 hours for a small site, and you get an estimate before we start.
