Websites Age Like Cars, Not Houses: How Long Your Site, Store, or App Will Really Last
A house left alone appreciates. A car left alone seizes. Software is the car. How fast marketing sites, web apps, and mobile apps actually age, what ages them even when nobody touches them, and what five years of honest ownership costs for each.
Jake Moreland
Senior Engineer, Initial Studios
Most owners think about their website the way they think about their premises: a thing you fit out once, then occupy. Spend big, launch, done, revisit in a decade. That's house thinking, and it's the single most expensive mental model in small business technology.
Software is not a house. A house left alone for five years appreciates. A car left alone for five years needs a mechanic before it needs a driver. Your website is the car: a working machine, in constant contact with a moving world, that stays reliable exactly as long as someone treats it like one. This is part three of our Owner's Manual series, after the anatomy of a project and what happens after launch, and it answers the question every owner eventually asks: how long does this thing actually last?
Why does an untouched website still age?
Because the world it runs in doesn't hold still, even if the code does. Your site from 2021 is bit-for-bit identical today, and yet:
- The devices changed. New phones, new screen sizes, new browsers with new rules. What rendered perfectly then renders oddly now, and you'd never know because you look at your own site on the same old laptop.
- Google changed. Speed expectations, mobile requirements, and now AI-driven search that reads structured data your old site doesn't have. Rankings don't fall off a cliff; they erode.
- The parts changed. Your site is assembled from dozens of software components, like a car is assembled from parts. Old parts stop getting security patches, and the services your site talks to retire old versions on their schedule, not yours.
- Your competitors changed. The site next door got faster and clearer. "Aged" is relative, and the customer comparing you at 9pm is doing the comparing.
- Your business changed. New services, new prices, new people. Every month the site describes your business slightly less accurately, which is aging of the most expensive kind.
None of that required you to touch anything. Entropy is included free with every website.
How fast does each kind of software age?
Not all software ages at the same speed, and this is where owners get genuinely useful leverage: knowing what kind of machine you own tells you what its service schedule looks like. Honest numbers, from the team that maintains all three kinds:
| Marketing website | Web app (bookings, portals, stores) | Mobile app | |
|---|---|---|---|
| Healthy lifespan before a major refresh | 3 to 5 years | 4 to 7 years, refreshed in parts | 2 to 4 years per era |
| What ages it fastest | Design trends, Google, your own content going stale | The services it connects to, and your business outgrowing its workflows | Apple and Google moving the goalposts every single year |
| Neglect tolerance | High: degrades gracefully | Medium: breaks in expensive, customer-facing ways | Low: can be removed from stores for falling behind |
| Realistic 5-year cost shape | Build once, light upkeep, one mid-life refresh | Build, then steady investment as your business grows into it | Build, then a real annual budget just to stand still |
The pattern worth memorising: the more a piece of software does, the faster it ages. A brochure site tolerates years of neglect. A booking system connected to payments, calendars, and SMS is negotiating with a dozen moving services, any of which can force work on you. A mobile app answers to two trillion-dollar landlords who renovate annually and evict tenants who don't keep up.
How do you know yours is aging?
You don't need a developer to run this smell test. Any two of these and your site is due for a look, which is not the same thing as due for a rebuild:
- It looks right on your computer and slightly wrong on your niece's phone.
- It takes noticeably longer to load than the sites you use as a customer.
- Changing your own trading hours requires emailing someone and waiting.
- The person who built it is hard to reach, or the honest answer to "who built this" is "we're not sure anymore".
- You've started apologising for it. "The website's a bit old" said out loud to a customer is a diagnostic, not small talk.
- Enquiries drifted down over years, and you've been explaining it with everything except the website.
The good news about the car model
Here's the part owners don't expect: car thinking is cheaper than house thinking. House thinking spends nothing for six years, then pays for a demolition and rebuild at panic prices, plus the invisible years of eroded enquiries along the way. Car thinking pays for small servicing continuously, catches the expensive stuff early, and pushes the big spend years further out. Same website, same decade, meaningfully less money, and the machine actually worked the whole time.
Which leaves one question: when the day does come, how do you know whether you're up for a service, a renovation, or a replacement? That's the final post in this series, on Thursday, and it comes with a decision framework you can run without a developer in the room.
Questions owners actually ask
- How long does a website last?
- A well-built marketing website is typically good for 3 to 5 years before it needs a serious refresh, with light upkeep along the way. Web apps like booking systems last 4 to 7 years but need steady investment. The variable that matters most isn't the build year, it's whether anyone has been servicing it.
- Do mobile apps age faster than websites?
- Yes, meaningfully. Apple and Google update their operating systems, design rules, and store requirements every year, and apps that fall too far behind can be delisted. A mobile app needs a real annual maintenance budget just to stand still, which is why we often steer small businesses toward web apps unless they genuinely need to be on the home screen.
- Is a slow website a sign it needs rebuilding?
- Not by itself. Slowness is often fixable with targeted work: image optimisation, better hosting, cleaning out accumulated plugins. Speed becomes a rebuild signal when it's combined with others, like a platform you've outgrown or a site nobody can safely change. One symptom is a service; a cluster is a decision.