Redesign or rebuild? How to tell which your site needs.

Your website is underperforming and somebody has to decide what to do about
it. Quotes arrive ranging from $800 to $40,000 for what sounds like the same
thing. Everyone is confident; nobody has looked at your analytics. Welcome to
the most expensive coin-flip in web work.

Getting this call wrong costs in both directions. Rebuild a site that needed
ten fixes, and you’ve burned five figures on a problem worth five hundred
dollars. Refresh a site with structural rot, and you’ve gift-wrapped the same
failures — then you’ll pay again in eighteen months.

Three options, not two

The question is usually framed as redesign vs. rebuild, but there are three
tiers, and the cheapest one is criminally underused:

• Refresh — targeted fixes to the existing site: copy, images,
  speed, key pages. Days of work.
• Redesign — new design and content architecture on the
  existing platform. Weeks of work.
• Rebuild — new platform, new engineering, content migrated.
  The full project.

When a refresh is enough

Choose a refresh when the foundation is sound but the surface has drifted:
the platform is maintained and reasonably fast, the structure makes sense, but
the message is stale, photos are old, and a few key pages underperform. The
tell: people who know you say the site “still looks fine,” but the copy
describes the organization you were five years ago.

A refresh is also the right call when the real problem is
clarity — rewriting
a homepage costs a fraction of redesigning one, and converts better too.

When a redesign pays

Choose a redesign when the platform is healthy but the design actively
works against you: navigation visitors can’t follow, a structure that buries
what matters, mobile layouts that were clearly an afterthought, or a visual
identity that undermines trust with the audience you serve now. The tell:
analytics show people arriving and wandering — traffic without movement
toward action.

When only a rebuild works

Choose a rebuild when the foundation itself is the problem — and be honest
about the signs, because they don’t improve with paint:

• The site is slow
  at the platform level — theme bloat, plugin pile-up, hosting that buckles
  under load.
• Your team can’t edit content without breaking something (or someone).
• Security updates have lapsed beyond recovery, or the theme/page-builder
  is abandoned by its developers.
• The site can’t do what the organization now requires — giving, booking,
  membership — without duct tape.

A redesign on top of any of these is the most expensive way to keep the
problem.

How to decide with evidence

Three checks anyone can run before spending a dollar:

1. Speed: run PageSpeed Insights on mobile. Platform-level
   slowness points toward rebuild; one heavy page points toward refresh.
2. Editability: ask the person who updates content to change
   a homepage section while you watch. Their face is data.
3. Behavior: in analytics, find where visitors actually exit.
   Confused navigation says redesign; instant exits on slow pages say platform.

And one rule that protects you from every confident quote: never
accept a recommendation from someone who hasn’t looked. Diagnosis
before prescription — it’s the entire reason the
Clarity Audit exists,
and why ours ends in a straight call: refresh, redesign, rebuild, care, or
growth, whichever the evidence supports.