Outdated website: repair it or rebuild from scratch?
When did you last look at your company website honestly, as a potential customer rather than its owner? If the answer is "a while ago", there is a good chance you are leaving money on the table. An outdated site is not an aesthetic problem. It is a business risk that quietly costs you customers, revenue and credibility every day.
This article covers how to recognize that your site has aged out, how to decide between a facelift and a full rebuild, and how to make the change without losing the search rankings you spent years earning.
What makes a website outdated
What counted as modern five years ago is now a liability. Three signs matter more than the rest:
Speed. Google's own research puts mobile abandonment at 53 percent once a page takes longer than three seconds to load. There is no patience left to win back.
Confusing experience. If visitors have to hunt for information, or filling in a form feels like an ordeal, they simply go to a competitor.
Aging technology. An old codebase is slow and full of known vulnerabilities, and search engines actively demote sites that fail modern technical expectations such as Core Web Vitals.
The security risk is not theoretical either. Analyses of hacked sites consistently find outdated software or plugins behind the majority of breaches. A compromised site costs you data and reputation, and it can get you flagged in search results, which ends your visibility altogether.
Technical debt, the invisible profit killer
Technical debt is what you pay later for the quick fix you took earlier. Every "let's just solve it this way for now" adds a brick to the wall that eventually blocks your growth. Adding a feature to an eight-year-old patched system can cost five times what the same feature costs on a modern foundation. That is the real bill, and it arrives long after the original decision.
Mobile is the baseline, not a variant
Search engines index the mobile version of your site first. If that version is slow, incomplete or awkward, your desktop version will not save you. Responsiveness alone is no longer enough: good UX/UI design does not shrink the desktop layout, it designs for how people actually behave on a phone.
Repair or rebuild: how to decide
A visual refresh is enough when the engine underneath is modern, fast and secure and only the styling has aged. That is the rarer case. Far more often, the slowness, the painful admin and the weak conversion rates all trace back to the platform itself, and new paint on an old engine changes nothing.
Make the call on evidence, not instinct. Run an audit first: page speed on mobile, crawl and indexing issues, conversion paths, and how much a small change actually costs you today in developer time.
When only an engine swap works
These signs point at a rebuild rather than a repair:
Mobile PageSpeed scores below 50.
A layout that breaks or becomes unusable on phones.
Recurring security incidents or a plugin stack nobody dares to update.
New functionality, such as booking or a modern payment flow, being impossible or absurdly expensive to add.
An admin interface your own team avoids using.
Running the numbers
Ask what the current site costs you, and do not think about hosting fees. Think about the revenue that never arrives. Research into ecommerce performance has repeatedly found that a single second of extra load time can cut conversions by around 7 percent. On a shop turning over EUR 12,000 a month, that is roughly EUR 850 lost every month, or over EUR 10,000 a year, to a problem you can fix once.
Against that stands the one-off cost of a build on a modern stack. No endless patching, no plugin licences, no standing security worry. Framed that way, a rebuild is usually the highest-return investment available to a small company's marketing budget. Proving that return afterwards is its own discipline, and our guide on marketing reports for executives covers how to present it.
Why we do not build on WordPress
Ten years ago WordPress was the sensible default. For a business that depends on speed and security it now brings more problems than it solves: a plugin-heavy monolith, a large attack surface, and performance you fight against rather than build on.
We build on Next.js with a headless CMS instead. Server-side rendering and static generation make pages load close to instantly, which improves both conversion and technical SEO. Separating content from presentation means your marketing team edits text and images in a friendly interface while the code stays untouched, and the same content can later feed a mobile app or another channel. That is what our web development service delivers, and for anything with real business logic behind it, our custom software work picks up from there.
What a strategic rebuild looks like
A rebuild does not start with a design tool. It starts with the business question: what should this site do, for whom, and how will we know it worked. We map the current traffic and the pages that actually earn, then design around those instead of redecorating everything equally.
The migration is where projects are won or lost. Existing content, rankings and backlinks are assets, and they carry over through a precise 301 redirect map and a careful content migration. Done properly, you launch with your search equity intact and a technical foundation that outperforms the old one from day one.
The visual side deserves the same rigor. A rebuild is the natural moment to bring your brand identity in line with where the business is now, so the site does not look like a company you stopped being three years ago.
If you are weighing this decision and want an honest answer about which side of it you are on, get in touch and we will look at your current site with you.
Frequently asked questions
How often should a website be rebuilt?
Every two to three years is a reasonable rhythm, sooner if the site is slow, awkward on mobile or converting badly. A bounce rate above 60 percent or a mobile load time over three seconds is a clear warning sign.
What does a full rebuild cost?
For a custom build on a modern stack, expect to start from roughly EUR 6,000. That covers strategy, the full UX and UI design, the build itself and a headless CMS. It is not a template price because it is not a template.
How long does a rebuild take?
Typically eight to twelve weeks. The first two to three go into strategy and design, five to eight into development, and the last week into testing and launch. Rushing that timeline is how you end up with the site you are replacing.
Will I lose my Google rankings if I change platform?
Not with a careful migration. Your SEO equity moves across with a detailed 301 redirect map, and a faster technical foundation usually improves rankings rather than hurting them. The risk comes from skipping the redirect work, not from the move itself.
Why not WordPress?
Because a plugin-heavy monolith is slower, more fragile and harder to extend than a modern framework. We do not work with WordPress. We build on technologies that give you a speed and security advantage rather than a maintenance habit.
Will I be able to edit content myself?
Yes. Content lives in a headless CMS with a straightforward editor: rewrite text, swap images, publish a post, no developer involved. The same content can later feed a mobile app or any other channel without being rebuilt.