Insights
Websites age. Here's how to tell when yours has.
Adobe Flash once ran the most creative corners of the web. Adobe announced its retirement years in advance, and when the end came, every site still built on it went dark overnight. Most website aging is slower and quieter than that. The result is the same.
Sites age in layers
The visible layer ages first. Design has fashions like everything else, and a site styled for the tastes of a decade ago tells customers the business might be living there too.
Under that, the code ages. The platform version drifts out of support, the plugins stop getting updates, the developer who knew where everything lived moves on. Nothing looks different from the outside, but every change gets scarier to make.
And the ground moves. Most of your visitors are now on phones, and a site designed shoulder-first for desktop makes them pinch and squint their way to a competitor.
The honest signs
You apologize for the site when someone mentions it. Nobody on staff can change a price or a photo without a support ticket. It's noticeably slow on a phone off wifi. The browser flags it, or forms fail quietly and customers tell you about it later. The company that built it no longer exists, and the person who has the passwords is a search through old email.
Any two of those together is the site telling you it's time.
What ignoring it costs
The costs are quiet, which is why they're easy to carry too long. Visitors leave slow pages before they load, and search engines notice the same slowness. Old platforms accumulate security holes, and a hacked site costs more than a rebuilt one, in money and in reputation. Meanwhile every year of deferral makes the eventual move bigger, because content, integrations, and habits keep growing roots in the old ground.
Flash sites had a hard deadline and still caught their owners flat. Yours won't send a press release first.
When to act, and how much action
Not every aging site needs a rebuild. Sometimes it needs a fast host, a cleanup, and ten targeted fixes. Sometimes the foundation is genuinely done and patching it is throwing money down a well. The difference is usually in the code layer, not the visible one, which is why eyeballing it from the homepage doesn't answer the question.
Get it read by someone who can see all the layers, and insist on the answer in writing, with the reasons attached.