How to Decide Between a Website Redesign and Targeted Improvements
A website redesign can be the right investment when the current site no longer supports your customers, content, or business goals. But a weak conversion rate or a dated homepage does not tell you how much needs to change. Some problems can be fixed within the existing platform; others will keep returning until the underlying systems change.
The decision starts with identifying what is failing, why it is failing, and whether your current setup can support a lasting improvement.
These questions were central to TechBehemoths’ Web Development Expert Insights 2026 — Second Edition, which featured First Line Software’s Natalie Miller alongside contributors from Relia Software and Identixweb. Following from that discussion, here is a practical way to decide what to fix first and what to ask a development partner.
How do you know whether your website needs a full redesign
Start with the work the website needs to do. For a B2B services company, that might mean helping buyers understand an offering, evaluate the company’s experience, and submit an enquiry. For an ecommerce business, it includes finding products, understanding availability, and completing checkout.
Choose one important journey and follow it on the devices your customers use. Combine that review with analytics, customer feedback, and technical testing.
A drop in form submissions, for example, could come from a broken form, unclear service information, less relevant traffic, or a slow mobile page. Each calls for a different response. Confirm that tracking works before treating the numbers as evidence of a website problem.
The scope should follow the diagnosis:
| What you find | A sensible next step |
| A broken form, confusing navigation, or an isolated performance issue | Investigate and fix the affected journey within the existing site |
| Repeated problems across shared templates or components | Improve those components and test the effect across affected pages |
| Publishing, content reuse, or integration requirements that the current setup cannot reasonably support | Assess the CMS and architecture before deciding on a migration or rebuild |
| A new business model or customer journey that changes much of the site’s purpose | Evaluate a broader redesign alongside the required platform changes |
A visual refresh, a redesign of the user experience, and a platform migration are separate decisions. Your project may need one or a combination.
What should you fix first when the budget is limited
Give priority to problems that prevent customers from completing important tasks. A failed checkout or inquiry submission deserves attention even if another page receives more visits.
Once those failures are addressed, compare opportunities using four questions:
- How important is this journey to customers and the business?
- What evidence suggests that the problem is affecting outcomes?
- How much effort will the change require, including testing and maintenance?
- Will the improvement remain useful if a larger rebuild follows?
Look beyond total traffic. A specialist service page with fewer visitors may generate more valuable inquiries than a popular informational article.
For example, if visitors read a service page but rarely complete its inquiry form, check the form itself, its mobile behavior, and what information it asks for. Review whether the page gives buyers enough confidence to get in touch. Establish which explanation is plausible before changing everything at once.
Start with a defined scope, measure the result, and use what you learn to guide the next decision.
When do website problems require changes to the CMS or architecture
Some difficulties originate in how content and systems are organized.
A marketing team may need developer support for routine page changes because templates are too restrictive. Regional teams may maintain separate versions of the same information. Product pages may require manual updates because the website is poorly integrated with business systems.
Ask a potential partner to identify the specific constraint. Could configuration, better content models, or a targeted integration solve it? What would a broader migration cost to implement and operate?
FLS’s work on O’Neill’s regional websites illustrates the distinction. The regional sites used separate CMS systems, creating excessive support requirements. The project consolidated them under a single Optimizely CMS. The scope addressed how the sites were managed as well as the customer-facing experience.
A composable architecture, in which capabilities connect through APIs, is one possible approach to complex requirements. It also introduces integration and governance responsibilities. Assess whether those trade-offs fit your team and operating budget before selecting a platform.
What should you ask before hiring a web development partner
A useful proposal should explain how the partner will investigate your situation and support what they deliver. These questions help make that discussion concrete.
What evidence will you use to recommend the scope
Ask how the team will review user journeys, analytics, accessibility, performance, content operations, and integrations. Request a clear explanation of what needs to change, what can stay, and why.
Which changes will our team be able to make independently
Ask for a demonstration of routine tasks: creating a service page, updating navigation, reusing content, and managing approvals. Agree on which tasks belong with editors and which require engineering.
Can you show how a comparable project has evolved after launch
Discuss maintenance, upgrades, changes in requirements, and the client team’s ability to use the system. This reveals more than launch screenshots alone.
Who will deliver the work and support it afterward
Clarify the delivery team, responsibilities, escalation process, documentation, and handover. Understand how later improvements will be scoped and funded.
How will you protect existing search visibility and measure results
If URLs, content, or platforms change, ask about redirects, tracking, migration checks, and monitoring. Agree on the business outcomes and technical measures before delivery begins.
How do you measure whether the improvements worked
Choose measures that match the problem you are solving and record a baseline before making changes.
| Improvement | What to measure |
| An inquiry journey | Successful submissions, completion rate, and inquiry quality |
| A mobile purchase journey | Checkout completion, errors, and performance on relevant devices |
| Publishing workflows | Time and effort required to create, approve, and publish content |
| A CMS consolidation | Maintenance effort, duplicated work, and the reliability of shared operations |
Compare equivalent periods and account for changes in traffic sources, campaigns, and seasonality. Where feasible, use controlled tests to assess the effect of a change.
Assign someone to review the results and decide what happens next. That turns the first round of improvements into evidence for future investment.
How First Line Software can help assess your next step
First Line Software’s CMS and digital experience architecture services cover assessment, implementation, integration, migration, and ongoing support. We help teams evaluate their current environment and choose an approach that fits their content, customer journeys, and operational needs.
If your website is becoming harder to use or maintain, start by identifying the constraints. That assessment can establish where targeted improvements will help and where broader changes deserve investment.
Discuss your website and CMS priorities with our team.
Last Updated: October 2026