When Should You Redesign Your Website? 9 Signs It Is Time

A website redesign is one of those decisions most companies make at the wrong moment. Some owners scrap a perfectly healthy site because they feel bored with it. Others keep a site that has leaked leads for years because it still "works". I have worked in digital marketing since 2012, and I have watched both mistakes many times. So in this guide I give you nine concrete signs. For each one, I also explain how to measure it on your own site and whether it calls for a full rebuild or a smaller fix.

When does a website redesign actually make sense?

A website redesign means replacing the platform, the visual design and the content structure of an existing site together. It makes sense when your site is slow, weak on mobile, running outdated software and failing to convert. One isolated problem usually needs a fix; three or more signs at once call for a planned redesign.

The key distinction is simple. A redesign is a business decision, not a matter of taste. Therefore the feeling that a site "looks old" does not justify the budget on its own. On the other hand, when measurable losses pile up, every month of waiting costs you money. As you read the nine signs below, score your own site on a sheet of paper.

One more note before we start. Protecting search traffic during the project is a separate job, and I will not repeat it here. For that topic, read my guide on how to protect SEO during a website redesign. This article covers only the "when" question.

Which data should you collect before you decide?

Before you look at the signs, gather a few basic numbers. Otherwise the decision turns into a contest of opinions in a meeting room. Before every redesign conversation, I ask clients for this data:

• Organic clicks and impressions for the last 12 months from Search Console.
• Conversions split by mobile and desktop: forms, calls, carts.
• Page speed measurements, ideally field data from real users.
• Versions of your CMS, plugins and server software.
• Every change request from the past year and what each one cost.

For example, without Search Console data you cannot tell a seasonal dip from a technical drop. If you have not set it up yet, my Google Search Console guide walks you through it. In addition, the website value calculator gives you a rough sense of what your current site is worth.

Sign 1: Does your site fail the Core Web Vitals thresholds?

The first sign is speed. Google measures user experience with three metrics. According to the web.dev documentation, the "good" thresholds are an LCP of 2.5 seconds or less, an INP of 200 milliseconds or less and a CLS of 0.1 or less. INP replaced FID in March 2024. In other words, Google now measures a metric that nobody optimized on older sites.

However, slowness alone rarely justifies a rebuild. Often you only need to compress images, add caching or remove a heavy plugin. So find the root cause first. My guide to the Google Lighthouse performance test shows the steps.

The redesign signal appears when the root cause is the theme or page builder itself. You cannot patch a structure that loads hundreds of kilobytes of unused JavaScript on every page. If you want the details on rankings and revenue, read how site speed affects SEO.

Also, look at field data rather than a lab score. A Lighthouse score reflects your test machine. Field data comes from the phones of real visitors. Google’s page experience documentation also stresses that good experience is more than a single score. Therefore do not tie this sign to one number; focus on the moments where users actually wait.

Sign 2: Do mobile visitors struggle on your site?

Google now indexes sites based on their mobile version. The Google Search Central page on mobile-first indexing states this clearly. As a result, missing content, hidden menus or cropped tables on mobile hurt your search visibility directly.

The typical symptoms look like this: buttons too small for a thumb, horizontal scrolling, pop-ups that cover the screen and form fields that vanish behind the keyboard. Moreover, if your mobile conversion rate sits far below desktop in analytics, that gap is a strong sign in itself.

So when does mobile trouble mean a redesign? If the site uses a fixed width or a separate mobile version instead of a responsive layout, the fix usually costs about as much as a rebuild. To check your own site, follow my mobile-friendly test guide.

Sign 3: Has your platform lost security support?

This sign gets the least attention, yet it carries the most danger. Once server software reaches end of life, nobody patches new holes anymore. For instance, the PHP supported versions page lists the active and security support dates for every PHP release. If your version no longer appears there, your site runs at risk.

