Back to Blog

Websites

When Should a Business Redesign Its Website?

Aug 11, 20266 min readAxxon Team
When Should a Business Redesign Its Website?

Redesigning too early wastes momentum and budget. Waiting too long quietly costs leads. Here is a framework for telling which situation you are actually in.

"Our website needs a redesign" is one of the most common things a business says about its own site, and one of the least reliable diagnoses. Sometimes it's true. Sometimes what's actually needed is a faster homepage, a clearer form, or copy that reflects what the business does now instead of what it did three years ago, none of which requires starting over. Knowing which situation you're actually in matters, because a full redesign is expensive, disruptive to search rankings if handled carelessly, and takes months. Getting the call wrong in either direction costs something: too early wastes budget and momentum, too late quietly costs leads the whole time you wait.


The honest, if inconvenient, starting point


A design looking dated is real, and it matters more than it might seem. The most-cited number in this conversation, that "75% of consumers judge credibility by website design," gets repeated constantly, but it doesn't hold up when traced back. The actual study it's pulled from, Stanford's Persuasive Technology Lab and Consumer WebWatch research on web credibility, found that 46.1 percent of people cited a site's visual design, layout, typography, and color scheme as part of what they used to judge its credibility. That's still a large number and still worth taking seriously, close to half of visitors are forming a trust judgment based partly on how the site looks, not what it says. It's just not three-quarters, and it's worth using the real figure. That study is also over two decades old at this point, which doesn't make the underlying finding wrong, people still judge quickly and visually, but it does mean it's describing a pattern rather than a current benchmark.
The practical takeaway isn't "redesign because the number is scary." It's that appearance genuinely does some of the work of earning trust before a visitor reads a word of copy, which means an outdated look isn't purely cosmetic. It's one input into whether someone believes the business behind the site is current, capable, and worth contacting.


Redesign and optimization solve different problems


The two get treated as interchangeable, but they're not, and confusing them is how businesses end up either overpaying for a rebuild they didn't need or underinvesting in one they did.
Optimization is the right call when the underlying structure works and the problems are specific and fixable in place: a slow page, a confusing form, thin copy, weak calls to action, missing mobile polish. These are real problems, and they're often the actual cause of low conversion even when the business assumes the whole site is the issue. Fixing them is faster, cheaper, and lower-risk than a rebuild, and because search engines have already indexed the site's structure, optimization doesn't carry the SEO risk that a careless redesign does.
Redesign is the right call when the problems are structural rather than surface-level: the site was built for a business that no longer exists in its current form, the technology underneath is genuinely obsolete or unsupported, the information architecture doesn't reflect current services, or the site simply wasn't built with conversion in mind at all, common with older sites built primarily as a digital brochure. No amount of copy editing or button-color testing fixes a site whose fundamental structure doesn't match what the business needs it to do now.


Signals that point toward redesign specifically


A few situations tend to cross the line from "needs fixing" to "needs rebuilding":
The business has changed more than the site has. Services, positioning, or target customers have shifted, but the site's structure still reflects an earlier version of the company. Editing copy on an architecture built for a different business rarely reads as coherent.
Mobile performance is broken at the structural level, not just unpolished. Google evaluates most sites primarily on their mobile version now, so a responsive layout that technically works but wasn't actually designed mobile-first tends to show up as both a user experience problem and a search visibility problem simultaneously. That combination is a strong redesign signal, because it's rarely fixable with incremental patches.
The technology is genuinely obsolete. A CMS that's no longer supported, a platform that can't accommodate basic modern functionality, or a site that requires a developer for every small content change all point toward rebuild rather than repair.
Traffic is healthy but conversion has been low for a long time despite incremental fixes. If forms have been shortened, copy has been rewritten, and load time has been improved, and the site still isn't converting, the problem may be the underlying structure and user flow, not any one page.


Signals that point toward optimization instead


The inverse list is just as useful, mainly because it's the one businesses skip past when they've already decided "redesign" is the answer:
The site is slow, but the platform itself is capable of being fast, this is a performance fix, not a rebuild.
The design feels dated in specific, nameable ways, old fonts, a cluttered layout, low-quality imagery, rather than the whole structure feeling wrong.
Conversion is inconsistent across pages, some convert fine, others don't, which usually points to page-level problems rather than a site-wide structural issue.
The business hasn't fundamentally changed; the site just hasn't kept pace with smaller updates.


A rough timing benchmark, held loosely


As a general industry pattern rather than a hard rule, most actively growing businesses end up redesigning roughly every five to eight years, not because the calendar demands it, but because that's typically how long it takes for the accumulated gap between a business's current reality and its website's original structure to become the larger problem, rather than any individual fixable issue. That's a loose benchmark, not a deadline. A three-year-old site with a structural mismatch needs attention sooner. A seven-year-old site that's been maintained and incrementally improved might still be the right foundation.
The more reliable approach is working through the signals above rather than defaulting to either "it's old, so redesign" or "we already spent money on this, so it must just need tweaks." Both defaults skip the actual diagnosis, and the diagnosis is what determines whether the next dollar spent goes furthest on a rebuild or on fixing what's already there.