Website Maintenance
Service Overview
WordPress now applies most updates by itself, and even rolls back a plugin update that crashes the site. What it cannot do is notice that your enquiry form stopped sending on Tuesday. Website maintenance is everything around the Update button: a backup first, a test afterwards on the paths that bring in business, and a named person who fixes whatever that test finds.
We look after WordPress sites we have built or revamped, and sites we take over after a first review of what is installed, who holds the logins and when the backups were last restored.
What Maintenance Includes
The commitments we attach to every site we look after:
- A staging copy for every live change
- Security patches within 72 hours
- Daily backups stored off the server
- A restore tested every quarter
- Uptime alerts and a monthly test enquiry
- Renewals tracked with named owners
- A plugin audit twice a year
What breaks on a site maintained by updates alone
Updates are necessary, and they are also where most breakages start. None of these is caught by clicking Update. All of them are caught by a plan.
The form stops sending
A plugin update conflicts with the theme. The site loads and looks normal; the enquiries simply stop arriving, and nobody notices for a week.
An old plugin meets new PHP
The host moves to a newer PHP version, and an abandoned plugin starts throwing errors on every page.
The certificate lapses
An SSL renewal fails quietly, and the browser starts warning visitors away from your site.
A known flaw goes unpatched
Patchstack’s 2026 report found about half of high-impact WordPress vulnerabilities are exploited within 24 hours of becoming public.
Speed decays
One added plugin and one uncompressed image at a time, until the site that launched fast fails Core Web Vitals and nobody can say when it happened.
The backup was never restored
Running, reporting success, and database-only. It is one of the most common things we find broken on a site we take over.
More in why website maintenance should include more than plugin updates.
Every commitment checked, and reported monthly
A commitment that is not checked is a marketing line. Each of these is set up at the start and reported on every month.
Staging before any live change
Updates are tested on a private copy first, where a failure costs nothing.
Patches within 72 hours
Security releases applied within three days, with a scan after each round of updates.
Daily backups, off the server
Database and files, stored away from the hosting account, and restored to staging at least once a quarter to prove they work.
Uptime alerts and a test enquiry
Monitoring that alerts a person, and a real test enquiry through every form each month.
Speed on a real phone
Core Web Vitals measured on real 4G with a mid-range phone, not on desktop fibre.
Renewals and plugins
Licence and domain renewals tracked in one place with named owners, and a plugin audit twice a year that removes what is unused or abandoned.
How often your site should be backed up
Set it by what the site records, not by how big the business is. WordPress’s own guidance is weekly for a smaller site and daily for a busy one, and “always before an upgrade”.
Orders or enquiries most days
Back up daily. A failure costs one day of orders and enquiries.
Weekly edits and posts
Back up weekly. A failure costs up to a week of edits.
A few edits a year
Back up monthly. A failure costs up to a month, usually little.
Any plugin, theme or PHP update
Take an extra copy first. It turns a two-day repair into a fifteen-minute rollback.
A WhatsApp enquiry survives a server failure; a web-form enquiry lives only in your database. How often a business website should be backed up explains why that matters.
When the site cannot be looked after as it stands
Sometimes the honest answer to a care plan quote is that the site cannot be maintained safely in its current state. These are the signs.
An abandoned plugin holds the layout together
Removing it breaks the pages; keeping it means running code nobody patches.
A theme nobody can change
Every small fix breaks something else, and the page builder, theme and add-ons fight over the same layout.
No staging copy to test on
Every update is tested on the live site, in front of your customers.
A slow first byte
web.dev treats a Time to First Byte over 1.8 seconds as poor. That is a server or caching problem no amount of image compression will fix.
Expensive to change
Hosting upgrades bought to compensate, and licences renewing for features nobody uses.
The fix
A website revamp that keeps your content and URLs, then maintenance on a site that can actually be maintained.
See seven signs a website is becoming expensive to maintain.
Website maintenance questions
Is a website care plan the same as a maintenance plan?
The names are used interchangeably. What matters is whether the plan says in writing how updates are tested, where backups are kept, how quickly someone responds, how many changes the fee covers, what is excluded and what you keep if you leave.
Does a small brochure website need maintenance?
It needs less of it. A site edited a few times a year is fine on a monthly backup, but it still needs updates applied, the certificate renewed and someone checking that the contact form still delivers.
Isn’t my hosting company already backing up my website?
Often, but check three things: that the copy holds both the database and the files, that it is stored away from the hosting account, and that someone has actually restored it at least once.
How quickly do security patches need applying?
Within days, not at the end of the month. Patchstack’s 2026 report put the weighted median time from a flaw being published to its first exploit at five hours. We apply patches within 72 hours of release, with a scan after each round.
Can you take over a site someone else built?
Yes. We start with a review: what is installed, who holds the administrator accounts and licences, and when a backup was last restored. Some sites need a revamp before they can be looked after safely, and we will say so.
How much does website maintenance cost?
It depends on what the site records and how much changes. A brochure site and a store taking orders every day need different backup schedules and testing, so we quote after that first review rather than from a package.
Before you sign a care plan
Why Maintain With iRevamps?
We look after what happens around the Update button: the backup before it, the test after it, and the person who fixes what the test finds.
1. Staging First
2. 72-Hour Patching
3. Off-Site Backups
4. Tested Restores
5. Monthly Test Enquiry
6. Named Contact
7. No Lock-In
