To speed up a WordPress website, measure first, then fix the causes in order of size: make sure exactly one page cache is running, resize and compress your images (and never lazy-load the main one), remove the scripts and plugins you do not need, run a current PHP version, and serve the site from close to your South African visitors. The target is Google’s Core Web Vitals: the main content showing within 2.5 seconds, the page responding to a tap within 200 milliseconds, and layout shift of 0.1 or less.
Below are the six steps in that order, what each one fixes, and how to tell whether it worked. Faster pages help rankings a little, and they usually help conversions more, so the same work pays off whether your visitors come from Google search or from ads. Speed is part of the technical work in our SEO service; this guide is for doing it yourself.

Step 1: Measure before you change anything
Test your homepage and your two or three most important pages, not just one. Use these:
- PageSpeed Insights (pagespeed.web.dev). The top section shows real-visitor data when Google has enough of it; that is what Google uses. The Lighthouse test below it is a lab run for finding causes.
- Search Console’s Core Web Vitals report, under Experience. It groups pages that share a problem, so you fix a template once instead of page by page. Small sites often see “No data available”; then rely on the lab tools.
- GTmetrix or WebPageTest for a waterfall: the list of every file the page loads, in order, with its size and time. Pick a test location as close to South Africa as the tool allows, or the results will flatter or punish your hosting unfairly.
Write down four numbers per page: LCP, CLS, Total Blocking Time (the lab stand-in for responsiveness) and server response time (TTFB). Google’s web.dev guidance suggests a TTFB of 0.8 seconds or less as a rough target. If yours is well above that, start with Step 6; no plugin will fix a slow server.

Which number points to which fix
| What the test shows | Most likely cause | Where to start |
|---|---|---|
| High TTFB (well over 0.8 s) | Slow or distant server, no page cache | Steps 2 and 6 |
| Slow LCP (over 2.5 s) | A large hero image or video, or the main image being lazy-loaded | Step 3 |
| High Total Blocking Time, poor INP | Too much JavaScript: chat widgets, page builders, sliders, trackers | Step 4 |
| CLS over 0.1 | Images without width and height, late-loading fonts, banners pushing content down | Step 3, then fonts and banners |
| Slow only in the WordPress admin | Too many plugins, old PHP, database clutter | Step 5 |
Step 2: Run exactly one page cache
Without caching, WordPress builds every page from the database for every visitor. A page cache stores the finished page and serves that instead, which is usually the biggest single cut in server response time.
- Check your host first. Many managed WordPress plans already cache at server level. Adding a caching plugin on top can conflict with it; your host’s help pages will say which plugin, if any, to use.
- Use one caching plugin, not two. xneelo’s own WordPress guidance says the same. Common choices are LiteSpeed Cache (only if your host runs a LiteSpeed server), WP Super Cache, W3 Total Cache and WP Rocket (paid).
- Clear the cache after changes to content, theme or plugins, then test again as a logged-out visitor. Logged-in pages are usually not cached, so testing while signed in shows the slow version.
Step 3: Fix images, and leave the main one alone
Images are usually the heaviest files on a page and the most common cause of a slow LCP. Three fixes cover most of it:
- Upload at the size you display. A photo straight off a phone is several thousand pixels wide; a blog column needs a fraction of that.
- Convert to WebP. Google’s figures: WebP lossy images are 25 to 34% smaller than comparable JPEGs, and lossless WebP is 26% smaller than PNG. Image plugins such as ShortPixel, Imagify or Smush convert existing images in bulk.
- Do not lazy-load the main image. WordPress has lazy-loaded images by default since version 5.5, and since 6.3 it marks the likely main image with
fetchpriority="high"and skips lazy-loading for the first images on the page. Some themes and optimisation plugins override this and lazy-load everything, including the hero. That delays LCP. Check the hero image’s HTML forloading="lazy".
Give every image a width and height so the browser reserves its space; that alone fixes most layout shift. An autoplaying video at the top of the page is often the LCP element on mobile; a still image in its place is the quickest fix.
Step 4: Remove the scripts you do not need
Third-party scripts are the cause most guides skip. Live chat, review widgets, heat-mapping tools, social feeds, several tracking pixels and the page builder’s own scripts all compete for the phone’s processor, which shows up as high Total Blocking Time and poor INP.
- List every script in the waterfall and ask what it earns. Remove tools nobody has opened in months.
- Load the rest only where they are used: chat on contact pages, not on every article.
- Delay non-essential scripts until the visitor interacts. Most caching plugins offer a “delay JavaScript” setting; test forms and buttons afterwards, because it can break them.
- In Google Tag Manager, remove old tags and duplicate pixels before tuning when the rest fire.
Step 5: Fewer plugins, current PHP
Deactivate and delete plugins you are not using, and remove duplicates: two SEO plugins, two caching plugins, or a slider plugin left over from an old homepage. If you cannot tell which plugin is slow, deactivate them one at a time on a staging copy and test after each.
Then check your PHP version in your hosting control panel or under Tools, Site Health. WordPress.org recommends PHP 8.3 or greater. Older versions are slower, and those past their end of life no longer receive security fixes. Take a backup and test on staging before switching, because old plugins sometimes break on newer PHP.
Step 6: Serve the site from close to your visitors
If most of your customers are in South Africa and your server is in Europe or the United States, every request travels there and back before anything appears. Two ways to fix it:
- Host locally, or choose a plan with a South African data centre. Ask your host where the server physically is; the answer is not always on the sales page.
- Add a CDN. Cloudflare lists data centres in Johannesburg, Cape Town and Durban, and its free plan caches static files close to visitors. Older guides tell you to switch on Cloudflare’s Auto Minify; Cloudflare retired that feature in August 2024, so minify through your caching plugin instead.
Moving hosts is worth it only when the server is the bottleneck. If your TTFB is already low and pages are still slow, the cause is on the page, in Steps 3 and 4.
When the theme is the problem
Sometimes the steps above take a page from slow to less slow and no further, because the theme or page builder loads far more code than the page uses. At that point a lighter template for your key landing pages does more than any plugin. The difference can be large: a landing page we rebuilt went from 52 to 98 on Google’s mobile speed score, and its main content now shows in 1.8 seconds instead of 21.9 (13 November 2026).
Speed is one part of technical SEO. For the full set of checks, see WordPress SEO for South African businesses, and the guide to Core Web Vitals explains each metric in detail.
Other questions owners ask
Does website speed affect Google rankings?
A little. Google says Core Web Vitals “are used by our ranking systems”, and also that it “always seeks to show the most relevant content, even if the page experience is sub-par”. A fast page with nothing useful on it will not outrank a slower page that answers the question. The bigger gain is in how many visitors stay and enquire.
Do I need a PageSpeed score of 100?
No. The score is a lab summary. What counts is whether real visitors get good LCP, INP and CLS. Chasing the last few points usually means removing things that earn you money, such as tracking or a booking tool.
How do I know a fix worked?
Re-run the same lab tests on the same pages straight away. Real-visitor data takes longer: Search Console’s Core Web Vitals report looks at the last 28 days, so allow about a month before judging it. You can follow it in our Search Console tutorial.
Want your site checked and the slow parts fixed? Book a call with Searchly.

