You have a website. It's been around for a while. Lately you've noticed it's not performing the way it used to, or maybe it never performed well at all. Before you decide what to do about it, you need to know whether you're looking at a repair job or a replacement.

This matters because the decision changes everything: the time, the cost, and how fast you'll see results.

The website that just needs fixing

Some websites are fundamentally sound but have gotten neglected. These are good candidates for a repair approach.

Your site probably just needs fixing if:

The structure and layout still work. Visitors can find what they're looking for without confusion. The pages are organized in a way that makes sense for your business. If someone lands on your site, they know what you do and how to contact you or buy from you.

The problem is specific and visible. A contact form that doesn't send emails. A page that loads slowly. Mobile buttons that don't work right. A form field that's broken. These are concrete, fixable problems.

Your site is reasonably recent. "Recent" typically means built within the last five to seven years. Older sites often have invisible problems beneath the surface—outdated code that makes them slow, security vulnerabilities, or a design that doesn't work on phones.

Content is the main issue. The site structure is fine, but the copy is stale, the photos are bad, or the messaging doesn't match your current business. This is absolutely something you can fix without rebuilding.

Fixing means you hire someone to solve the specific problems. It's faster and cheaper than rebuilding. It's the right move if you like your site's general layout and it's doing most of what you need it to do.

The website that needs replacing

Some websites have problems so fundamental that patching them up wastes time and money. These need to be rebuilt from the ground up.

Your site probably needs rebuilding if:

It looks outdated. If your website still looks like it was made in 2015 or 2018, it signals to visitors that your business might be outdated too. Design expectations have shifted. Mobile-first design is not optional anymore. If your site doesn't look current and modern, visitors won't trust it.

It doesn't work well on phones. This is non-negotiable. A huge portion of traffic comes from mobile devices. If your site is clunky on a phone, people leave. If your site was built before responsive design became standard, fixing it might require rebuilding it anyway.

It's slow. You've had a developer look at it and they've said the underlying code is a mess, or that the hosting is the problem. Speed issues that can't be solved with a quick fix require a rebuild.

The structure doesn't fit your business anymore. You've changed what you do, or you want to add services your site can't accommodate. The layout forces customers through a confusing path to find what they need. If you have to rethink the whole customer journey, you're rebuilding.

You can't update it yourself. If every small change requires hiring someone, and even then it's expensive or slow, the site's foundation is probably too rigid. A new site should let you change text, images, and basic content without a developer.

It's built on very old technology. If your developer says it's on a platform that's no longer updated, or if nobody can maintain it anymore, it's time to move on.

The problems are everywhere. It's slow and ugly and clunky on mobile and the contact form doesn't work and the photos are bad and the copy needs rewriting. When the list is that long, you're not fixing things—you're replacing them.

The honest trade-off

Rebuilding is faster than fixing multiple problems. But it does mean starting over. You'll lose any customizations that were specific to your old site. You'll need to move your content over, which takes time even if someone else does it.

Fix if you have one or two specific issues and you like the overall site. Rebuild if the site is fundamentally not working for you.

How to decide

Ask yourself: if I walked into a competitor's newer website right now, would I think theirs was clearly better? If yes, you probably need to rebuild.

Ask a few people who aren't you: does the site look professional? Is it easy to use? Can they find what they came for? If they hesitate or say "kind of," rebuilding is likely the answer.

Get a second opinion from a web professional. A quick audit can tell you whether the problems are surface-level or structural. Most audits are cheap or free.

If you're in doubt, rebuilding is usually faster and less painful than spending months patching a site that was never quite right in the first place. The goal is a website that actually works for you, not one that's been maintained back to life.