How to Compare Your Website Against a Competitor Before a Redesign

Most redesign projects begin with opinions that sound urgent and expensive.

"We look dated."

"Their site feels sharper."

"Our homepage is not premium enough."

Those comments are not always wrong. They are just incomplete.

Before a redesign, the better question is not whether a competitor looks better. It is whether the competitor communicates, routes, proves, and converts better for the same buyer job. That is a very different investigation.

If you want the hands-on comparison environment for this, SavageAudit's compare websites is the product surface. This article is the pre-redesign workflow teams should run before they turn a redesign into a taste contest.

Why competitor comparison matters before a redesign

Redesigns fail when teams change the paint without diagnosing the leak.

Sometimes the real problem is visual credibility. Sometimes it is weak proof, confusing navigation, poor mobile flow, or message mismatch. If you do not compare your site against a live alternative in a structured way, you risk solving the wrong problem with an expensive design cycle.

A useful competitor comparison does three things:

1. shows what the competitor is doing better
2. shows what they are doing worse
3. turns those differences into redesign priorities instead of inspiration-board noise

Step 1: Pick one competitor and one buyer job

Do not start by comparing your site against eight competitors at once.

Choose one direct competitor and one specific buyer job.

Examples:

• evaluate homepage audit tools
• compare SaaS demo page optimization services
• shortlist full-site audit providers
• find a website comparison workflow before redesign

Why this matters:

If you compare everything at once, the exercise gets vague. A redesign needs grounded trade-offs, not broad market commentary.

Step 2: Build a page inventory before judging design

List the equivalent pages on both sites.

At minimum, compare:

• homepage
• core offer or product page
• pricing or plan page
• trust or About page
• one high-intent supporting page
• one educational or blog page if content matters in the category

This helps because many redesign conversations compare one polished competitor page against your entire messy site. That is not a fair test.

You need page-role parity before you need visual opinions.

Step 3: Compare positioning and message clarity

This is where many redesigns uncover a content problem disguised as a design problem.

Check both sites for:

• headline specificity
• target audience clarity
• value proposition strength
• plain-language outcome framing
• uniqueness of the offer

Ask:

• Which site makes the category easier to understand?
• Which site says who it is for faster?
• Which site translates features into business outcomes more clearly?
• Which site feels less dependent on internal jargon?

A competitor may look better largely because their copy is more disciplined.

If that is the case, redesign energy should include messaging strategy, not just visual refresh work.

Step 4: Compare information architecture and navigation

Before redesigning the homepage hero, check whether the site is routing people properly.

Compare:

• top-level navigation labels
• page hierarchy
• how quickly users can reach key pages
• whether the site reflects real buyer questions
• whether important supporting pages exist at all

A competitor often wins not because every section is prettier, but because the site is easier to traverse.

That matters for both users and discovery systems.

Clean navigation improves:

• conversion path confidence
• content discoverability
• topic clustering
• internal linking

If you want the broader leak framework around this, SavageAudit's website audit categories is the right companion page.

Step 5: Compare proof and trust density

A lot of sites lose before redesign because they are under-evidenced.

Compare both sites for:

• testimonials
• customer logos
• case studies
• screenshots
• quantified claims
• founder or company credibility
• legal and trust basics

Ask:

• Which site shows more believable proof earlier?
• Which claims are backed by specifics instead of adjectives?
• Which company feels more real from the public-facing site alone?

This matters because teams often copy surface-level design cues from competitors while ignoring the real persuasive gap: the other site simply proves more.

Step 6: Compare conversion paths, not just CTAs

A button label is only one part of the path.

Compare:

• primary CTA choice
• number of competing CTAs
• placement of the CTA
• clarity around what happens after the click
• form or booking friction
• use of secondary or lower-commitment paths

Then ask:

• Which site asks for commitment at the right time?
• Which site makes the next step feel less risky?
• Which site better matches traffic intent to action path?

Many redesigns focus on button style while ignoring that the underlying step feels too expensive.

That is not a design polish issue. It is a conversion strategy issue.

Step 7: Compare content depth and search support

If content plays any role in the category, compare the supporting content system too.

Look for:

• category explainers
• comparison pages
• FAQ coverage
• methodology pages
• educational blog content

Ask:

• Which site answers more of the next obvious questions?
• Which site has better supporting content around commercial pages?
• Which site appears to be building topical depth instead of relying on one sales page?

This matters because a redesign often gets framed as a homepage project when the real competitive moat sits in the supporting page layer.

Step 8: Compare mobile experience and performance

Do not let both teams judge the comparison from desktop screenshots alone.

Compare:

• mobile readability
• navigation usability
• form friction on small screens
• page speed and perceived load quality
• stability of layouts and media

A competitor can feel more premium simply because the site is faster and calmer to use.

That is useful to know before you spend months redesigning card styles.

Step 9: Build a scorecard instead of a vibe report

At this point, turn the comparison into a scorecard.

Use categories like:

The key is that every "we are weaker here" note should become a redesign implication, not just a complaint.

Step 10: Separate copy problems, UX problems, and visual problems

This is one of the most useful outputs of the whole process.

Once you compare the sites properly, sort the findings into three buckets.

Copy problems

These include:

• vague headlines
• weak differentiation
• poor objection handling
• unclear page roles

UX problems

These include:

• confusing navigation
• hard-to-find next steps
• bad form flow
• poor mobile behavior

Visual problems

These include:

• dated styling
• weak hierarchy
• inconsistent spacing
• low-quality imagery

Why this separation matters:

Teams often run a redesign trying to fix copy, UX, and visual problems with one giant visual-system sprint. That almost always creates unnecessary noise.

A better redesign sequence usually starts with diagnosis, then messaging and architecture, then interface refinement.

What not to do

When comparing your site against a competitor before a redesign, avoid these traps.

• Do not copy their visual language without understanding why it works
• Do not assume higher polish means higher conversion
• Do not judge only the homepage
• Do not ignore your existing strengths
• Do not redesign around opinions that were never tested against real alternatives

Competitor comparison is useful because it sharpens your understanding, not because it gives you permission to imitate.

What a strong output looks like

A good competitor comparison should end with conclusions like these:

• our homepage message is weaker than theirs, so copy strategy comes before visual redesign
• our proof density is lower, so the redesign needs evidence architecture, not just layout updates
• our navigation hides important pages, so IA cleanup is part of the redesign scope
• their mobile flow is cleaner, so responsive UX deserves explicit work, not cleanup at the end

That is how the exercise becomes actionable.

A practical redesign priority order

If you want a reliable sequence after the comparison, use this one.

1. Fix positioning and page-role clarity
2. Improve trust and proof surfaces
3. Repair conversion path friction
4. Simplify information architecture
5. Upgrade visual design on top of those decisions

That order reduces the chance of a beautiful redesign that still underperforms.

The better pre-redesign question

Do not ask, "Why does their site feel better?"

Ask, "Which specific job does their site perform better than ours, and what system change would close that gap?"

That question is how redesign work becomes strategic instead of decorative.

If you want the direct head-to-head workflow, use SavageAudit's compare websites. If you need the broader site diagnosis before comparison, step back into full-site audit first.

Redesigns should not begin with envy.

They should begin with evidence.