When to Redesign a Website Versus Repairing What You Have

Repair your website when the problems are specific and the site's structure still fits your business: a broken form, an outdated service list, a slow page, a confusing menu link. Consider a redesign when several basic things fail at once: the navigation no longer reflects what you offer, customers struggle to finish tasks on a phone, content is out of date across many pages, and routine updates are hard to make.

The age of a site does not decide it on its own. An older site with a sound structure may only need repairs. A newer site built on the wrong structure may need more. Many projects land in between: fix what is urgent now, and plan larger changes separately.

Start by finding out what is actually wrong

Before choosing between repair and redesign, write down the problems and where they happen. Three quick checks help:

• Try real customer tasks on a phone. Find a service, read how pricing works, and contact the business. Note exactly where each task gets slow, confusing, or stuck.
• Compare the site with your business today. Look for services you no longer offer, questions customers ask that the site does not answer, and the same information repeated in several places.
• List the updates you avoid. Note the changes your team puts off because the tools are awkward, nobody has access, or nobody knows how.

For each problem, note whether it lives in one place or shows up across the whole site. That one distinction settles most of the decision.

When a repair is usually enough

These problems are usually local and can often be fixed without rebuilding:

• A contact form stopped delivering messages.
• Hours, phone number, prices, or a service list are out of date.
• One page loads slowly because of oversized images.
• A menu label is confusing or a link is broken.
• A specific accessibility problem, such as an image without a text description or a form field without a label.

A repair makes sense when the problem is isolated, the current platform can support the fix, the page structure still matches how customers choose you, and your team can handle routine updates. A repair is still real work and should be scoped in writing. It is just smaller.

When a redesign deserves a serious look

These signs point to structural problems:

• The structure no longer fits. Your services have changed, and the navigation cannot show them clearly without a rebuild.
• Phone visitors struggle everywhere, not on one page. The layout itself does not work at small screen sizes.
• Most of the content needs rewriting anyway. If nearly every page is outdated, much of the work of a redesign is already on your list.
• Updates are hard. Simple edits need a developer, access is unclear, or the platform is difficult to maintain.
• Problems are built into the templates. Speed or accessibility issues repeat on every page because they come from the shared layout, so fixing one page does not fix the rest.
• The site cannot support what the business needs now, such as online booking or clear pages for each service area.

One of these alone may still be a repair. Several together usually mean that patching will keep costing time without solving the underlying problem.

Measure speed and accessibility before you decide

Speed and accessibility are common reasons people consider a redesign. Measuring them first tells you whether you are dealing with one fixable issue or something built into the whole site.

Page speed: Core Web Vitals

Google's Core Web Vitals measure three parts of how a page feels to use:

• Largest Contentful Paint (LCP): how long the main content takes to appear. Google recommends within 2.5 seconds.
• Interaction to Next Paint (INP): how quickly the page responds when someone taps or clicks. Google recommends under 200 milliseconds.
• Cumulative Layout Shift (CLS): how much the page jumps around while it loads. Google recommends a score under 0.1.

According to Google's Web Vitals guidance, these targets are assessed at the 75th percentile of page loads, separately for mobile and desktop, and the set of metrics can change over time. If your site is set up in Google Search Console, its Core Web Vitals report shows how your pages perform for real visitors.

A poor result on one page often has a specific cause, such as a very large image or a heavy script, which a repair can address. Poor results on nearly every page may point to the shared layout or the platform. Google recommends good Core Web Vitals, but they are one part of how pages are evaluated, not a guarantee of rankings, traffic, or sales.

Accessibility: WCAG 2.2

The W3C's Web Content Accessibility Guidelines (WCAG) 2.2 is a widely used set of recommendations for making web content more accessible. One example: images that carry information need a text alternative that serves the same purpose. The W3C notes that following the guidelines makes content accessible to a wider range of people with disabilities, but will not address every user need.

A missing image description or an unlabeled form field is usually a repair. If menus, forms, and interactive parts are hard to use with a keyboard or screen reader on every page, the fix may reach into the templates and look more like a redesign. This article is not a legal assessment; accessibility obligations depend on your situation.

Questions to answer before you choose

• Is each problem in one place, or built into every page?
• Does the current structure match how customers choose you today?
• Can your team make routine updates without a developer?
• Is the platform still supported and practical to maintain?
• How much of the content would you rewrite anyway?
• Over the next year, will repeated fixes cost more time and money than a planned rebuild?

If most answers point to local problems, repair first. If most point to structure, plan a redesign.

If you redesign, protect what already works

A redesign should keep what customers and search engines already rely on:

• Make an inventory first. List your pages, content, images, forms, integrations, hosting, DNS, and who owns each account. Decide what stays, changes, or goes before agreeing on scope.
• Map every old URL. Keep useful addresses when you can. When one must change, redirect it permanently to the closest matching new page, not to the homepage.
• Test real tasks before launch. Use a phone, submit a test inquiry, and confirm where it arrives.
• Check after launch. Confirm that forms and email still work, and look for errors in Search Console.

A careful migration reduces avoidable problems. It cannot guarantee rankings or uninterrupted search traffic. The website ownership checklist helps you keep control of your accounts during the move.

How Wild Logic approaches repair and redesign

Wild Logic's website redesign guide starts with the same distinction: an outdated service list, a failed form, or a confusing menu may need a targeted fix, while a redesign may make sense when the structure no longer fits the business, routine updates are difficult, or customers cannot complete important tasks on a phone. The guide covers the inventory, URL map, task testing, and launch steps in more detail.

For upkeep after launch, Website Care is optional. It includes scheduled health checks and a limited monthly allowance for routine changes. New pages, features, integrations, and redesigns are not included; they are scoped and priced in writing before work starts. Wild Logic keeps build costs, optional care, third-party expenses, and review-required scope separate.

Next step

Run the three checks above and write down what breaks. If the list points to a redesign, read the website redesign guide or configure a redesign in Build your site to see a planning estimate. If you are starting fresh, small business websites covers choosing a practical set of pages. If the list points to a few repairs, contact Wild Logic with your site address and the specific problems.