A website being annoying does not automatically mean it needs rebuilding.
That sounds obvious, but website projects have a habit of escalating. A business starts by asking somebody to fix a slow page and three conversations later they are discussing a completely new website, new CMS and a five-figure budget.
Sometimes that is absolutely the right answer. Sometimes it really is not.
Our preference is to establish what is actually wrong with the existing website before deciding that replacing the whole thing is the solution.
When is it worth fixing what you have?
If the underlying website is reasonably modern, the content is useful and the main problem is a collection of smaller issues, improving the existing site can be much more sensible.
Performance problems can often be addressed. Poor templates can be redesigned. Elementor pages can be cleaned up. Forms can be replaced. Navigation can be improved and outdated sections removed.
I’ve worked on plenty of websites where the technology wasn’t necessarily the problem. The site had simply accumulated years of additions, changes and quick fixes. If the website fundamentally does what the business needs but has become untidy, there is no prize for throwing everything away.
This is particularly true when a rebuild would mean recreating hundreds of pages, risking existing search rankings and retraining the team, all to arrive at something that performs much the same job.
When does rebuilding start to make sense?
The calculation changes when the problems are structural.
If the website is built on an abandoned theme, relies heavily on unsupported plugins, has become almost impossible to edit or needs functionality it was never designed to handle, repeatedly patching it may eventually become more expensive than starting again.
The same applies when the business itself has fundamentally changed. If your services, audiences, brand and content structure no longer resemble what the website was originally designed around, there may be little value in preserving the old architecture.
A rebuild can also make sense when every proposed improvement requires another workaround. At some point you are not maintaining the website anymore, you are maintaining all the previous fixes.
Look at the next three years, not the last three
One useful way to make the decision is to stop asking how much money has already been spent on the existing site and instead ask whether you would willingly continue investing in it for another three years.
If the answer is yes, improve it.
If the answer is no because the technology, design or structure is already holding the business back, a rebuild deserves serious consideration.
We would also look at what proportion of a proposed rebuild genuinely needs replacing. Sometimes the right answer is somewhere in the middle, keeping good content and functionality while replacing an ageing theme or rebuilding the front end.
If you are stuck between fixing and rebuilding, send us the site. We are quite happy to recommend keeping what you have if that is the more sensible use of your money.
