On this page
To speed up a WordPress website, measure it first, then fix the biggest causes in order: slow server response, no page caching, oversized images, too many heavy plugins and render-blocking scripts. On most small business sites, page caching plus properly sized images deliver the largest gain for the least effort.
This guide gives you the targets to aim for, eight fixes in the order we would tackle them, and how to tell whether the problem is your site or your hosting.
Key takeaways
- Aim for Google's "good" Core Web Vitals: LCP within 2.5 seconds, INP of 200 ms or less, CLS of 0.1 or less.
- Field data from real visitors matters more than the 0 to 100 PageSpeed score.
- Page caching and right-sized, compressed images are the biggest wins on most sites.
- Delete unused plugins and replace heavy ones; count scripts, not plugins.
- If server response is slow even on a cached page, the fix is hosting, not WordPress.
Measure first
Run your home page and one or two key pages through PageSpeed Insights. It shows two kinds of results:
- Field data ("Discover what your real users are experiencing"): Core Web Vitals from real Chrome users over the last 28 days, if your site has enough traffic. This is what Google's page experience assessment is based on.
- Lab data (the score out of 100): one simulated test on a throttled phone. Useful for finding problems, but it varies from run to run and is not a ranking number.
According to web.dev's Core Web Vitals guide, a good experience means Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less, measured at the 75th percentile of visits. Focus on the mobile results: most South African visitors browse on phones, and Google indexes the mobile version of your site.
Why WordPress sites slow down
| Symptom in PageSpeed Insights | Likely cause | Fix |
|---|---|---|
| "Reduce initial server response time" or slow TTFB | No page cache, slow or overloaded server, old PHP | Steps 1 and 2 |
| "Properly size images", "Serve images in next-gen formats" | Large photos uploaded straight from a phone or camera | Step 3 |
| "Reduce unused JavaScript/CSS" | Page builders, sliders, plugins loading on every page | Steps 4 and 5 |
| Poor INP | Heavy scripts, chat widgets, tracking tags | Step 5 |
| High CLS | Images without dimensions, late-loading banners and fonts | Step 6 |
Step 1: Check server response and PHP
If a cached page still takes well over half a second for the server to start responding, no front-end tweak will fully fix it. Check three things. First, the PHP version: newer releases are faster, and PHP 8.1 and older no longer get security fixes, so move to 8.3 or newer using our help article on changing your PHP version in cPanel. Second, resource limits: if cPanel shows you hitting CPU or memory limits, the server is throttling you. Third, distance: a server in South Africa answers local visitors faster than one overseas.
Our explainer on CPU, RAM, inodes and other hosting specs helps you read those limits, and how web hosting affects SEO explains where server speed fits into rankings.
Step 2: Turn on page caching
Without caching, WordPress runs PHP and database queries to build every page on every visit. A page cache saves the finished HTML and serves that instead, which is usually the single biggest improvement. Use the caching your server supports: on LiteSpeed servers, the free LiteSpeed Cache plugin caches at server level and also handles CSS, JavaScript and image optimisation. On other servers, plugins such as WP Super Cache, W3 Total Cache or the paid WP Rocket do the job. Run only one caching plugin, and exclude cart, checkout and account pages if you run a shop.
Step 3: Resize and compress images
A phone photo can easily be several megabytes. Displayed in a 1,200-pixel-wide area, it rarely needs to be more than about 200KB. Resize images before uploading (or let a plugin do it), compress them, and serve WebP or AVIF; WordPress supports WebP uploads since version 5.8 and AVIF since 6.5. Plugins such as ShortPixel, Imagify or LiteSpeed Cache's image optimisation can convert existing images in bulk.
Make sure the main image at the top of the page (often the LCP element) is not lazy-loaded, while images further down are. Recent WordPress versions handle most of this automatically, but some themes and sliders override it.
Step 4: Clean up plugins and the theme
The number of plugins matters less than what each one loads. One slider or page builder can add more weight than ten small utility plugins. Delete plugins you no longer use, then check each remaining one: does it load scripts on pages where it is not needed? A lightweight theme with the block editor is usually faster than a heavy multipurpose theme plus a page builder. Our WordPress performance optimisation tips list common culprits.
Step 5: Tame third-party scripts
Chat widgets, social feeds, embedded videos, multiple analytics and ad tags all download code from other servers and compete for the phone's processor, which hurts INP. Remove what you do not use, load embeds only when clicked (a video thumbnail instead of a full YouTube player), and delay non-essential scripts until after the page loads.
Step 6: Stop layout shift
Pages that jump while loading frustrate visitors and score badly on CLS. Give images and embeds width and height attributes, reserve space for cookie banners and notices, and preload your main font or use a system font stack.
Step 7: Consider a CDN
A content delivery network serves images, CSS and JavaScript from locations close to each visitor and takes load off your server. If nearly all your visitors are in South Africa and your server is local, the gain is smaller but a CDN still helps with traffic spikes and security filtering. Cloudflare's free plan suits most small sites; test carefully, because a misconfigured CDN can cache logged-in or cart pages.
Step 8: Tidy the database
Old post revisions, spam comments and expired transients build up over the years. On small sites this rarely causes a noticeable slowdown, but on older sites and WooCommerce stores a clean-up can speed up the admin. Back up first, then use a tool such as WP-Optimize, and limit revisions with define('WP_POST_REVISIONS', 10); in wp-config.php. The WordPress optimisation guide covers caching and database options in more depth.
When the problem is your hosting
If you have done steps 2 to 6 and the server response is still slow, or the site slows down only at busy times, you have probably outgrown the plan. Our guide to getting more from your hosting plan covers the in-between fixes, and our checklist of WordPress hosting features that matter explains what to look for in a replacement. Our WordPress hosting runs on LiteSpeed servers with the LiteSpeed Cache plugin supported, and the WordPress Business and Ultimate plans add NVMe storage and extra CloudLinux resources.
Speed and your SEO
Google says its core ranking systems look to reward a good page experience, of which Core Web Vitals are part, but there is no single signal and relevance still comes first. A faster site will not outrank a much more relevant one. The clearer benefit is visitors: fewer people leave before the page appears, and more fill in your form.
Quick recap
- Measure with PageSpeed Insights; trust field data over the lab score
- Fix server response and PHP version first
- Turn on one page cache that suits your server
- Resize, compress and convert images; do not lazy-load the hero image
- Delete unused plugins and cut heavy scripts
- Upgrade hosting only when a cached page is still slow
Frequently asked questions
Why is my WordPress site so slow?
Usually a mix of no page caching, oversized images, a heavy theme or page builder, too many scripts, and sometimes a slow or overloaded server. PageSpeed Insights shows which applies.
Does hosting affect WordPress speed?
Yes. Server response time, PHP version, caching support and resource limits set how fast WordPress can be. But a well-hosted site with huge images will still be slow.
What is a good page load time?
Use Google's thresholds: the largest element on the page should appear within 2.5 seconds for at least 75% of visits, with quick responses to taps (INP 200 ms or less) and no jumping layout.
Which caching plugin should I use?
The one that matches your server. On LiteSpeed hosting, use LiteSpeed Cache. Elsewhere, WP Super Cache, W3 Total Cache or WP Rocket all work. Use only one.
Sources
Web Design Hosting SA has hosted and built websites for South African businesses since 2009. Prices in our guides come from our live price list and are checked when a guide is updated. How we write our guides. Spotted something out of date? Tell us.



