Website Redesign or Website Optimisation: Which Problem Are You Actually Solving?

“We need a new website” is often a conclusion reached before the problem has been named.

Sometimes the conclusion is correct. The business has changed, the content no longer fits and the technology prevents necessary work. In other cases, a full redesign becomes an expensive way to rearrange the same weak proposition, poor traffic or neglected operating process.

We are not against redesigns; we design and build websites. We are against treating replacement as the default answer because it is more visible than diagnosis.

Identify the type of problem

Most underperforming websites have a mixture of five problem types.

Positioning problems

The site does not clearly say who the business is for, what it does or why somebody should choose it. The visual design may be competent, but the message is broad enough to fit any competitor.

This can require strategic and content work. It may not require rebuilding the platform.

Structural problems

Users cannot find important information, services overlap, pages have accumulated without a plan or the navigation reflects the company structure rather than customer needs.

If the content model and routes are fundamentally wrong, a redesign may be justified. If only one journey is weak, focused restructuring may be enough.

Experience problems

The site is difficult on mobile, forms are too long, focus states are missing, motion blocks content or calls to action are hard to distinguish. These are design and interaction issues, but not all require a new visual identity.

Technical problems

Slow loading, fragile plugins, poor security, broken integrations and an editor nobody can safely use can make the underlying system the problem. Rebuilding may reduce accumulated risk, but a technical audit should establish whether repair is viable.

Operational problems

Nobody owns updates. Enquiries arrive in an unmonitored inbox. Old services remain published. Performance is never reviewed. A new website will begin ageing immediately if the operating model stays the same.

That is a care problem, not a launch problem.

When optimisation is the responsible choice

Keep and improve the existing site when its foundations are sound and the problem is specific. Examples include:

• an important service page has weak content;
• mobile spacing and forms need correction;
• calls to action are unclear;
• case studies show images but not the thinking or outcomes;
• technical performance has declined;
• the website needs a clearer maintenance cycle;
• analytics reveal one avoidable point of friction.

Optimisation works best when there is a measurable hypothesis: “More qualified visitors will reach the enquiry form if the service page clarifies fit and evidence,” not “make the page feel fresher”.

When a redesign is warranted

A redesign becomes reasonable when several foundations need to change together:

• the business now serves a different audience;
• the offer and navigation need a new architecture;
• the identity no longer supports the company’s position;
• the content model cannot represent the work;
• the platform blocks essential integrations or safe editing;
• accessibility problems are structural across the component system;
• years of patches have made focused improvement riskier than rebuilding.

The decision should include migration, redirects, content reconciliation and operational ownership. A redesign is not complete when the new homepage is approved.

Look at evidence before aesthetics

Collect evidence from several places:

1. Customer conversations. What do prospects misunderstand or ask before they proceed?
2. Sales and enquiry quality. Are too few people enquiring, or are the wrong people enquiring?
3. Analytics and search data. Where do relevant visitors arrive and leave?
4. Content audit. Which pages are useful, duplicated, obsolete or missing?
5. Technical review. What creates performance, security or maintenance risk?
6. Accessibility review. Can people navigate, understand and complete important tasks?
7. Internal workflow. Can owners update the site without breaking it?

No single metric decides the answer. A high bounce rate, for example, may be normal for a page that answers a simple question. Evidence needs context.

What project work has taught us

For Chellaston Hearing Services, the website needed to make a personal healthcare journey feel clear and reassuring. For Extrude Solutions, it needed to organise technical capability and present authority to a specialist audience.

The visual outcomes are different because the underlying communication problems are different. We do not claim measured conversion improvements for either project. The lesson is about diagnosis: a website should be designed around the decision its audience needs to make.

Avoid the redesign reset myth

A new site does not reset the organisation’s content problems. If service descriptions are vague, the new design will display vague content more beautifully. If nobody can approve a case study, the portfolio will remain thin. If form follow-up is slow, a new form will not fix the sales process.

Budget time for content ownership and decisions. The project plan should identify who supplies facts, approves claims, checks legal requirements and maintains the finished system.

A staged alternative

When uncertainty is high, use stages:

Stage one: diagnose

Audit journeys, content, technical health and business requirements. Agree what success means.

Stage two: repair urgent friction

Fix broken forms, major accessibility barriers, security concerns and inaccurate information before waiting for a larger project.

Stage three: test the proposition

Improve one high-value route or service page. Learn whether clearer positioning and proof change enquiry quality.

Stage four: redesign if the case is proven

Use the evidence to define a more accurate scope, architecture and migration plan.

This approach can lead to a redesign. It simply earns the decision.

Questions to ask before approving a rebuild

• Which business change makes the current site inadequate?
• Which parts work and should be preserved?
• What evidence suggests visitors are struggling?
• What must the new platform do that the old one cannot?
• Who will create, approve and maintain content?
• How will URLs, metadata and useful existing pages be preserved?
• Which outcome will be reviewed after launch?

If the answers remain vague, the scope is not ready.

Our recommendation

Optimise when the problem is contained and the foundation is sound. Redesign when strategy, structure, system and operation need to change together. In both cases, begin with the business problem rather than a gallery of visual references.

Our website care and optimisation service supports the first route; our web design and development work supports the second. The label matters less than choosing the intervention that matches the evidence.