Start with a redesign when several problems share a cause, such as a content structure that no longer matches the business or a template that makes every mobile task harder. A single broken form, confusing headline or oversized photo may need a focused repair. Use these ten signs to determine where the trouble starts.

1. The phone experience gets in the way

Try to request a quote on a phone using one hand. Watch for overlapping controls, tiny tap targets and menus that hide the contact path. Repeat after rotating the screen or enlarging text. Problems across every template point toward a shared layout issue.

2. Important pages feel slow

Open a service page on a mobile connection and watch for the main image and headline. Try a tap while the page is still loading. Google’s Web Vitals distinguish loading, responsiveness and visual stability. Measure before redesigning so you can identify whether a shared script, image policy or layout causes the delay.

Source: web.dev Web Vitals

3. Navigation reflects your org chart

Give a visitor a simple task such as finding emergency support. If they have to know the department name, your navigation is asking them to learn your internal structure. Test labels drawn from customer questions and try grouping pages by what visitors need to do.

4. Your content describes an older business

Check hours, service boundaries, price qualifiers and evidence of current work. A handful of stale entries needs an editing pass. If your old page structure gives the wrong services prominence or forces new offers into unrelated pages, address the structure first.

5. The visual presentation obscures priorities

A crowded header, inconsistent headings or several equally prominent buttons can make an otherwise tidy page difficult to scan. Show a page to someone briefly and ask what it offers and what action they would take. Compare what they remember with what matters to your business.

6. Suitable visitors rarely finish the next step

Compare inquiries with visits to key pages and review whether inquiries were a reasonable fit. Check the form and confirmation before interpreting conversion data. If visitors understand the offer but hesitate, add useful proof or explain the next step more clearly and observe what changes.

7. People encounter accessibility barriers

Try the essential paths with a keyboard. Verify that focus is visible and fields have meaningful labels. Check the contrast of labels and instructions against the backgrounds they actually appear on. Bring in specialist testing if important tasks remain difficult across the site.

Sources: W3C guidance on labeling controls · W3C minimum contrast guidance

8. Updates create recurring security concerns

Find out whether the platform and dependencies still receive updates, who applies them, and how the team responds if a change breaks the site. If the current stack cannot be supported within your resources, a planned migration may be more sensible than repeated emergency work.

Source: Canadian Centre for Cyber Security baseline controls

9. Your staff avoid making ordinary edits

Ask the person responsible for updating content to change one representative service detail. Watch for requests to a developer, changes in several locations, and fear of breaking layout. If everyday changes are hard to publish and check, editing requirements belong in the project brief.

Preserve what is already doing useful work

Before a redesign, identify the pages customers currently share and the actions that already work. Keep a copy of the old page inventory, identify high-value entry points and decide where each retired URL should lead. Carry forward accurate project evidence, frequently requested service details and information your support team relies on.

During acceptance testing, use concrete tasks. Have someone identify a suitable service, read a relevant example, send a test inquiry and check the confirmation. Ask an editor to update a page and preview it. Test both a new URL and an old link. Comparing the same tasks before and after the project makes it easier to see which issues the redesign addressed.

Your Action Checklist

  • Record the three most disruptive issues with page URLs and screenshots.
  • Decide which issues share a cause and which can be fixed independently.

NSBDA can help assess the problems you’ve documented and scope a rebuild around the tasks customers need to complete.

Explore Website Development