Website redesign comparison between an old website with strong performance and a new website with declining traffic and conversions

Redesigning a website without losing performance: what to check immediately

SEO: URLs, redirects, traffic-driving content, internal linking and structured data.
Conversions: CTAs, forms, checkout, user journeys and key messages.
Measurement: GA4, events, tags, consent, server-side tracking and pre/post go-live dashboards.
Accessibility: WCAG, EAA, keyboard navigation, contrast, markup and components.
AEO/GEO: modular content, direct answers, FAQs, clear entities and structured data.

The myth of new website = better results

Redesigning a website is often seen as a natural move: more modern graphics, updated technology, a new CMS, a new user experience. In internal corporate narratives, redesign almost automatically becomes synonymous with relaunch.

The reality is more complex. A new website does not improve performance simply because it is new. On the contrary, if the project is not driven by data, clear objectives and a correct reading of the existing website, the risk is to achieve the opposite effect: traffic loss, conversion decline and increased acquisition costs.

The problem is not redesigning the website. The problem is redesigning it without knowing what is already working.

A redesign fails when it erases what the old website had learned to do: generate traffic, trust and conversions.

Matteo Doveri, Director at HT&T

When redesign breaks what was already working

One of the most common mistakes is treating the existing website as something to reset, rather than as a knowledge base. Established URLs, high-performing content, information structures already understood by search engines and users are often removed or changed without proper analysis.

Google also treats URL changes as a migration that must be carefully planned: redirects, page mapping and post-release checks are necessary precisely to reduce the impact on search results.
Source: Google Search Central

The result is a loss of signals accumulated over time: organic rankings, internal links, navigation habits of returning users. Even when redirects are technically correct, a structural change can still create friction that affects visibility and conversion.

From a business perspective, this translates into weeks or months of adjustment during which digital performance is lower than before. A cost that is rarely included in the budget.

Without a shared measurement baseline before the redesign, there is no real decline to analyse: there is only a lack of control. Traffic, conversions, rankings and engagement signals must be captured beforehand, otherwise the new website is evaluated by feeling rather than by data.

Why redesigning a website today is riskier than before?

Today, a website is not evaluated only by users and Google Search. It is also interpreted by generative systems, AI Overviews, AI Mode, conversational assistants, answer engines and tools that read content, entities, markup and semantic relationships.

This means that a redesign cannot be limited to putting the new website online, but must preserve and improve the existing information assets: indexed content, authority signals, page structure, structured data, FAQs, answer-first content and internal links.

From an AEO and GEO perspective, the risk is not only losing positions on Google but becoming less readable for AI systems that select, synthesize and cite sources in generated answers.

Design, UX and performance do not automatically coincide

A more visually polished website is not necessarily more effective. Redesigns often prioritize visual impact, creativity or brand alignment, while overlooking essential aspects such as message clarity, information hierarchy and simplicity of user journeys.

Less visible calls to action, vaguer texts, unnecessary animations or complex layouts can slow down comprehension and increase friction. The result is an experience perceived as “beautiful”, but less functional.

When this happens, the data is clear: the new website is appreciated internally, but converts less.

Accessibility: the issue you can no longer ignore when redesigning a website

There is one aspect that many redesigns still treat as secondary, when in reality it has become structural: accessibility.
Redesigning a website today without considering accessibility principles is not only a short-sighted choice in terms of user experience, but also a concrete regulatory and reputational risk.

With the entry into force of the European Accessibility Act (EAA), more and more websites and digital services must comply with clear and verifiable accessibility requirements.
This does not concern only public bodies: eCommerce, digital services, information platforms and companies operating in the European market increasingly fall within its scope.

The European Accessibility Act has applied since 28 June 2025 and marks a change of scenario for digital products and services in the European market.
Source: AccessibleEU

The critical point is this: accessibility is not added at the end. If a redesign is created without considering it, fixing it later means intervening on layouts, components, content, interactions and markup, with much higher costs and friction.

Accessibility does not only mean helping people with disabilities.
It means designing a website that is: understandable, navigable by keyboard, readable by screen readers, usable with correct contrasts, clear texts, logical hierarchies and predictable interactions.
In other words: a more robust website for everyone.

From a performance perspective, the effect is far from neutral.
An accessible website tends to have cleaner markup, less dependence on complex interactions, clearer flows and better-structured content.
All these elements improve not only usability, but also SEO, AEO, GEO and the overall reliability of the digital ecosystem.

The WebAIM Million 2026 report shows that users with disabilities may encounter errors on average on 1 homepage element out of 26, confirming that accessibility must be addressed as a structural issue and not as a final check.
Source: WebAIM Million 2026

