Maintenance6 min read
What actually breaks on a website, and what it costs to ignore
Short answer
An unmaintained website doesn't fail all at once — it degrades on a predictable schedule. Certificates expire in 90 days, contact forms break silently within a year, dependencies go stale in months, and security patches accumulate until one becomes an incident. Almost none of it announces itself.
Most people picture website failure as the site going down. That's the rare case, and the easy one, because you notice. The expensive failures are the quiet ones.
The timeline of neglect
| When | What fails | How you find out |
|---|---|---|
| Day 90 | SSL certificate expires | Browser scare page. Usually a customer tells you. |
| Month 1–6 | Contact form stops delivering | You don't. Enquiries just stop and you assume it's a slow quarter. |
| Month 3–12 | Dependencies go stale | Nothing visible until an update becomes impossible without a rewrite. |
| Month 6–18 | An integration's API changes | A payment, booking or CRM sync quietly stops working. |
| Month 12+ | Performance drifts | Rankings slide. Nobody connects it to the site. |
| Any time | An unpatched vulnerability is exploited | Abruptly, and publicly. |
The one that costs the most
Broken contact forms. It's not dramatic, which is exactly why it's expensive. A form breaks after a DNS change, a mail provider policy update, or a spam filter reclassification — and it fails silently. The visitor sees a success message. You see nothing at all.
Why it accumulates
Everything on a website sits on top of things other people maintain — a framework, a CMS, plugins, a hosting platform, half a dozen APIs. All of those change on their own schedule. Doing nothing isn't stasis; it's drifting further from the versions everything else expects.
The compounding matters. Six months of skipped updates is an afternoon. Three years is a rebuild — because by then the upgrade path involves breaking changes stacked on breaking changes.
What maintenance should actually cover
- Dependency and platform updates, applied and tested, monthly
- Backups that have been restored at least once — an untested backup is a hypothesis
- Uptime and certificate monitoring, so you learn before your customers do
- Form and checkout delivery checks, because these fail silently
- Security patching with a defined response time
- A performance budget, so speed doesn't drift back
- A named person who answers when something is wrong
Doing it yourself
Entirely reasonable, and cheaper. The requirements are a recurring calendar slot you actually honour, somewhere to be alerted, and the willingness to apply an update the week it lands rather than the quarter it lands. Most businesses manage the first two.
If that isn't realistic, a care plan starts at $29/month and exists so it never becomes your problem. It's how we keep plenty of sites, stores and apps running for other people.
Written by Mohit Kumar, Founder & Technical Lead at decodewithMohit.
Put it into practice
Want us to just handle this?
Tell us what you're trying to fix. You'll get a written reply within 24 hours with whether we can help, what it costs, and what isn't worth paying us for.
Written reply within 24 hours · No mailing list · contact@decodewithmohit.com