Rebuild your website or fix it? The signs that tell you which

A website needs rebuilding when the problems are in its foundations. That happens when the technology no longer gets updates, the structure can’t cope with phones, you can’t manage the content yourself or the site no longer does the job you need. If the foundations are sound and the issue is the look or a few pages, it’s worth fixing instead. These are the signs I look at to work out which of the two you’re dealing with.

It’s slow, and Google measures it

For visitors, slowness shows up in three ways, with a page that stays blank, a button that doesn’t respond when tapped, or content that jumps just as they’re about to tap it. Google measures exactly these three things with Core Web Vitals, the indicators it uses to judge a page’s experience.

• LCP measures how long the main content takes to appear, and 2.5 seconds or less counts as good.
• INP measures how quickly the page reacts to taps and clicks, and 200 milliseconds or less counts as good.
• CLS measures how still the page stays while it loads.

INP is the newest of the three. On 12 March 2024 it replaced FID, a metric that only looked at the first interaction. Google says its ranking systems use Core Web Vitals. It also says they won’t get you to the top on their own, because first and foremost the page has to answer what the person is looking for.

The real question is where the slowness comes from. If a few images or a couple of scripts are weighing the site down, targeted fixes will do. If it sits on a heavy theme and dozens of plugins that depend on each other, every improvement breaks something else, and starting again makes more sense.

On a phone, it breaks or is awkward to use

Google indexes and ranks sites based on their mobile version. If yours was built for desktop and adapted later, it shows straight away. Menus won’t open, tables run off the screen, text has to be pinched to read and forms are impossible to fill in. When the structure wasn’t designed for small screens, fixing it page by page often costs more than rebuilding it properly.

You depend on someone for every change

You want to change your opening hours, add a photo or publish a new piece of work, and you have to email someone and wait. Or the admin panel is so clunky that you’re afraid of breaking something, or whoever built the site has moved on and nobody has the logins. Either way the site ages, shows outdated prices and news, and makes the business look like it’s standing still.

A site built today lets you manage your own text, photos, services and projects, with fields designed for your content rather than for any website at all. Structural changes are still a job for a developer, but everyday ones aren’t.

It runs on technology nobody updates any more

This is the least visible sign and the riskiest. The content management system, or CMS, is stuck on an old version. Some plugins have been abandoned by their authors, the theme no longer gets updates, and the server runs a version of PHP that has reached end of life.

PHP is the language WordPress and many other CMSs run on. Its own developers warn that anyone on an unsupported version may be exposed to security holes that will never be patched, and WordPress says the same in its requirements.

Often you can’t update one piece without breaking the others, so nobody updates anything. In the worst case the site gets hacked and used for something else, along with the data people left in your forms. When the update chain is stuck, rebuilding is the safer choice.

It isn’t accessible, and AI answers can’t read it

An accessible site can be used with a visual impairment, with a keyboard only or with a screen reader, and in practice it’s easier for everyone, older customers included. Low-contrast text, images without descriptions, forms without labels and tiny buttons shut people out. Since 28 June 2025 the European Accessibility Act has applied across the EU, covering a range of products and services, e-commerce among them.

Who has to comply and what changes is covered in the article on accessibility obligations for websites. What matters here is that on an old structure accessibility rarely gets added afterwards, because it touches almost every page.

The same goes for answers written by artificial intelligence. Google explains that to appear in its AI features a page has to be indexed and eligible to show in search results with a snippet, and that important content should be available as text. A site with its services written inside images, price lists in PDFs and pages Google struggles to read stays out of these answers, just as it does from the regular results.

It makes you look smaller than you are and no longer does the job

Your website is often the first thing a customer sees of you. If the business has grown since, changed its services or now works with bigger clients, a site from years ago describes a smaller, older company than the real one. People who only know you from there get the wrong idea, and your prices look out of proportion to them.

Then there is the work the site should do and doesn’t. Maybe you need online bookings and still take them by phone, or you’d like to sell online and the site can’t. If orders and requests arrive by email and someone copies them into the management software by hand, the site isn’t talking to the rest of the business. The cost doesn’t show up on any invoice, because it’s in the hours spent every week working around it.

When a redesign or targeted fixes are enough

Not every site that needs improving needs rebuilding. If the technology is up to date, the site works well on phones and you manage the content yourself, targeted work is often enough, and it usually takes one of three forms.

• If the problem is how you come across, a redesign of the visuals and copy is enough.
• If the slowness comes from images or scripts rather than the structure, you need performance work.
• If the foundations can carry it, you can add a new feature, such as bookings or a form that passes data to your management software.

A good redesign changes the way people work as well as the look. On the home page of my site there is a before-and-after comparison of a management dashboard, with the same data rethought to be easier to read and use on any device.

Before deciding, find out whether the problem is in the foundations or the facade.

When someone asks me whether their site needs rebuilding, I look at the foundations first. I check the technology and its updates, the speed measurements, how the site behaves on phones, who can change what and how it connects to the rest of the business. From there I’ll tell you whether to fix it or start again, and why.

An existing project can often be improved without starting from scratch, and if that’s the case I’ll say so. If you’re unsure, send me your site’s address.