An old-looking website is not automatically a redesign project
The right reason to redesign is not that the site “looks like 2018”. It is that the site no longer helps people do what they came to do: understand the offer, trust the business, and take the next step.
Use the seven signs below as a practical screen. If several appear together, run a structured audit instead of applying a new visual layer to an old problem.
1. Visitors cannot explain what you offer quickly
Open the home page without context. Does the headline say who you help and what you do? Is the next step obvious? If the answer depends on a long scroll or a menu tour, the problem is usually message hierarchy, not logo size.
2. The site is acceptable on desktop but difficult on mobile
Test the menu, buttons, forms, images, multilingual text, and calls to action on a real phone. “Responsive” is not the same as usable. Check the actual tasks a visitor needs to complete.
3. Pages are slow, unresponsive, or visually unstable
Google describes Core Web Vitals through loading performance (LCP), responsiveness (INP), and visual stability (CLS). Its “good” targets are LCP within 2.5 seconds, INP below 200 milliseconds, and CLS below 0.1. These metrics do not replace user research, but they are useful technical signals.
Start with real-user data in Google’s Core Web Vitals report, rather than relying on one lab score.
4. Important content exists but is hard to find
If a service, pricing explanation, FAQ, or contact path is buried, the information architecture needs attention. Before creating more content, map the pages people need and the shortest route to them.
Google’s site-move guidance is useful preparation here too: it emphasizes URL mapping, link checks, and monitoring after a change.
5. The site is difficult to use with a keyboard or assistive technology
Accessibility is not a final plugin. Check contrast, focus states, form labels, image alternatives, heading structure, and whether key actions work without a mouse. WCAG 2.2 is a W3C standard with testable criteria. It is a starting point, not a substitute for professional review and user testing.
6. The site gets attention but not action
Separate the stages: do visitors reach the right page? Is the offer clear? Is the call to action appropriate? Is the form short and functional? Does the enquiry reach someone who follows up? Sometimes the answer is a conversion-path fix, not a full redesign.
7. Every small change creates operational risk
A business site should be maintainable. If updating a service, testing a form, or publishing a correction requires a fragile developer dependency, review the CMS, permissions, backups, monitoring, and publishing process. A new frontend without clear ownership can recreate the same problem next year.
What to check before you decide
- Collect your key entry pages, search queries, enquiries, and forms.
- Audit mobile usability, performance, accessibility, content, and conversion separately.
- Map every old URL to a destination. When URLs change, missing redirects can break user access and search signals; Google recommends permanent server-side redirects for permanent moves.
- Decide what must be preserved, improved, or removed.
- Define success before design starts: user tasks, enquiries, handling time, or easier maintenance—not simply “a nicer site”.
The practical conclusion
A redesign is justified when the site creates clear friction in messaging, usability, performance, accessibility, findability, conversion, or maintenance. If the problem is narrow, fix it narrowly. If several layers are failing together, an audit and a new plan are safer than another patch.
For a structured starting point, compare this list with EzraTech’s UX audit guide and business website brief checklist.