How do I know if my website's problems are technical or just visual?

Run a technical audit using a tool like Google PageSpeed Insights or Screaming Frog, and have a developer review your CMS setup. If the audit shows structural performance or security issues, the problem is technical. If the scores are healthy but the site looks dated or converts poorly, it's likely a design and UX issue.

How long does a website rebuild typically take?

A straightforward rebuild for a small business site usually takes eight to sixteen weeks. Larger or more complex sites — with e-commerce, integrations, or custom functionality — can take four to six months or more.

Can I redesign my site without changing the platform?

Yes, in most cases. If your CMS is still supported and working well, a designer can restyle templates and restructure pages without migrating platforms. Webflow, WordPress, and Squarespace all support significant visual changes within the existing environment.

Is a rebuild always more expensive than a redesign?

Upfront, yes. But if your current platform keeps causing problems, the ongoing cost of maintenance, fixes, and repeated redesigns often exceeds the one-time cost of a proper rebuild. Think of it as a capital investment rather than a project expense.

How often should a website be redesigned or rebuilt?

There's no fixed rule, but most business websites benefit from a meaningful update every three to four years. Technology, design conventions, and user expectations shift quickly — a site that looked modern in 2020 may feel dated now.

Rebuild vs. Redesign Your Website: How to Decide

If your website isn't performing, the instinct is often to 'refresh the design'. Sometimes that's exactly right. Other times, it's painting over damp — the problem is structural, and no amount of new fonts will fix it. Knowing which situation you're in saves time, money, and frustration.

What's the Actual Difference?

A redesign changes how a site looks and feels — layouts, colours, typography, imagery — while keeping the underlying platform, CMS, and codebase largely intact. A rebuild replaces the technical foundation: the platform, the architecture, sometimes the hosting and integrations too. You can redesign without rebuilding, but you can't fully rebuild without redesigning.

Signs You Need a Redesign

A redesign makes sense when the core infrastructure is sound but the site no longer reflects who you are or what you offer. Common triggers include:

The visual identity has changed — new logo, brand colours, or tone of voice
The site looks dated compared to competitors, even though it functions fine
Conversion rates are low despite decent traffic (a UX and messaging problem)
Navigation and page structure need rethinking, but the CMS works well
You've rebranded or repositioned and the site no longer matches

In these cases, the engine is fine — you just need a new body. A skilled designer can often work within your existing platform and deliver a result that feels completely fresh without touching the back end.

Signs You Need a Rebuild

A rebuild is necessary when the underlying system is working against you. No amount of visual polish fixes a slow, fragile, or unmaintainable site. Look for these signals:

Page load times are poor and technical audits flag deep performance issues
Your CMS or platform is outdated, unsupported, or genuinely painful to use
The site isn't mobile-friendly at a structural level, not just visually
You've accumulated so many plugins, patches, or hacks that updates break things
You need features (e.g. e-commerce, booking, personalisation) your current platform can't support
Security vulnerabilities are recurring and patching feels like whack-a-mole

These are foundation problems. Redesigning around them is like redecorating a house with subsidence — it'll look fine briefly, then the cracks reappear.

The Cost and Time Trade-Off

Rebuilds cost more and take longer — that's simply true. A redesign within an existing platform might take four to eight weeks. A full rebuild, done properly, is typically three to six months depending on complexity. But a rebuild done once is usually cheaper in the long run than redesigning a broken site every two years.

Before committing either way, get a proper technical audit. It costs relatively little and tells you definitively whether the foundation is salvageable. Without one, you're guessing — and guessing wrong is expensive.

When Both Happen Together

Often the right answer is both — a full rebuild that also includes a redesign. This is common when a business has grown significantly, changed direction, or is migrating from a legacy platform to something modern like Webflow, WordPress with a headless setup, or a purpose-built solution. It's more work upfront, but you get a site that's fast, maintainable, and visually aligned with where the business is now.

A Simple Decision Framework

Is the platform still supported and capable of what you need? If no → rebuild.
Are load times and Core Web Vitals acceptable? If no → likely rebuild.
Can your team update the site without developer help? If no → rebuild or major overhaul.
Does the site work well but look wrong? → Redesign.
Has the brand or offering fundamentally changed? → Redesign at minimum, rebuild if infrastructure is also weak.

The Bottom Line

Be honest about what's actually broken. If it's aesthetics and messaging, redesign. If it's performance, platform, or maintainability, rebuild. If it's both — which is common with sites more than four or five years old — commit to doing it properly rather than papering over the cracks again.