The finish line, that's how a website launch usually gets treated. It's really closer to the starting point of the part that matters most, keeping the thing running properly.
- Plugins go out of date
- A form quietly stops sending emails and nobody notices for three weeks
- A page that used to load fast starts taking six seconds because an image was never compressed after a content update
What our website maintenance and support actually covers
This is more than a support contract that sits unused until something breaks.
- Regular updates to your CMS, plugins and dependencies, done carefully and tested so nothing breaks in the process
- Backups kept current and actually tested, so a bad update or a hosting issue isn't a disaster you discover the hard way
- Monitoring for uptime, broken links and slow pages, caught before they cost you traffic, leads, or a customer's trust
- Small content and feature changes handled as they come up, without a full new project quote every single time
- A monthly or quarterly check in on what's changed, so you're not surprised by what we've been doing behind the scenes
Fixing a crisis after a client has already complained that the contact form doesn't work costs a lot more, and a lot more stress, than catching it on a schedule before a visitor ever notices.
Why this gets skipped so often
Nothing visibly breaks for a while, that's exactly why maintenance is so easy to deprioritise, right up until it does, usually at an inconvenient moment. We've seen businesses lose a week of enquiries because a contact form silently stopped working after a plugin update and nobody was checking. The cost of that missed week is almost always higher than a year of proper maintenance, it's just a cost that's harder to see coming.
What a typical support arrangement looks like
- A set number of hours each month for updates and small changes
- Anything bigger scoped and quoted separately, not buried in vague hourly billing
- A plain answer on whether your site needs light monthly attention or closer watching, depending on traffic and how many moving parts it has
What is included and how often
| Task | How often | Why it matters |
|---|---|---|
| Core and plugin updates | Monthly | Security and compatibility |
| Backups | Weekly, or before major changes | Recovery if something goes wrong |
| Uptime and broken link checks | Continuous | Catch issues before visitors do |
| Speed check | Quarterly | Performance degrades over time if nobody checks |
If you're currently the person who gets a panicked call every time the website does something odd, that's usually a sign the site needs a proper maintenance plan instead of reactive firefighting every few months. Have a look at our full website development services for how this fits into the bigger picture, and if speed specifically has been slipping over time, our performance focused development page covers how we catch that.
