Six months ago the site was quick. Someone compressed the images, set up caching, removed the plugins nobody used, and the pages finally opened without that pause on mobile. Today it feels slow again, and nobody can point to the day it happened, because it did not happen on one day. If you want to know how to keep a website fast after that kind of work, the first step is seeing how it slowed down.
It happened like this. In March, a new team member uploaded a batch of product photos straight from their phone. In April, marketing added a heatmap tool for a two-week test and never removed it. In May, a plugin update brought a new feature that loads on every page. In June, someone installed a popup plugin for a festival offer. Each change was small and sensible on its own. Together they undid most of the work.
Keeping speed is mostly about preventing that drift. It is a set of habits rather than a technical project, and most of them can be done by people who are not developers.
Why fast sites slow down again
Speed optimisation is a snapshot. It makes the site fast as it was on the day the work was done. After that, a live website keeps changing: new pages, new images, new plugins, plugin updates that add features, new tracking tags, new embeds. Very few of those changes make a site faster. Most add a little weight, and nobody checks the total.
There is also a quieter cause: things that need attention over time. Caches fill with stale entries, scheduled tasks pile up, the database grows, and a hosting account that suited the site last year may now be closer to its limits. None of this is dramatic, which is why it goes unnoticed.
The answer is not to freeze the site. It is to make speed part of how changes get made, so that every addition is a choice rather than an accident. That is what website speed maintenance means in practice.
Rules for whoever adds content
Most slow pages on small business sites are slow because of what was uploaded, not how the site was built. A few rules, written down and shared with everyone who can edit the site, prevent a lot of trouble.
- Resize before uploading. Agree a maximum width for each use: full-width banners, content images, product photos, team portraits. Phone photos are many times larger than any of these need. Our post on image dimensions and file size explains how to choose sensible sizes.
- Compress every image. Use a compression tool or the site’s image plugin, and do not switch it off because one picture looked slightly soft.
- Do not upload videos to the page. Use a video platform and embed it, ideally with a click-to-play preview, rather than placing a large video file in the media library.
- One hero image, not a gallery, at the top of a page. If a page needs many pictures, put them lower down.
- Ask before adding embeds. Social feeds, review widgets, maps and booking tools each load code from somewhere else. One on a contact page is fine. One on every page in the footer is not.
Rules for adding plugins, apps and tags
New functionality is the biggest source of drift, so give it a short gate. Before anyone installs a plugin or adds a tracking tag, they should be able to answer:
- What problem does this solve, and is there already something on the site that does it?
- Does it need to load on every page, or only where it is used?
- Is it actively maintained, and does it have a reasonable reputation?
- Who will remove it if the test ends or we stop using it, and when?
After installing, compare a speed test of an affected page before and after. If the page became noticeably slower, the steps in what to do when a new plugin slows the site help you decide whether to keep it, configure it or replace it.
The last question in that list deserves emphasis. Temporary tools have a habit of becoming permanent simply because nobody owns their removal. Put an end date next to anything installed for a campaign or an experiment.
After every update
Updates are necessary, and occasionally they change how a site performs. Plugin updates add features, theme updates change how styles load, and core updates change defaults. Most are harmless, but a quick check afterwards catches the exceptions before customers do. If you are not sure how to update safely in the first place, see our post on updating WordPress core, plugins and themes.
A short post-update check:
- Clear the site cache, then open the homepage, one key landing page and, on a store, a product page, in a private browser window.
- Note whether anything feels slower than usual, especially on a phone.
- Run one speed test on the most important page and compare it with your last recorded result.
- Submit the contact form and, on a store, add something to the cart.
If something feels wrong, you know exactly which change to look at, because you checked straight after making it.
How to keep a website fast: a monthly routine
Once a month, set aside a short block of time. It does not need a developer, just someone who is careful and keeps notes.
- Test the same pages the same way. Use the same tool, same pages and same device setting each month, and record the results in one place. Several runs per page give a fairer picture than one. Ways to automate this are covered in monitoring website speed over time.
- Check Search Console’s Core Web Vitals report for any new groups of slow or failing pages.
- Look at the newest uploads. Sort the media library by date and check that last month’s images follow the upload rules.
- Review plugins and tags. Anything added this month: is it still needed? Anything with an end date that has passed: remove it.
- Glance at the hosting panel for resource warnings, and at storage use.
Writing results down is what makes this useful. A single slow test means little. A page that has been getting slower for three months in a row tells you something real.
Every few months
Some checks are worth doing less often but more thoroughly:
- Clear out unused media, old post revisions and expired transient data, after a full backup.
- Check that the PHP version is still supported and that the host has not changed caching settings.
- Open every page template on a mid-range phone over mobile data, not just the homepage.
- Look at the full list of third-party scripts on your key pages and ask whether each one still earns its place.
- Review whether the hosting still fits the site’s traffic, particularly before a busy season.
Write it down: a one-page speed note
The habit that holds the others together is a short document that everyone who touches the site can find. It might contain:
- Maximum image sizes for each use, and the compression tool to use.
- The caching setup: which plugin or host feature, and what must be cleared after edits.
- The plugin and tag gate questions above.
- The pages to test each month, the tool and the settings.
- A log of changes that affect speed, with dates.
When a new staff member or agency starts, give them this note on day one. It turns speed from one person’s knowledge into the team’s habit. For the bigger picture of what affects speed and where each topic is covered, our full guide to website speed is the place to start, and for why the effort is worth it, see how speed connects to enquiries and sales.
When habits are not enough
Good habits slow the drift, but they cannot fix everything. If the monthly tests show a page getting slower and none of the recent changes explains it, or if real-user data in Search Console starts failing after months of passing, something structural has probably changed: the host moved the account to a different server, traffic has grown beyond what the plan handles, or a major plugin changed how it works. That is the point to stop adjusting settings and look at the site properly, with the change log in hand. The log is often what turns a long investigation into a short one.
Frequently asked questions
How often should I re-optimise my website?
If you follow regular habits, a full re-optimisation is rarely needed. It makes sense after a redesign, a migration, a change of theme or builder, or when monthly tests show a steady decline that the usual checks cannot explain. Otherwise, small corrections each month keep the site close to where it was.
Who in a small team should be responsible for website speed?
One named person, even if they are not technical. Their job is to keep the speed note, run the monthly tests, ask the plugin and tag questions, and call in help when something looks wrong. Without an owner, everyone assumes someone else is watching.
Do I need to clear the cache every time I edit a page?
Many caching plugins clear the affected page automatically when you save it, but not always related pages such as category listings or the homepage. Check how your setup behaves. If edits do not appear for visitors, clearing the cache is usually the first thing to try.
Should temporary marketing tools be allowed on the website at all?
Yes, as long as each one has an owner and an end date. Tests and campaigns are a normal part of running a business. The problem is tools that outlive their purpose. Note the date they were added and remove them when the test or campaign finishes.
Some owners would rather hand the routine side over. Our WordPress monthly maintenance plan applies core, plugin and theme updates with a backup first and includes a monthly performance and speed check. Whoever does the work, us or anyone else, give them your speed note so they keep to the same rules.
Next in this series: Is AMP Still Worth It? A Plain Answer for Small Sites
