Redesign or Rebuild? How to Tell What Your Site Needs

Your website is five years old. It looks it. It is slow on phones and you have stopped sending people to it.

So: redesign, or start over?

Everyone wants the answer to be redesign, because it sounds cheaper. Sometimes it is. Sometimes it is the most expensive possible choice, because you spend real money making a broken thing look nicer and end up rebuilding anyway eighteen months later, having paid twice.

Here is how to tell.

First: what is actually wrong?

Be specific. "It looks old" is not a diagnosis — it is a symptom, and it has several possible causes.

Write down what is actually bothering you:

• It looks dated compared to competitors
• It is slow
• It is painful on mobile
• Nobody can find it in search
• People visit and never get in touch
• You cannot change anything without paying someone
• It breaks when you touch it The first item on that list is a design problem. The rest are not — they are structural, and no amount of new design fixes them. This is the single most common expensive mistake: paying for a redesign to solve problems that were never about the design.

The six tests

Run these before anyone quotes you anything.

1. Open it on your phone. Not resized on your laptop — an actual phone, on mobile data, away from your office wifi. Is text readable without zooming? Are buttons tappable? Does anything run off the edge? If the site is fundamentally unusable on a phone rather than just ugly, that is usually structural.

2. Run Google PageSpeed Insights on mobile. Under 50 is a problem. Under 30 and it is rarely fixable by redesigning — it means the foundation is loading things it should not, and putting a new design on top adds weight to something already sinking.

3. Search site:yourdomain.com in Google. No results means you are not indexed at all, which is a technical problem a redesign will not touch. That has its own set of causes, and they are worth ruling out before you spend anything.

4. Try to change something small. A phone number, a paragraph. Can you? How long does it take? If the answer is "I have to email someone and wait three days", that is not going to be fixed by new colours.

5. Ask what it is built on. You do not need to understand the answer, but there is a difference between "it's a normal setup, it's just old" and "it was built on something that has not been updated since 2019 and the person who made it is gone". The second one is a rebuild whether you like it or not — nobody can safely modify a thing they cannot understand.

6. Ask yourself whether the structure is right. Not the colours. The structure. Are the pages the right pages? Does the navigation reflect what you do now, or what you did when the site was made? Businesses drift, and a site that has been patched to accommodate five years of drift usually has an architecture that matches nothing.

When a redesign is enough

You want a redesign when:

• The underlying site is technically sound — it loads reasonably fast, it works on mobile, it is indexed
• The content and structure are broadly right
• What is wrong is how it looks: dated typography, tired colours, an aesthetic that no longer matches what you have become
• You can change things without a fight
• You are not planning to add anything substantially new Signal: you look at it and think "this is fine, it just looks like 2019."

A redesign here is efficient. You keep everything that works — the structure, the URLs, whatever search visibility you have accumulated — and change the layer that is failing.

When it is a rebuild

You need a rebuild when:

• It is fundamentally slow and nobody can explain exactly why
• It is broken on mobile in ways that are not cosmetic
• The structure no longer matches your business
• Nothing can be changed without something else breaking
• It is built on something abandoned, or by someone unreachable
• You need to add something the current foundation cannot support
• Every fix reveals two more problems Signal: you describe the problem and it takes more than one sentence, and every sentence is about a different part.

The uncomfortable truth: patching a site like this costs more than replacing it. Each fix is cheap, and there are eleven of them, and the twelfth appears while you are paying for the eleventh. Meanwhile you are still living with a site that is losing you work the whole time.

The trap in the middle

The genuinely dangerous case: a site that is almost fine.

It looks decent. It mostly works. There are three or four things wrong, none catastrophic. So you redesign, because a rebuild feels like overkill for four problems.

And then you find out that two of those four are load-bearing. The slow page speed comes from the way the site was assembled, not the images. The mobile problem is in the layout system, not the CSS. So the redesign quietly becomes a rebuild, except it is being done as a redesign — patching around a foundation nobody planned to touch — and it costs more than a rebuild and works less well.

How to avoid it: before committing to a redesign, ask whoever is quoting: "Which of my problems does this actually fix, and which are underneath?" An honest answer separates the two. If you get "yeah, a redesign will sort all that out" without any examination, that is not an answer, it is a hope.

What you keep either way

People assume a rebuild means losing everything. It does not, and this matters more than most people realise.

Keep your URLs. If /services/plumbing exists and ranks, the new site should have /services/plumbing too. If it must change, it needs a redirect. Changing every URL without redirects is the fastest way to delete whatever search visibility you spent years accumulating — this is a genuinely irreversible mistake and it is made constantly.

Keep your content. Even if it needs a rewrite, the substance took years to work out. Nobody should be starting from a blank page.

Keep whatever is working. If one page brings you all your enquiries, that page has figured something out. Understand it before improving it.

The decision

Ask one question: is the problem what it looks like, or what it does?

Looks: redesign. Does: rebuild. Both: rebuild, and stop hoping otherwise — a redesign on a broken foundation is money spent to delay a decision you have already made.

And before either one, be honest about what the site is for. If it is a business card, do not spend business-critical money on it. If it is where your customers actually come from, the cheap option is the expensive one.

We're DAKER, a web design and development studio in Baku working with startups and small businesses across Europe. We'll audit your existing site for free and tell you honestly which one you need — including when the answer is "leave it alone, it's fine." Get in touch.