
Website redesign or fix what you have: how to decide
Every small business owner reaches the same point sooner or later. The website feels tired, someone says it needs a rebuild, and you are left wondering whether that is true or whether a few targeted fixes would do. This guide gives you some checks you can run yourself, a simple way to decide, and the questions to put to a developer before you commit any money.
It does not give you prices or promises. Costs and results depend on your site and your business, and nobody can honestly guarantee a ranking or a number of enquiries.
Start with what is actually wrong
"The site looks old" is a feeling, not a diagnosis. Before you decide anything, write down what you want the site to do (get calls, take bookings, sell products) and what is stopping it. Then test the site against things you can measure.
1. Speed and Core Web Vitals
Google publishes targets for what it calls Core Web Vitals. The "good" thresholds, measured at the 75th percentile of visits, are:
- Largest Contentful Paint (how quickly the main content appears): 2.5 seconds or less
- Interaction to Next Paint (how quickly the page responds when someone taps or clicks): 200 milliseconds or less
- Cumulative Layout Shift (how much the page jumps around as it loads): 0.1 or less
You can test your own pages against these using free tools such as PageSpeed Insights. If you pass, speed is probably not your reason to rebuild. If you fail, find out why before assuming the whole site is the problem. Oversized images and heavy add-ons are often fixable on their own.
2. Mobile experience
Google recommends responsive design, where one site adapts to any screen size. It also says your mobile site should contain the same content as your desktop site. Open your site on your phone and look for missing pages, hidden text, tiny buttons and menus that are hard to use.
A site that simply does not work on a phone is a strong sign that a rebuild deserves serious thought. A site that works but has awkward spots usually points towards fixes.
3. Accessibility
The W3C Web Accessibility Initiative has a set of quick checks you can run yourself, covering things like image descriptions (alt text), headings, colour contrast, zooming and form labels. The W3C is clear that these checks are only a starting point and are not exhaustive. Even so, they show you how much work lies ahead. A handful of failures can be corrected page by page. Failures everywhere, baked into the way the site is built, lean towards a rebuild.
Signs that fixing is enough
Fixing what you have usually makes sense when:
- The site works on phones and the content is the same as on desktop.
- The problems are specific: slow images, an out-of-date page, a confusing contact form, weak headings.
- You can still edit and update the site without a struggle.
- Your address structure (the URLs) is sound and people already find pages through search.
Google also makes a point worth remembering: chasing a perfect page experience score purely for search reasons may not be the best use of your time. Fixing the worst problems first is often better than rebuilding for a number.
Signs a redesign may be justified
A rebuild deserves a proper look when:
- The site does not adapt to mobile screens and cannot reasonably be made to.
- Core problems appear on every page because of how the site was built, not because of individual mistakes.
- The platform or theme is hard to update, so even small changes need specialist help each time.
- The site no longer reflects what you sell or who you serve, and patching it would mean replacing most of it anyway.
If several of these apply, a redesign may well be the more sensible route. If only one does, ask whether a fix would cover it.
A simple decision path
- 1Write down the goal. What should the site do for the business?
- 2Run the checks above. Speed, mobile and accessibility, on your most important pages first (usually the home page and your main service page).
- 3List the problems. Mark each as a quick fix, a larger fix or a structural problem.
- 4Compare. If most items are quick or larger fixes, fix first. If most are structural, get a rebuild quote and compare it with a fix quote.
- 5Decide in stages if you can. Fixing the worst issues first lets you see what difference it makes before you spend more.
If you do rebuild, protect what you have
A redesign can harm your search visibility if it is handled carelessly, mainly when page addresses change. Google's guidance for sites that change URLs is clear:
- Use server-side permanent redirects (such as 301s) from each old address to its new one.
- Point each redirect straight to the final destination, rather than through a chain of redirects.
- Keep the redirects in place for as long as possible. Google says generally at least a year.
Google states that 301 and other permanent redirects do not cause a loss in PageRank. It also says you may see ranking fluctuations while Google recrawls and reindexes your site, and that this is normal. For a medium-sized site it can take a few weeks or more for the new addresses to show. So do not panic in the first few days, and do not launch a rebuild in the middle of your busiest season.
What to ask a developer
Whether you are quoting for a fix or a rebuild, these questions help you judge the answer:
- What exactly is wrong with my current site, and how did you find out?
- Which of those problems would a fix solve, and which need a rebuild?
- How will you check the new or repaired site against Core Web Vitals and mobile use?
- Will my page addresses change? If so, how will you handle redirects, and for how long will they stay?
- Will I be able to edit the site myself afterwards?
- What happens if results are not what we hoped? (Be wary of anyone who promises rankings.)
A good developer will answer these plainly and will be happy to put the scope in writing.
The short version
Test first, then decide. Fix what is cheap to fix, rebuild only when the problems are built into the site, and protect your existing addresses if you do. Results vary and no change can promise more enquiries, but a clear list of problems makes every conversation with a developer more useful.
If you would like a second opinion on whether to fix or rebuild, our web development team can look at your site with you, or you can get in touch.
Continue Reading
Discover more insights and stories


