How Long Do Websites Last? (And When Should You Replace Them?)
The HTML All The Things podcast explores how long websites last before needing replacement, examining the Orbit Media statistic that top marketing brand websites last an average of two years and one month. The hosts discuss how this varies dramatically based on business size, industry niche, technical needs, and competitive pressure. They also cover incremental vs. full replacement, the role of security vulnerabilities, and how agencies should frame website value around business results rather than aesthetics.
Summary
The episode opens with a reference to an Orbit Media statistic stating that top marketing brand websites last an average of two years and one month before being replaced. The hosts note this is surprisingly short given the cost and effort involved, and question whether this applies to the small and medium businesses they primarily work with.
The hosts establish a working definition of what it means for a website to 'last,' breaking it down into several dimensions: technical functionality (is it still working?), conversion performance (is it still generating leads?), brand representation (does it still reflect the company's identity?), developer maintainability (can it still be updated without major issues?), and market competitiveness (is it keeping pace with competitors?). They emphasize that a website can technically function while still failing the business by no longer converting customers.
The discussion distinguishes between different scales of business and their website needs. For large brands like Nike, visual identity aging is a real concern because brand perception is central to their value proposition. For utility-focused retailers like Best Buy, the design can remain relatively stable for years while technical and SEO maintenance is the ongoing priority. The hosts argue that for Amazon-scale e-commerce, the website is never truly 'replaced' but is instead continuously updated, with some legacy systems persisting deep in the stack while front-facing elements are modernized.
For small and medium businesses, the hosts argue that full website replacements are less common and less necessary than incremental updates. They describe a common pattern where clients return after a year or two with a list of desired changes, which are then phased into manageable increments. They note that many small business owners are wearing multiple hats and lack the time, budget, or expertise to monitor analytics or pursue aggressive optimization strategies.
The hosts discuss the agency sales dynamic, arguing that the most effective approach is to sell clients on business results — more leads, more sales — rather than on design aesthetics or technical specifications. This reframing reduces unproductive debates about visual preferences and keeps conversations focused on measurable outcomes. They caution against always advocating for a new website when incremental changes might suffice, emphasizing the importance of honest client relationships over maximizing billable work.
A significant portion of the conversation covers niche industries where older, utilitarian website designs are actually well-suited to their audiences. The hosts describe losing clients to agencies specializing in industries like heavy equipment sales, where buyers access websites from old terminals and care only about technical specifications — not visual design. They argue that understanding the client's market and end-user behavior is essential before recommending any website changes.
The episode closes with a discussion of the current security landscape, with the hosts arguing that unprecedented levels of automated attacks and newly disclosed CVE vulnerabilities make ongoing maintenance more critical than ever. They suggest that security concerns alone can now justify website updates or replacements in ways that wouldn't have been compelling a few years ago. The hosts conclude that website lifespan is highly context-dependent, and professionals should evaluate each client's competitive environment, niche, user base, and operational capacity before making recommendations.
About this episode
How long should a website last? While some major brands rebuild their websites every couple of years, many businesses expect their websites to serve them for much longer. In this episode, Matt and Mike explore what it really means for a website to ”last,” why some sites become outdated while others remain effective for years, and the key factors that drive redesigns, rebuilds, and modernization projects. From branding and user expectations to technical debt, security, SEO, and performance, they break down when it’s time to replace a website - and when it’s better to keep improving the one you already have.
Key Insights
- The hosts argue that the two-year-one-month average lifespan cited by Orbit Media applies primarily to top marketing brands, and that small-to-medium business websites can and often do last much longer without meaningful replacement.
- The hosts contend that a website can be technically functional while still failing the business — for example, still loading correctly but generating only one lead per year instead of ten — meaning 'lasting' must be evaluated on business performance, not just uptime.
- One host argues that for large brands like Nike, the real driver of frequent redesigns is competitive cat-and-mouse — watching what competitors do and adapting — rather than consumers actually noticing or caring about visual aging.
- The hosts describe a pattern where small business clients agree to a comprehensive website scope during initial calls, but two months into the project become overwhelmed when asked to contribute content or pay for maintenance, sometimes abandoning finished websites they've already paid for.
- The hosts argue that agencies specializing in unglamorous industries like heavy equipment sales deliberately use outdated-looking, utilitarian websites because their clients' end users access the web from old warehouse terminals and care only about technical specifications, not design.
- One host claims that for e-commerce giants like Best Buy, the deeper transactional systems (like bill payment in banks) often remain on decade-old legacy stacks because they are too risky to replace, resulting in jarring visual inconsistencies between modernized front pages and ancient back-end interfaces.
- The hosts argue that framing website work around measurable business outcomes — such as a guaranteed increase in leads — eliminates unproductive client debates about visual preferences like text alignment, because the shared goal becomes results rather than aesthetics.
- One host warns that the current security landscape, marked by an unprecedented volume of publicly disclosed CVE vulnerabilities including recent Nginx remote access flaws, means that leaving a website unmaintained for even a short period now carries substantially higher risk than it did a few years ago.
Topics
Transcript
When we make a website, how long will it last before it needs to be replaced? Now, according to Orbit Media, the average website lifespan for top marketing brands is two years and one month. Now, that is an incredibly short amount of time, given the amount of effort and money that it takes to put together a professional, modern and modern marketing website, which are usually fairly fancy. But most websites are not part of the top marketing brands. So how long will their websites last? So we're going to explore these, this conversation in this episode, we're going to be like taking a look at it because I have this conversation with my clients, a lot small to…
Full transcript available for MurmurCast members
Sign Up to AccessMore from HTML All The Things - Web Development, AI, and Developer Careers
How to Design Websites for Small Businesses
The episode discusses web design strategies for small to medium businesses, emphasizing that design is only part of the solution. The hosts argue that choosing the right service offering (full custom, theme-based, or pre-made) based on client needs is crucial, and that many small businesses waste money on unnecessary custom designs when templated solutions would better serve their actual business goals.
Are Tech Leaks Real - or Just Marketing?
Two hosts discuss the GTA 6 gameplay leak and broader questions about tech leaks in general, debating whether leaks are accidental or intentional marketing tactics. Both hosts express disinterest in leaks, preferring to experience products through official presentations, though they acknowledge leaks are ubiquitous and sometimes unavoidable.
How to Become a GTM Engineer: A New Career Path for Developers
GTM (Go-To-Market) engineers are an emerging role combining coding, data analysis, and business acumen to directly impact revenue, offering developers a way to increase job security during corporate reorganizations. The episode discusses why this role is growing, how it differs from traditional development, and practical strategies for developers to transition into GTM engineering without restarting their careers.
Developers Are Exhausted by AI Coding
This web news episode discusses Brett Codes' viral video where he announces he's quitting AI-assisted coding due to mental health concerns, dependency issues, and environmental/ethical worries. The hosts explore why this resonates with developers, the pressure from management to use AI, and debate whether manual coding will become a niche artisan skill or disappear entirely.
Small Business Websites Need to Do More Than Exist
The podcast discusses the evolving role of small business websites, emphasizing that they need to go beyond mere existence to actively engage users. Three layers of website functionality are proposed: a foundational layer for credibility, a discovery engine through content, and a tool-oriented layer that utilizes micro-apps to retain customer engagement.