Five signs your business website needs more than a visual refresh
Use mobile task failures, inaccurate content, broken enquiries, missing evidence, and publishing friction to decide between targeted repairs and a redesign.
A redesign needs evidence of a shared problem
An old-looking website is not automatically a failing website. Before replacing it, identify tasks that visitors cannot complete and changes the business cannot make reliably. A redesign is easier to justify when several failures share a structural cause: confusing navigation, unsuitable templates, or a publishing system that prevents accurate content.
Collect observations in a short issue register. Record the page, task, failure, affected visitor, and smallest plausible repair. This prevents a broken form from becoming a six-month branding exercise while enquiries continue to disappear.
1. Mobile visitors cannot complete the main task
Test an actual journey on a narrow screen: identify a service, understand its scope, and submit an enquiry. Look for clipped controls, obscured buttons, unreadable errors, and content that changes position while someone tries to use it. Include keyboard operation and enlarged text rather than treating a mobile screenshot as the whole assessment.
If one widget is broken, replace or fix it. If every page repeats the same layout and navigation barriers, template-level redesign becomes a more credible scope. Keep the evidence attached to the task, not to a reviewer’s personal taste.
2. The content describes a previous business
Ask someone unfamiliar with the company to explain what it sells after reading the relevant page. Compare that answer with the current offer. Missing exclusions, obsolete packages, and ambiguous next steps are content defects even when the typography is attractive.
Correct urgent inaccuracies immediately. Then determine whether the content model can express the information properly. If editors must force every service into a generic block of promotional copy, changing the model and templates may be more valuable than rewriting the same field again.
3. Enquiries fail or lose context
Submit a clearly marked test enquiry and follow it to the intended destination. Verify what happens after invalid input, a network failure, and a downstream outage. A success banner without a stored request is not success. W3C’s forms guidance emphasizes understandable error and success feedback; this is a practical acceptance criterion, not a decorative detail.
Record whether sales receives enough context to respond. A short form can be appropriate, but hidden routing errors or missing service identifiers can create manual work. Fix data flow and user feedback together.
4. Nobody can explain whether changes help
Missing measurement warrants a measurement repair before a large redesign decision. Choose a baseline period, define an accepted enquiry, and distinguish browser events from server acceptance and later sales qualification. Low traffic or incomplete consented analytics may limit the conclusions; record that uncertainty.
Search Console can help inspect discovery and indexing, but it does not replace enquiry records. Review the journey using more than one signal and investigate tracking changes before interpreting a sudden difference as visitor behavior.
5. Routine publishing repeatedly requires engineering
Time a representative update from request to verified publication. Note where it waits: approval, missing assets, template constraints, deployment, or fear of breaking other pages. A slow approval process will not be fixed by a new JavaScript framework.
Use a small repair decision before commissioning replacement. This example is a review record rather than application configuration.
issue: service-pages-cannot-show-deliverables-consistently
evidence_required:
- examples-from-affected-pages
- editor-walkthrough
smallest_trial: add-structured-deliverables-to-one-template
verify:
- editor-can-update-without-source-code
- long-content-remains-readable
- preview-matches-published-page
- enquiry-path-still-works
expand_redesign_if: shared-template-limits-remain-after-trial
Choose the smallest coherent intervention
Group confirmed issues by cause. A form repair, content update, and accessible navigation fix may solve the immediate problem. A broader redesign is warranted when those repairs require changing the same underlying structure and doing them separately would create repeated rework.
Include accessibility in planning, implementation, and ongoing review, as W3C recommends. Assign owners and verification steps to the chosen scope. The useful outcome is a site that supports the business and its visitors, with evidence that the identified failures have been addressed.