Most slow WordPress sites are slow for the same five reasons, and they are worth fixing in order of impact. Aim for under three seconds on mobile data, which is the condition most South African visitors are actually browsing under.

Measure first

Run your homepage and your busiest service page through PageSpeed Insights and read the mobile score, not the desktop one.

Three numbers matter. Largest Contentful Paint should be under 2.5 seconds; it is when the main content appears. Interaction to Next Paint should be under 200ms; it is how quickly the page responds when tapped. Cumulative Layout Shift should be under 0.1; it measures content jumping about as things load.

Write the numbers down before you change anything, so you can tell what worked.

1. Images, which are usually most of the problem

The typical culprit is a 3MB photograph straight off a camera, displayed at 800 pixels wide. On mobile data that single image can cost several seconds.

Resize to the dimensions actually displayed, rarely more than 1,920 pixels wide. Convert to WebP, which is 25% to 35% smaller than JPEG at the same quality. Compress with a plugin such as ShortPixel, Imagify or Smush, which will also process your existing library in bulk. Enable lazy loading so images below the fold load only when scrolled to; WordPress does this natively now.

On most sites this step alone halves page weight.

2. Caching

Without caching, WordPress rebuilds every page from the database on every visit. Caching serves a pre-built copy instead.

WP Rocket is the easiest paid option, and LiteSpeed Cache is excellent and free if your host runs LiteSpeed, which many South African hosts do. W3 Total Cache and WP Super Cache are free alternatives.

Enable page caching, browser caching and GZIP or Brotli compression. Minification and combining of CSS and JavaScript are usually worth enabling too, but turn them on one at a time and check the site afterwards, because they can break layouts.

3. Plugin cleanup

Deactivating is not deleting. Go through the list and delete anything you are not using, including deactivated plugins, which remain a security exposure.

Watch particularly for page builders, sliders, multiple contact form plugins doing the same job, and social sharing plugins that load external scripts. One heavy slider can outweigh twenty light plugins.

Query Monitor will show you which plugins are actually consuming the load time, so you can act on evidence rather than guessing.

4. Hosting

If time to first byte is above 600ms, the server is the constraint and no plugin will rescue it. Cheap shared hosting packs hundreds of sites onto one machine and your site waits its turn.

Managed WordPress hosting in South Africa runs roughly R150 to R600 per month and typically cuts server response time substantially. Also confirm you are on PHP 8.1 or later, which is significantly faster than PHP 7 and is often a single setting in your control panel.

For a South African audience, a local server helps. For a mixed audience, a CDN matters more.

5. A CDN

A content delivery network serves your files from whichever location is nearest the visitor. Cloudflare's free tier is enough for most small business sites and adds caching, compression and basic security along the way.

Two more that are worth the half hour

Fonts. Every custom font weight is another download. Two weights of one family is usually plenty, and self-hosting them removes a third-party request.

The database. Post revisions, spam comments and expired transients accumulate. WP-Optimize will clean them, and setting a revision limit in wp-config.php stops it happening again.

Order of work

Step	Effort	Typical gain
Compress and convert images	1 to 2 hours	30% to 50%
Install and configure caching	30 minutes	20% to 40%
Delete unused plugins	1 hour	5% to 20%
Enable a CDN	1 hour	10% to 25%
Move hosting	Half a day	20% to 50%

Back up fully before you start, change one thing at a time, and remeasure after each change. If something breaks, you will know exactly what caused it.

Juicy Designs handles this as part of website maintenance and WordPress development. Related: Core Web Vitals in South Africa and why speed affects rankings.

Frequently asked questions

How do I speed up a slow WordPress website?

In order of impact: compress and convert images to WebP, install a caching plugin, remove plugins you do not use, move to better hosting, and enable a CDN. Images alone account for most of the weight on a typical South African WordPress site.

What load time should I aim for?

Under three seconds on mobile data, and under 2.5 seconds for Largest Contentful Paint. South African visitors are mostly on mobile networks, so a site that feels quick on office fibre may still be slow for the people buying from you.

Do plugins slow a site down?

The number matters less than what each one loads. A single page builder or slider can add more weight than twenty light plugins. Deactivating and deleting anything unused is still worth doing, because inactive plugins are also a security risk.

Is cheap hosting the problem?

Frequently. Shared hosting with hundreds of sites per server produces slow server response times that no plugin can fix. If your time to first byte is above 600ms, the host is the constraint.

Can I do this myself?

Most of it, yes. Image compression, caching and plugin cleanup need no code. Take a full backup first, change one thing at a time, and remeasure after each change.