A redesign that ignores accessibility today, in addition to not being compliant with the regulation, risks converting less.
In this sense, accessibility has also become a form of risk management, just like security, privacy and operational continuity.

For this reason, when deciding to redesign a website, accessibility must be treated as a project requirement, not as a final checklist. Ignoring it today means exposing yourself to future risks; integrating it from the start means building a more solid, more inclusive website aligned with regulatory and market developments.

Technology change as a risk multiplier

Many redesigns coincide with a change of CMS, framework or technology stack. It is a legitimate choice, but it significantly increases project complexity.

Performance, caching, content management, technical SEO, analytics tracking and integrations are often not replicated equivalently. Features taken for granted disappear or behave differently, generating inconsistencies that are difficult to identify immediately.

In these cases, the website worsens due to a sum of small deviations that, over time, affect reliability and results.

Another often underestimated factor is how the new website is released.
Big bang approaches increase risk because they concentrate all changes in a single moment.
Whenever possible, progressive rollouts, pilot sections or controlled releases make it possible to identify problems before they impact the entire digital ecosystem.

Checklist before redesigning a website

Before starting a redesign, it is useful to create an objective snapshot of the current state. This is not only useful to avoid mistakes: it helps identify which parts of the website generate value and must not be compromised.

SEO and content

Top pages by organic traffic
Main keywords and queries from Search Console
URLs with backlinks or strong history
Complete redirect map
FAQs, headings, schema markup and internal links

Conversions

Most used forms
Best-performing CTAs
Funnels and checkout
Advertising landing pages
Micro-conversions and lead magnets

Measurement

Active GA4 events
Marketing and advertising tags
Consent Mode and CMP
Server-side tracking
Pre/post go-live dashboard

Accessibility and quality

Contrasts and readability
Keyboard navigation
Semantic markup
Alt text and media
Accessible components and interactions

When redesigning the website is not the right answer?

There are situations in which redesign is a disproportionate response to the problem. If the website generates qualified traffic, converts and supports the business, but has specific limitations, taking an incremental approach is often more effective.

Optimizing content, improving key sections, working on performance, accessibility or conversion rate can produce better results than a total redesign, with less risk and less discontinuity.

Redesigning everything makes sense only when there is a real incompatibility between business objectives and the current structure, not as a shortcut to refresh the website.

Why redesigning a website is a management decision

A redesign is not a graphic design project but a strategic decision that impacts marketing, sales, IT and daily operations. Treating it as an exclusively creative or technical issue is one of the most costly mistakes.

A vision is needed that brings together historical data, future objectives, transition risks and the organization’s ability to manage change. Without this governance, the new website risks being a well-executed but poorly positioned project.

The new website should not be measured against the company’s internal taste, but against the real performance of the previous website.

Giuseppe Pane, Head of Analytics at HT&T

Different technologies, different impacts on performance (and control)

When a redesign worsens performance, the cause is often not visual. It is architecture: the chosen technology, how content and assets are managed, plugins and dependencies, deployment pipelines, caching and tracking. There are no universally better stacks: there are stacks that are consistent (or inconsistent) with objectives, governance and team maturity.

At HT&T we work daily on different ecosystems (WordPress, Shopify, Adobe Commerce/Magento, headless projects and lighter CMS solutions such as Statamic), and what we see most often is this: performance must be designed from the beginning. Technology determines how much control you have over that design and how much technical debt you carry over time.

WordPress: fast start, but governance is essential

WordPress is effective when you need to start quickly, when editing must remain simple and when the content structure is clear. But if it grows through layering (page builders + plugins + third-party scripts + heavy themes), performance becomes fragile: the impact is not only on Core Web Vitals, but also on stability, security and maintenance costs.

In practice, the real step forward comes when WordPress is managed as a platform: criteria for plugins and scripts, reusable components, proper caching, well-managed images and fonts, and a simple rule: fewer exceptions, more structure.

Statamic and content-first CMS: lightness, versioning, control

Solutions like Statamic (and, more generally, content-first or flat-file CMS) become interesting when you want predictable performance, controlled content structure, clear versioning and editorial workflows, less dependency on databases and cleaner HTML output.

The practical advantage is that pages tend to be clean by default: less overhead, more readable markup, fewer layers. The trade-off is that more project discipline is required: defining content models, components, editorial rules and a deployment process closer to development than to simple publishing.

Shopify: performance and reliability, but with constraints

Shopify is often the most sensible choice when the goal is to reduce operational risk and focus on merchandising, conversion rate and growth. At the infrastructure level, many variables disappear: hosting, critical updates, scalability and part of security are managed by the platform.

However, performance can still worsen if the theme becomes overloaded: too many apps, redundant tracking, scripts loaded everywhere, global sections multiplying assets. In these cases, redesign fails because the site becomes a stack of layers. The rule here is: fewer apps, cleaner integrations, and strict control over Liquid, assets and per-page scripts.

