What I Actually Look at Before I Recommend a Website Redesign

Before I tell anyone to rebuild their website, I try to talk them out of it.

Not because redesigns are bad. Because most of the time, the thing costing them money isn't the design at all. And a rebuild that fixes the wrong problem is just an expensive way to stay exactly where you were.

So before I recommend anything, I look at five things.

The data first, opinions second. I don't start with how the site looks. I start with what people do on it. Where they land, where they drop off, what they ignore, how far they scroll. The analytics usually point straight at the real problem, and it's rarely "the whole thing needs to go."

Traffic problem or conversion problem. These need opposite solutions. If people are arriving and leaving, no redesign fixes that on its own; the message or the offer is off. If nobody's arriving at all, that's SEO and visibility, not layout. Diagnose this wrong and you waste the entire budget.

The message before the design. Most underperforming sites don't have a design problem. They have a clarity problem. If the headline talks about the company instead of the visitor's problem, people leave in seconds, and a prettier version of an unclear page just fails more attractively. Usually a copy fix, not a rebuild.

Speed and mobile reality. I check how fast the site loads on a mid-range phone on mobile data, not on a fast laptop. A slow load kills conversions and rankings at the same time, and it's often a performance fix rather than a full redesign.

Where trust is, and isn't. I look at whether proof shows up where doubt lives, right next to the ask, or whether it's buried on a page nobody visits. Moving social proof is a small change with an outsized effect. Again, not a rebuild.

After all of that, one of two things is true. Either I've found targeted changes that lift results without a full rebuild, which saves the client real money. Or the site does need a redesign, and now we go in knowing exactly what to fix instead of guessing.

A redesign should be a conclusion, not a starting assumption.

The goal was never a new website.

It was more revenue. Sometimes those are the same project. Often they're not.

If your site is underperforming and you're not sure whether you need a rebuild or just a few targeted fixes, send me a message. I'll tell you which one it actually is.