“The website looks old” is a reason to investigate, not a diagnosis. A new colour palette will not repair lost enquiries, and a full rebuild may be unnecessary when a few broken journeys are doing most of the damage. Before commissioning a redesign, collect evidence against these seven warning signs.
1. People cannot work out what you do
Ask someone outside the company to read the first screen and describe the offer. Can they name the service, the customer it suits and the next step? If they can only repeat a slogan, try revising the heading, summary and navigation before replacing the entire site.
Record what people misunderstand. A supplier that does both software consulting and website work may need clearer routes for different buyers, rather than more decorative content on the homepage.
2. Enquiries disappear after submission
A success message is not proof that a request reached the right person. Follow an approved test submission through storage, notification and the team's follow-up queue. Check spam handling, forwarding rules and any CRM integration.
If that chain fails, fix it promptly. It is an operational defect even when the page looks excellent. Our form monitoring guide separates these stages so a redesign brief can name the actual fault.
3. Mobile customers struggle with ordinary tasks
Try selecting a service, reading a price, opening navigation and correcting a form error on a phone. Look for hidden controls, text covered by sticky elements, sideways scrolling and buttons too close together. Also check keyboard navigation and zoom on desktop; mobile testing does not replace accessibility review.
W3C's page structure tutorial describes how meaningful headings and regions support navigation. Use that as a practical reference, then test the actual journeys your customers need.
4. Staff avoid updating the content
If a routine service change requires finding a departed developer, the editing workflow may need work. Ask the person responsible for content to perform an ordinary update in a safe preview. Watch where they become unsure: finding the page, choosing an image, understanding shared sections or knowing whether a change is already public.
A focused improvement to editing permissions and reusable sections can be more useful than replacing the visual design. Include training and ownership in the scope if the site is rebuilt.
5. The platform blocks a requirement you now have
A brochure site might no longer suit a business that needs customer-specific prices, account permissions or a connection to inventory. First check whether the requirement can be met through a supported integration. Custom development becomes a separate decision when the workflow genuinely exceeds the platform.
6. Customers meet outdated or contradictory information
Compare services, contact details, prices and delivery statements across the site. Contradictions often point to a content governance problem. Rebuilding without identifying an owner for each source simply gives that problem a new interface.
Create a list of what stays, what changes and what should disappear. Keep valuable existing pages and URLs unless there is a clear reason to move them. Google's site move guidance is relevant when a redesign changes addresses.
7. Performance problems survive small repairs
Measure the pages and devices affected. Large media, third-party scripts, server response and unnecessarily heavy components can have different owners. A slow homepage does not prove every page needs rebuilding. Ask for before-and-after measurements on representative routes and a check that customer tasks still work.
Turn the diagnosis into a decision
- Repair: the platform works, but a contained form, content or layout defect needs correcting.
- Redesign: the platform remains suitable, while navigation, templates and content presentation need substantial work.
- Rebuild: the current system cannot reasonably support the agreed workflow, editing or integration requirements.
Ask the supplier to connect each proposed change to an observed problem and an acceptance check. “A modern website” is difficult to verify. “A customer can find maintenance coverage, submit a valid enquiry and receive confirmation on mobile” is a deliverable you can test.
Keep a short decision record
For each warning sign, save the affected URL, the task attempted, what happened and the smallest proposed repair. Retest that task after the repair. If the defect disappears, it is no longer evidence for rebuilding the whole platform. If several critical journeys share the same structural limit, record that dependency in the redesign brief.
Bring that evidence to a website redesign discussion, with a list of URLs and content that must survive the change.