Adobe Commerce/Magento: power, complexity, discipline costs

Magento/Adobe Commerce makes sense when advanced logic is required: complex multi-store setups, large catalogs, advanced pricing, deep integrations with ERP/CRM/PIM and enterprise governance. But it is also a stack that does not forgive mistakes: if the architecture is not solid (cache, indexing, infrastructure, module quality), performance and operational costs deteriorate quickly.

In a Magento redesign, the key question is: which bottlenecks are we inheriting? If you do not measure and fix them, you are simply redesigning on top of an already struggling system.

Headless and composable: maximum control, maximum responsibility

Headless/composable architectures are perfect when you want full control over UX and performance and you have an organization ready to support it. But they are not shortcuts: they move complexity from the CMS to the project. Without governance, you risk building a system that is more expensive, more fragile and harder to maintain.

How to choose in practice

If your goal is to reduce risk and accelerate go-to-market, a managed platform with clear rules on themes and tracking often wins. If your goal is editorial quality, speed and control over markup, a lightweight CMS can be the best choice. If your goal is commercial complexity and deep integrations, you need a more powerful platform, but only if you are ready to govern it.

The point is not which technology to choose, but to avoid the most dangerous choice: the one made without a governance model. That is where redesigns worsen performance, because the site is born with embedded technical and operational debt.

Metrics to compare before and after the redesign

To understand whether the new website has actually improved performance, it is not enough to compare impressions or total visits. A pre-redesign baseline is required, along with a clustered analysis: SEO, UX, conversions, tracking and technical quality.

Before redesign

Top URLs by organic traffic
Queries with the highest impressions and clicks
Conversion rate by channel
Active GA4 events and tags
Core Web Vitals and accessibility

After go-live

404 errors, redirects and indexed pages
Changes in strategic queries
Leads, sales and micro-conversions
Missing or duplicated events
LCP, INP, CLS and layout stability

Google clarifies that the Core Web Vitals report in Search Console uses real user data collected through CrUX: for this reason, post go-live measurement must be observed over time, not only through lab tests.
Source: Google Search Console Help

infographic about website redesign: what to check before, during and after the process

What to monitor after go-live?

Go-live is the moment when the project begins to prove whether it works. The first weeks are crucial because they allow you to detect drops, anomalies and friction before they become structural problems.

First 48 hours: 404 errors, redirects, indexing, forms, checkout, analytics events, advertising tags.
First week: organic traffic, main queries, Core Web Vitals performance, conversion rate, lead quality.
First month: comparison with baseline, SEO trends, paid campaigns, user behavior and conversion paths.
First three months: content review, CRO optimization, accessibility, structured data, AEO/GEO and new editorial opportunities.

Without this monitoring phase, redesign is judged based on subjective impressions. With a pre/post dashboard, instead, it becomes a measurable decision.

Conclusion: new does not mean better

Redesigning a website can be a growth accelerator or a silent brake. The difference is not made by the chosen technology or design, but by how the decision is made and governed.

A website works when it supports the business, not when it simply looks updated. Before redesigning it, the key question is not how we want it, but what we cannot afford to lose.

FAQ: redesigning a website without worsening performance

When does redesigning a website actually worsen performance?

When the redesign resets existing signals (SEO, content, conversion flows),
does not start from a measurable baseline and introduces structural changes without governance.
The problem is not the new website, but how the transition is designed.

Is it better to redesign everything or intervene incrementally?

In most cases, an incremental approach reduces risks and discontinuity.
Optimizing key sections, performance, accessibility and conversions often produces better results
than a total redesign not driven by data.

How much does technology choice impact redesign success?

It matters as long as it is consistent with objectives, governance and team capabilities.
There is no “best” technology: there are choices that increase or reduce control,
technical debt and long-term risk.

Why has accessibility become a central requirement in redesigns?

Because today accessibility is not only a UX best practice, but a regulatory requirement
(European Accessibility Act) and a structural quality factor.
Ignoring it during redesign increases costs, risks and future corrective work.

How can you avoid “losing everything” at go-live?

By defining a pre-redesign baseline, planning controlled rollouts and monitoring
key indicators immediately after release.
Without these steps, go-live becomes a leap into the unknown.

Who should make the decision to redesign a website?

Redesigning a website is a management decision.
It impacts marketing, sales, IT and operations, and must therefore be governed at a strategic level,
not delegated as a purely design or technical project.

References and further reading

The topics covered in this article are based on official guidelines, regulatory documentation
and HT&T insights related to performance, accessibility, UX, SEO, AEO/GEO and digital project governance.