Landing Page Redesign vs UX Fixes: How to Tell Which One Your Page Needs
Your landing page is not converting, and someone on the team has said the sentence that starts many expensive projects: "We should just redesign it."
Sometimes that is right. More often, the page has two or three specific problems, and a redesign would rebuild everything around them and leave the cause in place. This guide compares the two paths, shows how to diagnose which one you need, and gives a rule for choosing. Start by running our Free UX Scan on the page, so the diagnosis comes before the rebuild.
What each path is
UX fixes are targeted changes to a page you keep: rewriting the hero, giving the page one clear primary action, adding real proof, removing template leftovers, tightening the order of sections. The layout, brand, and structure stay.
A redesign replaces the page's structure and look. The message, layout, visuals, and often the build are all on the table.
Side by side
| Dimension | UX fixes | Redesign |
|---|---|---|
| Scope | A short list of specific problems | The whole page, often the whole template |
| What ships | A contained set of edits on the current page | A new structure, look, and often a new build |
| Effort | Mostly copy and layout work | Design, build, and review cycles |
| Risk | Low, and easy to roll back | Higher, because new problems can arrive with the new page |
| Learning | Each fix shows its own effect | Many changes land at once, so cause and effect blur |
| Best when | The page has clear, local problems | The page's structure or offer is wrong |
| Needs consensus | Little | A lot, across brand, product, and engineering |
What the research says
Nielsen Norman Group has argued for years that incremental change is the safer default. Their guidance is direct: never make radical changes when minimal adjustments will suffice. They observe that many problems you need to solve are isolated and can be fixed with smaller, incremental approaches, and that radical changes have a higher chance of inadvertently breaking something critical for users.
They also describe how redesigns go wrong: organizations often launch a redesign project with an ambitious timeline, only to see it stretched by endless debate. The projects that succeed have clear, measurable objectives set before the work begins.
Their list of legitimate reasons for a redesign includes:
- The gains from incremental changes have run out after many iterations.
- The technology is severely outdated and blocks critical changes.
- The site is architecturally a tangled mess after years of patchwork.
- Conversion is severely low site-wide, with issues too tangled for incremental fixes.
A separate NN/G article makes a related point about familiarity: users hate change, so it is usually best to stay with a familiar design and evolve it gradually. It names two cases where a fresh design is worth the disruption: when you have almost no current users and expect a major improvement to expand your audience, and when years of patches have left the experience overly convoluted, with no unified conceptual structure.
On the improvement side, NN/G's review of iterative design projects found that the median improvement from version 1 to version 2 was 45%, and from version 2 to version 3 was 34%. Those figures come from a limited set of documented case studies from an earlier era, and the article itself warns that the sample is small. The pattern still matters: the first few rounds of targeted fixes tend to deliver the largest gains.
Diagnose first: where is the problem?
The decision turns on where the problem sits. Use this table with your page open.
| What you see | Likely problem | Path |
|---|---|---|
| Visitors cannot say what the product is after a few seconds | Hero copy | Fix |
| Several competing buttons in the first screen | Hierarchy | Fix |
| "Trusted by" with no logos, testimonials with no names | Proof | Fix |
| Placeholder text, repeated cards, template leftovers | Polish | Fix |
| Wall of text, no visual order | Layout of sections | Fix, and sometimes a section redesign |
| The page speaks to the wrong customer | Positioning | Rework the message first, then decide |
| The offer itself is unclear | Offer | Settle the offer first, then the layout |
| The template or CMS blocks basic changes | Technology | Redesign or rebuild |
| Years of patches left contradictory sections | Architecture | Redesign |
| The page works and the traffic is wrong | Acquisition | Look at the ads or the channel |
How a scan helps you diagnose
Nielsen Norman Group's research says users often leave pages in 10 to 20 seconds, and that you must clearly communicate your value proposition within 10 seconds. A scan reads your page the way a stranger does in those seconds, so its findings tend to cluster in the top of the page. That is where fixes pay off first.
Our scan has two paths. The form sends a written report by email, with up to 3 priority fixes. The connector returns a one-line verdict, a score for each rubric area, and the strongest finding for one public page, limited to 6 scans an hour per network. Our post on how to read your results explains what to do with them.
If the scan's findings are mostly hero, button, proof, and polish issues, you have a fix list. If they point at positioning or the offer, the next step is a decision about who the page is for and what it promises. If you already tried fixes and the page still struggles, a redesign deserves a serious look.
Pick this if
Pick UX fixes if:
- You can name two or three specific problems on the page.
- The findings sit in the hero, the main button, the proof, or the polish.
- You want to ship the changes on the page you already have.
- You want to learn which changes mattered.
- The page has some traffic you do not want to disrupt.
Pick a redesign if:
- Your template or CMS blocks the changes you need.
- The page has patched layers that contradict each other.
- Your brand or offer changed enough that the page no longer fits.
- You tried targeted fixes over several rounds and gains have flattened.
- You have clear, measurable goals and agreement on them before work begins.
Do both in order if you are unsure: fix the first screen now, measure after those fixes are live, then decide whether the remaining problems justify a redesign. The fixes give you a baseline and a record of what worked, and either one makes a redesign briefing sharper. Our comparison of a UX audit and a redesign goes deeper on that decision for whole products, and our post on AI redesigns and senior UX audits covers the shortcut of generating a prettier screen.
If you do redesign
A few rules keep the project from drifting:
- Write the objective first. For example, "more demo requests from the pricing page." Without it, the debate never ends.
- Carry forward what works. Keep the headline or proof that visitors respond to.
- Measure before and after. Use the same metric and a similar period.
- Run a scan on the new page before launch. Redesigns often bring back the issues you just fixed.
What a paid review adds
A scan returns up to 3 priority fixes for one page. When you want the whole picture, our Website UX Audit reviews your pages one by one for clarity, navigation, and conversion, with annotated findings and a prioritized fix list. If you decide to redesign, a Discovery Sprint helps you define customers, problems, and the smallest useful scope before you commit to a build. Our Design Subscription and Fractional Designer plans cover the ongoing design work. Current offers are on our pricing page, and we confirm scope before you commit.
The short version
Fix the page when the problems are specific and local. Redesign when the structure, offer, or technology is the problem. Diagnose first, so the path matches the problem.
Run the Free UX Scan before you decide. The form sends a written report by email, and the connector returns a read of one public page.
If you want a senior team to help you decide between fixing and redesigning, book a discovery call, or email us at ash@uxsignalstudio.com.