The same applies to your CMS and plugins. An outdated theme, an abandoned form plugin or custom software from a developer who disappeared all open a door for attackers. In most hacked sites I have cleaned up, this was the cause.

Still, an old version does not always mean a redesign. If your code can move to a newer version, an update project will do. That said, if the code is so old that it breaks entirely on current PHP, the gap between migrating and rewriting closes. At that point a redesign becomes the rational choice.

You can run this check yourself. Look up the PHP version in your hosting panel and the core and plugin versions in your CMS. Then note the last update date for each. A plugin with no update for two years is usually an abandoned plugin.

Sign 4: Why does traffic arrive but conversions never follow?

If visitors come but forms, calls or sales do not, the problem lies in the site, not the traffic. Take this sign seriously, because it is the most common reason ad budgets go to waste. You pay for every click, yet the site cannot turn that click into a customer.

First, define the goal. If you do not know which action counts as a conversion, a low rate can mislead you. My article on how to set website conversion goals helps here. After that, review your most visited pages one by one.

The causes I see most often are these: the quote button appears only after scrolling, the contact form asks for twelve fields, and the page says nothing about price or process. I covered most of them in UX mistakes that kill sales. If fixing them means changing almost every page template, you are no longer looking at a tweak. You are looking at a redesign project.

Sign 5: Does your site still represent your brand today?

Companies grow, services change and brand identities evolve. The website, however, often stays frozen five years in the past. Consequently, a prospect meets one brand in a sales meeting and a different one online.

This sign usually looks like this: a new logo sits on an old colour palette, photos show people who left the team, and nobody has touched the client list for years. Sometimes the site even promotes services you no longer offer.

On the other hand, a new logo alone does not require tearing down the whole site. I explain when identity work makes sense in when you need a logo redesign. But if your positioning changed, for example from small businesses to enterprise buyers, the language, structure and proof on your site must change too. That is a strong case for a website redesign.

Sign 6: Can you update content without a developer?

If a simple text change means emailing a developer and waiting three days, your site does not serve you. I see this most often with old custom software and with systems left behind by agencies that closed.

A site you cannot update goes stale. Campaign news goes live late, prices stay wrong and the blog stops. Fresh content also matters for search visibility, which I discuss in content freshness and SEO.

Ask yourself these questions:

1. Can you add a new service page without a developer?
2. Can you edit title and description tags page by page?
3. Can several people log in with different permissions?
4. Do you own the source code and the database?

If you answer "no" to two or more, think seriously about a new CMS. The last question matters most. If you do not own the code, you do not truly own the site.

Sign 7: Has your business changed while the site structure stayed the same?

This sign concerns information architecture rather than design. A company that offered three services at launch may offer twelve today. The old menu cannot carry that growth. As a result, services end up crammed into one long page or buried under a menu.

The same problem shows up in search. Each service should answer its own search query. Services squeezed onto one page rarely rank well for any of them. So if you are entering new markets, cities or languages, rethink the structure from the ground up.

For example, a manufacturer that starts exporting needs more than a translation. It needs dealer applications, technical document downloads and contact flows per country. In a case like that, rebuilding the structure usually costs less than patching the old one.

Sign 8: Why is adding tracking and integrations so hard?

Nobody expects a modern site to work alone. It has to talk to your CRM, email marketing tool, payment provider, ad conversion tags and analytics. On older sites, those connections are often close to impossible.

Here is the picture I see in the field. Form data lands only in an inbox and never reaches the CRM. Ad conversions go uncounted because there is no thank-you page. Consent banners and tags do not talk to each other. In short, the marketing team works in the dark.

Tools like Google Tag Manager solve part of this. Still, when forms, templates and event triggers live deep in old code, every integration becomes its own development project. If you hit the same wall on the third integration request, you have a clear redesign signal.

For instance, if your developer must add code to every form page by hand to install one ad tag, even a simple campaign takes weeks. On a modern setup, the same job takes minutes inside a tag manager.

