
When a website underperforms, the obvious response is often to redesign it. A new visual treatment does not automatically fix unclear positioning, unsuitable traffic, broken measurement or a difficult enquiry process. Conversion optimisation improves a viable journey; a redesign or rebuild replaces a structure that can no longer support the business.
What conversion optimisation changes
Conversion rate optimisation (CRO) is a structured process for improving how an existing website helps suitable visitors complete meaningful actions. It can involve journey research, analytics, copy, landing pages, forms, accessibility and controlled experiments.
CRO is usually the first option when the proposition remains accurate, the platform can support changes, relevant traffic exists and underperformance is concentrated in identifiable journeys.
What a redesign or rebuild changes
A redesign should address more than colour and layout. It may reconsider positioning, navigation, content architecture, templates, mobile behaviour, performance, accessibility, integrations, governance and measurement.
A redesign or rebuild is more likely when the business model or audience has changed substantially, users cannot find critical information, maintenance is unreliable, obsolete technology creates risk, or performance and accessibility failures are embedded across templates.
Decision matrix
| Evidence | Optimisation is more likely | Redesign or rebuild is more likely |
|---|---|---|
| Positioning | Proposition is clear but execution is uneven | Services, audiences or market position have materially changed |
| Journey | Specific pages or steps lose users | Navigation and content architecture fail across the site |
| Technology | Changes are safe and maintainable | Platform debt blocks essential work or creates repeated risk |
| Performance | Problems are isolated to assets or components | Template architecture causes site-wide problems |
| Measurement | Baseline and success events are trustworthy | Tracking and integrations cannot be repaired reliably |
| Governance | Team can maintain current templates | Publishing and ownership are structurally unworkable |
Do not confuse a visual problem with a commercial problem
A dated website can convert because it is clear and trusted. A beautiful website can fail because the offer is vague. Define the underperformance in measurable terms: which audience, service, journey, device and outcome are affected? Check whether lead quality, response time or traffic intent—not design—is the constraint.
Evidence to collect before choosing
- Page and journey performance by source, device and relevant audience.
- Verified form, call, ecommerce or booking completion events.
- Lead or sales quality linked back to landing pages where possible.
- User interviews, support questions, search data and onsite search terms.
- Accessibility, performance, security, integration and maintenance findings.
- A content inventory showing duplication, gaps, ownership and approval effort.
A hybrid approach is often strongest
Stabilise measurement and repair the highest-value journey first. Use what the team learns to shape a wider architecture or rebuild. This can prevent old assumptions being reproduced in a new design and can deliver earlier improvements while larger work is planned.
Protect SEO and measurement during a redesign
- Inventory indexable URLs, titles, canonicals, structured data and internal links.
- Map changed URLs to relevant permanent redirects; do not redirect everything to the homepage.
- Preserve valuable content and intent unless evidence supports consolidation.
- Test analytics, consent, forms and integrations before and after launch.
- Validate sitemaps, robots directives, status codes and mobile rendering.
- Record baseline search, lead and performance data before migration.
Evaluate investment using the same criteria
Compare expected effect on qualified outcomes, time to evidence, content and approval effort, implementation risk, maintainability, ability to test after launch and total cost of ownership. Include the cost of migration, content production, training and ongoing support—not only the initial design fee.
Performance is evidence, not a redesign vote
Core Web Vitals measure loading, interactivity and visual stability. Use field data at page or template level where available and pair it with diagnostics. A failing metric can justify technical work, but it does not by itself prove the entire site must be rebuilt.
Official reference
Google’s Web Vitals guidance explains the current Core Web Vitals and their recommended thresholds.
Choose after diagnosis. Read Why Your Website Gets Traffic but No Leads, then explore FGX’s web development and conversion-focused services.


