Skip to content
All articles
Web Design8 min read

How do you know when your website needs a redesign?

A fresh look or a better experience? The signs to consider before deciding.

Glass-like browser mockup against a turquoise and copper background
Cure’s design approach · Edited with AI assistance.

Start with a different question.

For a team that sees its website every day, an ageing design may be more noticeable than the problems visitors face. The colours no longer feel exciting, competitors look more modern, or someone wants to add movement to the homepage. These are understandable wishes. But when they’re the only reason for a redesign, the real problems can remain beneath a fresh look.

Start by asking “Can people complete what they came here to do?” rather than simply whether the site looks dated. Its job might be to sell a product, explain a service, receive applications or help the right person get in touch. Assessing improvements against that purpose also makes the scope more concrete.

Four signs beyond appearance

1. People keep asking the same questions.

If you often hear “What exactly do you do?”, “What’s included?” or “How can I contact you?”, first look at how clearly the content answers those questions. The issue may be missing or misplaced information. Gathering questions from support requests and sales conversations is a useful starting point.

2. A key step takes unnecessary effort.

A long mobile form, an unclear button or selections that disappear when you go back can exist on a modern-looking website too. Ask someone to complete a specific task and observe without telling them where to click. Note where they hesitate, while remembering that a single session doesn’t represent every user.

3. Your business has changed. Your website hasn’t.

If new services, a different customer profile or a growing product range no longer fit the page structure, the issue is more fundamental. Instead of repeatedly adding sections to the homepage, you may need to rethink the information hierarchy. Establish which questions visitors bring, then decide which page should answer each one.

4. Usability has taken a back seat.

Hard-to-read text, controls that can’t be reached by keyboard and slow responses go beyond aesthetics. Include accessibility and performance in the design review. Where possible, consider real-user performance data as well as lab scores. The Web Vitals guide offers a starting point for looking at loading, interaction and visual stability together.

Not every problem needs a complete redesign.

Define the problem first, then the scale of the change. Keeping what works can free your team to focus on the areas that matter most. The following is a framework for discussion, not a fixed prescription.

A starting scope based on the problem
ObservationWhere to start
The service is unclear; navigation works.Headings, descriptions and content order
People struggle with one particular task.Design and testing of the relevant flow
The page structure no longer fits the business model.Information architecture and a broader redesign
Pages are slow and the layout shifts.Review technical performance and the interface together

For example, low use of a consultancy’s contact form doesn’t prove the form is badly designed. Traffic may be reaching the wrong audience, the service may be unclear, or visitors may prefer to call. Before trying to improve a metric, understand the behaviour behind it.

A little preparation before you start

Write down the three most important user tasks. For each, describe the current experience, the problem you’ve observed and how you’ll assess improvement. Set an observable goal, such as “Understand the service and find the right contact channel”, rather than simply “Look more modern”.

When comparing results after a redesign, account for changes in traffic sources, campaigns and timing. You may not have enough evidence to attribute an increase directly to the new design. Successful task completion, types of error and user feedback add context to the numbers.

A short checklist

  • Can you state the website’s main purpose in one clear sentence?
  • Do you know the most important user tasks?
  • Can you describe the problems through observation or data?
  • Do you know which well-performing parts to keep?
  • Are mobile, accessibility and performance in scope?
  • Is there a plan to evaluate the site after launch?

A useful starting point is a clear description of the change that’s actually needed. That clarity gives both design decisions and development work a stronger purpose.

This article offers general design guidance. Examples are illustrative and do not represent measured client results or guarantees of higher conversion.