A dated colour palette is easy to notice. A service page that attracts the wrong enquiries, a menu that conceals an important offer or a form nobody has tested can matter more. The case for a redesign should begin with those effects, not with the year the website was built.
Use the ten checks below as a diagnosis. For each problem, record the page, the task that becomes difficult and whether the issue repeats elsewhere. One fault may need a repair. Several connected faults can justify changing the system behind them.
1. The presentation makes important information harder to read
Outdated design becomes a practical problem when it weakens hierarchy: cramped paragraphs, inconsistent type sizes, decorative backgrounds behind text or several competing calls to action. Fashion alone is a poor test. A restrained older website may still communicate more clearly than a recent, visually elaborate one.
Open a substantial service page and identify its main point, supporting evidence and next step. Then inspect a second service page. If the same information has a different visual treatment each time, readers must learn the layout repeatedly. Replacing a single poor photograph is a small edit; restoring a consistent hierarchy across the site is a stronger reason for design work.
2. A normal task becomes awkward on a phone
Choose a realistic task: find a particular service, check whether it covers your location and start an enquiry. Complete it on a phone without rotating the screen or relying on your knowledge of the site. Note clipped text, tiny menu controls, hidden content and buttons covered by banners.
Test the form with the keyboard open. An interface can fit the screen while leaving too little room to understand an error or reach the submit button. If one element fails, repair it. If every page relies on desktop positioning that breaks when content wraps, the responsive layout needs broader attention. Keep a record of the affected tasks so the new brief describes usability rather than simply asking for “mobile-friendly design”.
3. Navigation reflects the company’s history rather than its offer
Services added over several years can end up under old department names or unrelated menu items. Visitors see the results of internal decisions without having the context that made them understandable. Renaming one menu label may not fix the page structure beneath it.
Ask someone unfamiliar with the site to find a specific capability. Give them a task rather than hints. Observe their first choice, where they hesitate and whether the destination answers the question. Repeat with another service. If both journeys require guessing, review how the offer is grouped. The aim is predictable choices, not an arbitrary maximum number of clicks.
4. Interested visitors meet an unclear or broken enquiry route
Follow the path from a useful service explanation to contact. A page that ends without a relevant action can leave the visitor uncertain. A form that asks for detailed procurement information before an initial conversation can create a different barrier. The next step should fit how the business sells.
With the team’s knowledge, send a labelled test enquiry and confirm that it reaches the right person. Check errors and confirmation too. A delivery fault deserves an immediate repair, even if a redesign is planned. If the inbox is simply quiet, use our guide to why websites fail to generate enquiries to distinguish a traffic problem from a problem in the customer journey.
5. Customers keep asking what the business actually does
Repeated basic questions can expose unclear positioning. A homepage that promises “complete solutions” may never state the service, the intended customer or the boundaries of the work. Polished language is not useful if prospective clients must decode it.
Compare the site with recent enquiry conversations. Are people assuming you supply a product when you only install it, or requesting domestic work from a commercial specialist? Rewrite one important introduction in specific terms and check its supporting pages. If the correction needs to reach navigation, service descriptions and project selection, the problem is broader than a headline. That gives a redesign a concrete content objective.
6. Routine content changes are difficult or risky
Ask the person responsible for the website to demonstrate a normal update: changing a service detail or publishing an approved project. Watch the actual process. It may require entering the same information in several places, rebuilding a layout manually or asking someone to fix what the edit breaks.
Identify the cause before recommending a new platform. Missing training, unclear responsibility and lost access can all make a sound system feel unusable. A rebuild is easier to justify when the content model itself causes repeated work, or when a small change regularly disrupts unrelated pages. The future editing task should be demonstrated during the redesign review, not left as a promise at handover.
7. People cannot use the site comfortably in different ways
Put the mouse aside and try the menu and contact route using the keyboard. Enlarge the text. Check whether focus is visible, information disappears or fields lose their labels. These checks reveal barriers that a screenshot cannot show.
W3C’s Easy Checks for accessibility provide a practical starting point while making clear that a preliminary review is not a full evaluation. Use our business accessibility guide for further context. An isolated missing label can be corrected directly. An inaccessible navigation pattern repeated across the site calls for a shared solution and proper testing, whether that is delivered as a repair or within a redesign.
8. Slow behaviour or fragile technology keeps returning
Distinguish a slow page from a confusing one. If the menu responds promptly but its labels make no sense, that is an information problem. If pressing it produces a noticeable wait, investigate performance. A new visual treatment would not necessarily address either cause.
Record the affected pages and actions, then ask whoever maintains the site what causes the delay or failure. One oversized image may explain much of the problem. Repeated dependence on unsupported components or changes that break other functions points towards deeper work. Our Core Web Vitals guide helps interpret performance evidence. Avoid treating one tool score or a platform’s age as a sufficient reason to replace everything.
9. Important services have no clear route from search
Search visibility is a symptom to investigate, not proof that the design is wrong. A useful service might be mentioned only inside an image, hidden in an unrelated page or split between several weak descriptions. In those cases, the site may lack a coherent page that answers the prospective buyer’s need.
Review relevant Search Console queries and landing pages over a meaningful period. Check whether the intended page is accessible, indexable and linked from the rest of the site. If information exists but a setting blocks it, correct the setting. If the offer has no adequate home within the current structure, include that in the redesign brief. Low traffic alone cannot tell you which explanation is right.
10. The website describes a business you no longer run
A company can change its specialism, project scale or geographical coverage while the website remains accurate only in a narrow, historical sense. Individual statements may still be true, but their combined emphasis directs visitors towards the wrong understanding.
Compare the current site with three recent pieces of work and the services you want to be approached about. Are those capabilities visible, supported by relevant evidence and connected to contact? Our earlier article on a website underselling its business explores that representation gap. Here, record which page relationships need to change and which useful information must survive, so the observation becomes an actionable brief.
Turn the findings into a proportionate decision
Do not total the signs and assume that a particular score means “rebuild”. A single broken enquiry form may be urgent. Several minor visual inconsistencies may be less important. Prioritise the effect on customers and the cause of each problem.
Repair a contained fault
Fix broken links, inaccurate details, oversized images and isolated form problems when the surrounding system works. Record the result and check the task again. Useful repairs need not wait for a larger project.
Redesign a repeated pattern
When the same weakness affects several pages, define the shared improvement: clearer service grouping, consistent mobile layouts or a manageable content structure. Our redesign versus rebuild comparison helps turn that diagnosis into a scope. The cost guide and timeline guide can then help you plan it.
If the work needs internal approval, turn the diagnosis into a website redesign business case that compares proportionate options and names the evidence behind them.
Bring those observations to a website redesign discussion. A short list of affected tasks, evidence and priorities is a better starting point than asking for the whole site to feel more modern.