Keeping WordPress Fast: A Monthly and Quarterly Performance Routine

By Shane Snyman, JWD Website Design Updated 25 September 2026

Most slow WordPress sites were not slow on launch day. They got that way gradually: a plugin added for a campaign and never removed, a few dozen full-size photos uploaded straight from a phone, a chat widget, a tracking script, an update that quietly added weight. No single change felt like a problem, and nobody was measuring.

This guide is about stopping that drift. It is not a one-off speed fix. It is a simple routine: a baseline you record once, a quick check after every update, a 30-minute monthly look and a longer quarterly review. If your site is already slow, fix it first with our DIY WordPress speed checklist or, if the problem is at hosting level, our WordPress server optimisation guide. Then use this routine to keep the gains.

Step 1: Record a Baseline You Can Compare Against

You cannot notice a slowdown without something to compare it to. Once the site is in good shape, write down the following in a simple spreadsheet, with the date:

PageSpeed Insights results for your homepage and your two or three most important pages, on both mobile and desktop.
Core Web Vitals field data, if PageSpeed Insights shows it: Largest Contentful Paint (good is 2.5 seconds or less), Interaction to Next Paint (good is 200 milliseconds or less) and Cumulative Layout Shift (good is 0.1 or less).
The Search Console Core Web Vitals report status for mobile and desktop, if your site is verified in Search Console.
Number of active plugins, your WordPress version and your PHP version (all visible under Tools > Site Health > Info).

Test the same pages every time. Changing which pages you test makes the numbers meaningless.

Step 2: Check After Every Update

Updates are the most common moment for a site to change behaviour, so treat each one as a small event rather than a background chore.

Back up first, and know how to restore.
Update in small batches rather than everything at once, so a problem points to one culprit.
Click through the pages that matter: the homepage, a service page, the contact form (send a test enquiry), and the cart and checkout if you sell online.
Re-run PageSpeed Insights on the homepage and compare the lab result with your baseline.
If something got worse, roll back that update or restore the backup, and check the plugin’s changelog or support forum before trying again.

WordPress can auto-update plugins and themes (you opt in plugin by plugin since WordPress 5.5), and it emails you after auto-updates run. If you use auto-updates, do step 3 and 4 when that email arrives.

Step 3: The 30-Minute Monthly Routine

Once a month, set aside half an hour:

Run PageSpeed Insights on your baseline pages and add the results to your spreadsheet. Look for a trend, not a single bad reading, since lab results vary a little between runs.
Open the Search Console Core Web Vitals report and check whether any URLs have moved into “Needs improvement” or “Poor”.
Open Tools > Site Health and deal with any new critical issues or pending updates.
Check what was uploaded this month. Look at new images in the Media Library and replace any oversized ones.
Check what was added this month. New plugins, embeds, pop-ups or tracking scripts are the usual reasons a site slows between checks. Ask whether each one is still needed.
Confirm your backups are running and that the latest one is recent.

Step 4: The Quarterly Review

Every three months, go a little deeper:

Plugin audit. Go through every plugin and ask whether the business still uses it. Deactivate, test and delete what it does not.
Test more pages. Run PageSpeed Insights on a wider set, including blog posts, landing pages from any campaigns, and product pages if you have them.
Clean the database. Remove old revisions, spam and trashed items with a reputable clean-up plugin, after a backup.
Review third-party scripts. Marketing tags, chat tools, review widgets and social embeds tend to accumulate. Remove the ones nobody is using any more.
Check your PHP version against PHP’s support dates. PHP 8.2, for example, reaches the end of security support on 31 December 2026. WordPress currently recommends PHP 8.3 or greater. Plan version upgrades with your host or developer rather than waiting for a warning.
Look at hosting resources. If your host shows CPU, memory or traffic graphs, check whether you are regularly hitting limits. Our server optimisation guide explains what to ask for if you are.
Test a restore. Restore a backup to a staging copy, or at least walk through the restore steps, so you know it works before you need it.

What to Monitor Between Checks

A routine catches drift. Monitoring catches sudden problems in between.

Uptime monitoring. A basic uptime monitor checks your site at regular intervals and emails you if it goes down or responds very slowly. Many services offer this, including free tiers.
Search Console tracking. When you fix an issue flagged in the Core Web Vitals report, use its fix tracking option, which starts a 28-day monitoring session to confirm the problem has gone across real visits.
Your own eyes. If staff or customers mention the site “feels slow”, test it that day rather than waiting for the monthly check.

Reading the Numbers Without Panicking

Lab scores move around. A few points’ difference between two runs is normal. Act on a consistent drop across several checks, or a sudden big one.
Field data lags. PageSpeed Insights field data covers a trailing 28-day period of real Chrome users, so a fix today shows up gradually over the following weeks.
Speed is not the same as rankings. Google uses Core Web Vitals in its ranking systems, but says good scores alone do not guarantee high rankings. Keep the site fast because it is better for visitors and removes a disadvantage in search, not because it will lift you to the top by itself.

A Simple Log Template

Keep one row per check in a spreadsheet with these columns: date, type of check (update, monthly or quarterly), pages tested, mobile and desktop lab results, field data if shown, active plugin count, what changed since last time, and what you did about it. After a few months, that log tells you exactly what slowed the site down and when, which saves hours of guesswork later.

When to Hand the Routine Over

This routine is designed so a business owner can run it. If you would rather not, or the checks keep turning up problems you cannot fix from the dashboard, that is where help makes sense. Our guide to website maintenance in South Africa explains what ongoing maintenance covers more broadly. At JWD, website maintenance is R450 an hour, with the time agreed before any work starts, so the routine checks can be done for you on whatever schedule suits your site. If the site needs a proper speed overhaul rather than upkeep, our WordPress speed optimisation service handles that.

And if a site keeps slowing down no matter how well it is maintained, the platform may be the problem. Our comparison of static, WordPress and custom CMS websites explains the options. A business website of up to 12 pages is R6,000 as a custom static site, R6,500 on WordPress or R7,500 on a custom CMS.

Frequently Asked Questions

How often should I test my WordPress site’s speed?

Test the homepage after every batch of updates, run your full set of baseline pages once a month, and do a wider review every quarter. Also test whenever someone reports the site feeling slow, or after adding a new plugin, embed or script.

What should I do if a plugin update slows my site down?

Confirm it first by testing again, since single lab results vary. If the slowdown is consistent, roll back that plugin or restore your pre-update backup, then check the plugin’s changelog and support forum. Report the issue to the developer, and consider a lighter alternative if it keeps happening.

Why has my Search Console Core Web Vitals report not improved after a fix?

The report uses real-user data from the Chrome UX Report, not a fresh test. After a genuine fix, it takes weeks for enough new visits to be measured, and the report’s fix tracking runs over 28 days. Check the lab results in PageSpeed Insights for immediate confirmation, and look at the report again after about a month.

Should I turn on automatic plugin updates?

It depends on the site. Auto-updates keep security patches current, which matters, but an update can occasionally break or slow something without you noticing. If you enable them, make sure backups run automatically, and check the site when WordPress emails you that updates have run. For online stores and sites with complex plugins, many owners prefer to update manually and test straight after.

Can JWD run this routine for me?

Yes. We can do the checks, updates, clean-ups and fixes as website maintenance work at R450 an hour, with the time agreed before we start. Ongoing SEO work, including Search Console setup, is a separate SEO service rather than part of maintenance.