Insights
7 Signs Your Business Website Needs a Redesign
A website does not need rebuilding simply because it is old. A redesign becomes justified when it creates measurable friction, becomes difficult to maintain, misrepresents the business or cannot support current requirements. Diagnose the problem first; an improvement may be more reasonable than replacement.
By Mythos Web Studio · Published · Updated
1. Mobile usability problems block ordinary tasks
Check for text requiring zoom, clipped content, overflowing layouts, difficult navigation, small controls, broken forms and poor responsive behavior. Try a complete inquiry on a phone, including the keyboard and confirmation step, rather than checking only the homepage screenshot.
Google uses the mobile version of content for indexing and ranking. Its guidance recommends equivalent important content on mobile and desktop. WCAG 2.2 also addresses pointer targets: its Level AA minimum is 24 by 24 CSS pixels, subject to spacing and other stated exceptions.
These are practical checks, not proof that a whole rebuild is needed. A broken form or a few cramped controls may be repairable within the existing site.
Mobile indexing guidance: Google Search Central: Mobile-first indexing best practices.
Target-size guidance: Success Criterion 2.5.8 in W3C: Web Content Accessibility Guidelines (WCAG) 2.2.
2. Visitors cannot understand the business
Can someone unfamiliar with the company explain what it does, who it serves, where it operates and what to do next? Test that with actual service information rather than relying on a broad slogan or decorative hero image.
Confusing information architecture and vague copy can make a suitable service difficult to evaluate. Reordering content, naming services clearly and giving related questions their own place may solve the problem without rebuilding the underlying system.
3. Important actions are difficult to find
Follow the visitor’s likely journey: View Services, Request a Quote, Book an Appointment, Call, Contact or Purchase. Does the relevant action appear where the decision happens, and does its label describe the destination?
Test the entire path, including errors and confirmation. A visible button that opens a broken form is still a failed customer task. Mythos plans information and actions around those journeys, with visual design supporting the task rather than substituting for it.
4. The site no longer represents the business accurately
Look for obsolete or missing services, outdated staff, incorrect contact information, old photos, superseded policies, broken forms and branding that no longer matches the business. These are factual content-management issues, not an argument for following every design trend.
Assign responsibility for updates. If useful information exists but is hard to maintain, improving the editing workflow may be more valuable than changing the visual theme.
5. Performance problems interrupt the experience
Google’s Core Web Vitals measure loading, responsiveness and visual stability. Good targets are LCP of 2.5 seconds or less, INP of 200 milliseconds or less and CLS of 0.1 or less, assessed at the 75th percentile and separately for mobile and desktop. A single lab score is not a complete picture of real visitors’ experience.
Poor Core Web Vitals do not automatically mean the entire website should be rebuilt. Image optimization, script cleanup, faster rendering or stable layout sizing may be sufficient. First identify which pages and customer tasks are affected, then diagnose the responsible implementation.
Google’s overview: Google Search Central: Core Web Vitals.
Thresholds and measurement: Google web.dev: Web Vitals thresholds and measurement.
6. Accessibility and readability need attention
WCAG provides testable guidance on contrast, text resizing, reflow, navigation and target size. Check readable typography, meaningful headings, keyboard access, visible focus, zoom behavior and form labels. People should be able to understand the page and complete its tasks without fighting the interface.
Some issues can be corrected in existing styles or components; a deeply inconsistent structure may need wider work. These observations are a starting point for review, not a claim of full accessibility or legal compliance.
Accessibility reference: W3C: Web Content Accessibility Guidelines (WCAG) 2.2.
7. The website cannot support where the business is going
New scheduling, payments, portals, databases, CRM connections, automation, advanced forms or multiple service paths can change what the website must do. Compare these actual requirements with the current platform and architecture before adding more components.
Repeated additions to an unsuitable implementation may eventually make a rebuild more reasonable. But an existing platform may already support the need through its own tools or a well-scoped integration. Plan data ownership, access, maintenance and the customer journey alongside the interface.
Diagnosis first: repair, redesign or rebuild?
A good developer should be willing to recommend not rebuilding when the existing website can reasonably be improved. The objective isn’t ‘How can we replace this website?’ It is ‘What is preventing this website from doing its job, and what is the most reasonable way to correct it?’
Mythos starts with that diagnosis. The answer could be one-page improvement, mobile cleanup, performance work, design restructuring, platform work or a complete rebuild. Agree the problem and the scope before committing to implementation.
For theme, plugin or maintenance concerns, see WordPress redesign and modernization options.
Explore examples in the selected client website work.
Sources & Documentation
Documentation and published pricing checked on . These references support the platform facts and benchmarks above; the project recommendations are Mythos’s professional guidance.