Sign 9: Are maintenance costs approaching the cost of a new site?

The last sign is purely financial. Add up every hour you paid in the past year for fixes, updates and emergency work. If that total rises every year, the old system charges you invisible rent.

Here is a simple example calculation. Imagine an average of six hours of fixes per month at your agreed hourly rate. Compare the yearly total with one third of the cost of a new site. This is only an illustrative method, and your numbers depend on your own contracts. Still, if maintenance gets close to that ratio, a new site pays for itself within about three years.

Moreover, this sum ignores opportunity cost. Slow campaign launches, lost form submissions and security exposure all belong in the equation. So look beyond the invoice and ask how much the site slows your team down.

How many signs should trigger a website redesign?

Once you have scored all nine signs, apply this simple rule. It is a starting framework based on field experience, not a guarantee:

Weight matters here as well. The security sign demands action even on its own. In contrast, the brand sign can usually wait if nothing else is wrong. In other words, count the signs but also weigh them.

What is the difference between a partial and a full redesign?

In a partial redesign you keep the existing platform and change only the visible layer. For example, you swap the WordPress theme and rebuild the page templates. Content, URL structure and database stay in place.

In a full redesign the platform, information architecture and design all change together. This path costs more and takes longer. It also carries more risk, because URLs usually change. Therefore, if you choose a full rebuild, plan the move with a website migration SEO checklist.

My practical rule is this. If the problems sit in the visible layer, a partial redesign will do. If they sit in the foundation, meaning security, CMS flexibility or integrations, a full redesign becomes unavoidable.

Should you redesign a site only because it looks dated?

Short answer: usually not. Design trends shift every two or three years, and rebuilding with each wave is not sustainable. Moreover, changing a site that ranks and converts well just for looks puts what you already earned at risk.

That said, "looking dated" sometimes hides a real problem. If visitors find the site untrustworthy and leave, the issue becomes a conversion sign. To find out, run a quick user test or at least review heatmap data.

In short, do not let looks decide alone. If the dated design comes with other signs, take it seriously. If it comes alone, move forward with small design touches.

Can accessibility be a reason to redesign?

Yes, and increasingly so. Letting people with disabilities use your site is both an ethical and a commercial matter. The international reference is the W3C WCAG guidelines. Contrast, keyboard navigation, alternative text for images and form labels are core topics there.

Older sites rarely considered accessibility at all. For example, menus only work with a mouse, forms have no labels and colour contrast is low. You can fix some of this in place. However, if the template structure is flawed from the start, adding accessibility later becomes hard.

If you sell into Europe, this topic matters even more. So when you decide on a redesign, do not push accessibility to a later phase. List it as a core requirement of the new build.

What does postponing a website redesign really cost?

Postponing looks free, but it is not. Every month, lost forms, wasted ad clicks and growing maintenance hours add up. Because this cost never shows on an invoice, most managers miss it.

There is a technical price too. An unmaintained system ages a little more each year, and migration gets harder. A problem you could solve with an update today may require a full rebuild two years from now.

On the other hand, a rushed redesign is expensive as well. Projects that start unprepared blow the budget and lose traffic. So the right approach is to measure the signs at regular intervals and base the decision on data. I recommend that clients check these nine signs once a year.

Which time of year works best for a relaunch?

Timing matters as much as the decision itself. Do not launch the new site in the middle of your busiest sales season. Small bugs always surface in the first weeks after launch. Fixing them during peak demand means stress and lost revenue.

My suggestion is simple. Identify the two or three quietest months in your industry and put the launch date at the start of that window. For example, enrolment season in education, November and December in retail, and summer in tourism are all risky. That way you keep breathing room for post-launch fixes.

Also, estimate the timeline honestly. Design, content, development and testing almost always take longer than planned. Content slips most, because the people writing it usually work inside your own company. Therefore start content production in parallel with design instead of leaving it for the end.

What should you ask the team that will build the new site?

