When Does a Business Need a Website Redesign? 9 Signs to Check

Start with diagnosis, not the assumption that design is the problem

Low enquiry volume can come from weak demand, inappropriate traffic, an unclear offer, poor follow-up or a technical fault. A redesign addresses only some of those causes. Changing the homepage because ads are not converting may leave the actual problem untouched.

First confirm that enquiries are delivered and measurement is correct. Review the landing destinations used by important campaigns, device differences and the sales team's feedback. A form opening is not a saved enquiry, and a saved enquiry is not necessarily a qualified lead.

Keep a baseline before making changes: relevant visits, successful submissions, qualified leads, organic entry pages and known defects. Do not claim losses or promise a percentage improvement without this evidence. Use the checks below to form testable hypotheses rather than justify a predetermined rebuild.

Nine signs to investigate and how to verify them

One confirmed problem can be enough to justify work, but it does not automatically justify a full redesign. A broken form is primarily a delivery problem; a service structure that no longer matches the company may require a broader change.

A practical mobile and enquiry test

Open the actual campaign URL rather than judging the homepage. Use a real phone and work through the primary enquiry action. Check whether overlays, sticky controls or the keyboard hide an important field or button.

1. Read the first screen and locate the intended action.
2. Open the menu and return to the enquiry route.
3. Use the form with missing and incorrect values.
4. Wait for any anti-spam check and test a valid submission.
5. Confirm that the request appears in the receiving system.
6. Check that confirmation and advertising conversion follow successful delivery.

Record the device, page, steps and actual result for each defect. “The mobile page is bad” gives the team less information than “the submit button becomes inaccessible after the phone keyboard opens”. Use anonymised replay evidence where appropriate; do not expose form data in public reports.

Targeted repair, redesign or rebuild?

Ask the supplier to explain why the smallest option will or will not solve the confirmed problem. Rebuilding because a developer prefers a different stack is not a business case. Conversely, repeatedly patching an unsuitable platform can create ongoing cost and fragile releases.

The design process is explained separately in our website design guide. Use it after the scope is understood; it should not replace diagnosis or a migration plan.

Real portfolio examples: define the destination you need

Autobuscenter: distinct service journeys

The Autobuscenter case shows a business with several automotive service directions, work examples and a blog. That structure gives different customer tasks appropriate entry points. It illustrates an architecture, not a documented before-and-after redesign experiment.

EURO-MONT: a focused quotation journey

In the EURO-MONT case, the focused offer, project evidence and quotation journey serve a narrower B2B task. Adding the same multi-page structure to every company would not necessarily help. Decide what information the buyer needs and where each conversation should start.

These examples do not establish an uplift in leads for your business. Use them to discuss service coverage, evidence and forms with the team. Request genuine historical data before treating any supplier's case as proof of a particular commercial improvement.

Protect valuable content and URLs during redesign

Before changing the site, make an inventory of important addresses, search entry pages, useful content, titles and internal links. Record which URLs stay and which must change. A visual update does not require removing a page that answers a distinct customer question.

1. Back up the site and retain a recoverable version.
2. Map necessary address changes to relevant replacements.
3. Preserve valuable content and discoverable internal links.
4. Check canonical, language alternatives and index rules.
5. Verify that staging restrictions are not carried into production.
6. Test response codes, rendering and sitemap entries after release.

Do not redirect unrelated service pages to the homepage or delete content merely to make a layout shorter. Keep the mobile version substantively useful. A migration is not finished when the new design is published; it is finished when the intended pages and customer journeys work.

How to measure whether the update helped

Compare equivalent traffic sources and devices over meaningful periods. Changes to budget, targeting, seasonality or the offer can affect the result. Record these alongside the redesign date. More engagement can be encouraging, but it is not a substitute for relevant enquiries.

What to improve first

Start with blocked actions: broken forms, inaccessible mobile controls and missing delivery. Next improve unclear offers and the highest-value entry pages. Address wider template and architecture work when the diagnosis shows that individual fixes are insufficient.

• Define each issue as a reproducible problem.
• Name the intended outcome and how it will be checked.
• Estimate dependencies and review responsibilities.
• Release in a recoverable way and retest the full journey.
• Keep a record of changes alongside performance data.

For commercial planning, the website cost guide explains budget components. If you need help deciding between repair and a larger update, discuss website redesign with WebUI Studio using the confirmed issues, not only a reference design.