The redesign bills bigger. That's not a reason to start there.
If conversions are underperforming, a full rebuild is often the wrong first move. It resets your data to zero and most redesigns dip conversion before they lift it.
Our bias, declared
We sell both of these services, so we have every incentive to tell you a redesign is what you need. It bills bigger and takes longer. Our actual position: if the site converts poorly, run a CRO diagnostic first in nearly every case. What you learn becomes the brief for the eventual redesign instead of the redesign being an expensive guess about what was actually wrong.
Side by side
| Factor | CRO first | Redesign first |
|---|---|---|
| Time to first result | 2–6 weeks to a running test | 3–6 months to launch |
| Cost | Scoped from your brief, no rate card | Much higher, scoped to your brief |
| Effect on existing data/tracking | Preserved and built on | Reset to zero at launch |
| Short-term conversion impact | Targeted, measured lift per test | Frequently a temporary dip before recovery |
| Fixes structural/technical debt | Cannot, works within the existing build | Can rebuild the foundation entirely |
| Fixes an off-brand or outdated look | Cosmetic changes only, within reason | Full control over brand expression |
| Risk if the read on the problem is wrong | Low, a failed test costs weeks | High, a mis-scoped rebuild costs months and budget |
| Produces evidence for future decisions | Yes, every test result is reusable data | Only after launch, starting from zero again |
Choose cro first when
You have enough traffic to test
CRO needs volume to reach statistical significance in a reasonable window. If you're nowhere near that traffic level, testing individual elements will take too long to be useful. See our A/B test sample size calculator before committing to this path.
The site works, but doesn't convert
If people can complete the core task without confusion or technical friction, the problem is usually persuasion and flow, not the underlying build. That's exactly what CRO is built to diagnose and fix.
You don't yet know what's actually broken
A CRO diagnostic (session recordings, funnel analysis, on-site surveys) tells you where people are actually getting stuck, which turns a redesign from a guess into a brief with evidence behind it.
You need to preserve historical data and tracking
Redesigns routinely break UTM structures, event tracking, and years of accumulated conversion data. If that continuity matters to your reporting, CRO changes preserve it; a rebuild doesn't.
Choose redesign first when
The site is technically broken or unusably slow
No amount of button-color testing fixes a site that fails Core Web Vitals, breaks on mobile, or runs on a platform that can't support basic functionality. That's a foundation problem, not an optimization problem.
The brand itself is the actual issue
If the site looks and reads like a company from five years ago, or actively misrepresents what the business does now, cosmetic CRO tweaks won't close that gap. That needs a real brand and design decision.
You're on a platform that can't support what's next
Adding a configurator, multi-market support, or a very different information architecture sometimes just isn't possible on the current build. No test result changes that constraint.
You've already run CRO and hit a ceiling
If a mature testing program has stopped producing meaningful lift, that's real evidence the site's structure, not its details, is the constraint, which is exactly when a redesign is the right next move.
What each path actually costs you if you guess wrong
Guessing wrong on CRO costs weeks and a modest budget. A test that finds nothing still tells you something, and you move to the next hypothesis with the site otherwise untouched.
Guessing wrong on a redesign costs months of production time, a much larger budget and, because most redesigns dip conversion at launch before recovering, a real revenue cost while the new site re-earns the trust and habits the old one had built up.
That asymmetry is the actual argument for sequencing CRO before redesign in ambiguous cases: the downside of being wrong is far smaller, and being right produces the brief that makes the eventual redesign, if you still need one, much less of a guess.
Related questions
Technically, but it defeats the purpose of both. Testing on a site mid-redesign contaminates results, and a redesign built without CRO findings first is exactly the expensive guess we're trying to avoid. Sequence them: diagnostic and testing first, redesign scoped from what you learned.
Other comparisons
Services referenced
Get the audit before you decide anything.
Thirty minutes, free, no obligation. We'll tell you honestly whether you need an agency at all, including when the answer is that you don't.