You have seen the signs and made the call. Next comes choosing the team. At this stage, price should not be the only criterion. The answers to these questions tell you a lot about how the project will end:

• Will you analyse current traffic and conversions at the start?
• Who keeps the source code, design files and admin access?
• Do you put speed and Core Web Vitals targets into the contract?
• How many days of free post-launch fixes do you include?
• Who prepares the redirect plan for old URLs?

If you cannot get clear answers, be careful. Ownership of the source code matters most, because it keeps the problem from sign six from returning on the new site. In other words, do not buy tomorrow’s problem while solving today’s.

How should you measure the success of the new site?

A redesign project does not end on launch day. Instead, the real test starts in the three months after launch. So write down how you will measure success before the project begins.

With clients, I usually track organic clicks and impressions, mobile and desktop conversion rates, Core Web Vitals in field data and cost per lead. I also measure content update time. When a change that took three days now takes ten minutes, that is a concrete gain.

Meanwhile, small traffic swings in the first weeks are normal. Google needs time to crawl and understand the new structure. So do not panic in week one. However, if a clear drop remains in week four, check redirects and indexing status right away.

Which mistakes do companies make most when deciding on a redesign?

Over the years I have seen the same mistakes at very different companies. Knowing them protects you from an expensive error:

1. Deciding on one person’s taste instead of looking at data.
2. Deleting pages that perform well because they "do not fit" the new design.
3. Leaving content preparation for the final week.
4. Setting up tracking and conversion tags only after launch.
5. Approving the new site on a desktop screen only.

The second mistake hurts the most. If a page on your old site has brought traffic for years, keep it in the new structure. Ideally, keep it at the same address too. Otherwise the project gives you a new look and takes away years of work.

Finally, watch the fifth point. Management meetings approve sites on big screens, yet most customers arrive on phones. Add at least two different phones to the approval step: one fast and current, one mid-range device a few years old.

Do the signs read differently for an online store?

All nine signs apply to e-commerce too, but their weight changes. On a corporate site, a drop in form submissions may take weeks to notice. In contrast, a single bug in a store checkout hits revenue the same day.

So in e-commerce, watch three signs more closely: speed, mobile experience and integrations. Slow category pages, a coupon field that disappears in the mobile cart or sync issues with stock and shipping systems all mean lost money.

Also, switching e-commerce platforms is more complex than rebuilding a corporate site. Product data, customer accounts, order history and product URLs all need to move. In short, make the redesign decision earlier in e-commerce, but plan the execution more carefully.

Could a new landing page be enough instead of a redesign?

Sometimes, yes. If your problem is the conversion rate of one campaign or one service, a dedicated landing page often delivers faster than a full rebuild. This works especially well for pages that receive Google Ads traffic.

On the other hand, a landing page is a bandage, not a cure. It does not fix security, CMS or structural problems on the main site. Moreover, a landing page that looks very different from the main site can hurt brand consistency.

My advice is this. If you have decided on a redesign but the project will take a few months, build a temporary landing page for your most important service. That way your ad budget does not go to waste while the new site takes shape. After launch, move the page into the new structure and reuse its conversion data.

How can you score your own site today?

Finally, here is a 30 minute self-assessment. Open a spreadsheet and create nine rows. For each sign, write "yes", "partly" or "no". Next to each row, note the evidence: a screenshot, a metric or an invoice.

• Speed: LCP, INP and CLS in field data.
• Mobile: mobile conversion rate compared with desktop.
• Security: support status of PHP, CMS and plugins.
• Conversion: form and call volume over the last 90 days.
• Brand, content, structure, integrations and maintenance: concrete examples from the past year.

Treat any row without evidence as a "no". That keeps emotion out of the decision. If you score five or more, it is time to budget for a full website redesign. If you land between three and four, plan a partial improvement. And if you want someone to run the whole process with you, from inventory to launch, my web design service covers every step.