Your website feels slow. The design looks dated. Your competitors have launched sleek new sites and you're wondering if it's time to do the same. Before you commit to a full rebuild — which is expensive, time-consuming and disruptive — it's worth asking a more nuanced question: does this actually need rebuilding, or can we get what we need by improving what's already there?
At Inlucent we've seen businesses waste five-figure budgets on rebuilds they didn't need, and we've seen others stubbornly patch sites that should have been replaced years ago. The answer is rarely obvious, but there is a sensible way to think about it.
Start with the data
Before making any decisions, measure what you have. You can't know whether your site needs a rebuild or a tune-up if you don't know where the problems actually are.
If you haven't set up performance measurement yet, our guide on measuring website performance with Lighthouse will help you get a baseline.
Look at three things:
- Performance metrics — How does your site score on Core Web Vitals? Are load times driving users away?
- User behaviour — Where do visitors drop off? Which pages convert and which don't?
- Technical health — Are there broken links, crawl errors or security vulnerabilities?
If the data shows isolated problems — a slow-loading homepage, poor mobile layout on a few pages, a clunky checkout flow — those are optimisation targets. If the problems are systemic, that points toward a rebuild.
Signs you should optimise
Optimisation is the right call when the foundation is solid but specific areas underperform. Here are some common scenarios.
Performance is lagging but the architecture is sound
If your site is built on a modern framework, uses a sensible content management approach and has a clean codebase — but it's loading slowly because of unoptimised images, render-blocking scripts or too many third-party trackers — that's a performance problem, not an architecture problem. A few weeks of focused optimisation work can transform load times without touching the underlying structure.
The design is functional but needs a refresh
If the layout, navigation and user flows still work but the visual layer feels dated, a design refresh is far cheaper than a rebuild. Updating colours, typography, imagery and spacing can make a site feel brand new without rewriting a line of back-end code.
Conversion is low on specific pages
When most of your site performs well but one or two key pages — the pricing page, the contact form, a product landing page — aren't converting, targeted A/B testing and UX improvements are more effective than starting from scratch.
Signs you should rebuild
Sometimes optimisation is like renovating a house with structural problems. You can repaint the walls and replace the carpet, but the cracks keep coming back. Here's when a rebuild makes more sense.
The technology is end-of-life
If your site runs on a platform that's no longer maintained, doesn't receive security patches or can't support modern web standards, no amount of optimisation will fix the underlying risk. Older content management systems and bespoke frameworks built five or more years ago often fall into this category.
Mobile experience is fundamentally broken
If your site was designed desktop-first with mobile as an afterthought — or worse, wasn't built to be responsive at all — retrofitting a mobile experience onto a rigid layout is often harder than building mobile-first from the ground up.
We explore the importance of mobile-first design in our post: Is Mobile-First Important?
The site can't support your business goals
Perhaps you've outgrown a simple brochure site and need e-commerce, a client portal or a complex booking system. If the current architecture fundamentally can't accommodate what your business needs, it's time for a new foundation.
Maintenance has become a burden
When every small change requires a developer, content updates break the layout and the site feels fragile — the cost of maintaining the status quo is eating into the budget you could be spending on growth.
A practical framework
Here's how we think about it at Inlucent:
| Factor | Optimise | Rebuild |
|---|---|---|
| Core Web Vitals | Failing on a few metrics | Failing across the board |
| Technology | Current, maintained stack | End-of-life or unsupported |
| Mobile experience | Needs refinement | Fundamentally broken |
| Content management | Works, needs improvement | Blocks content updates |
| Business requirements | Current site can adapt | Requires new capabilities |
| Design | Needs a visual refresh | Needs a structural rethink |
| Budget | Limited, need quick wins | Available for longer investment |
If most of your answers land in the "Optimise" column, start there. If three or more are in the "Rebuild" column, it's probably time.
The middle ground: phased rebuilds
There's a third option that we often recommend. Instead of a big-bang rebuild where you replace everything at once, you rebuild in phases. Start with the most critical area — often the homepage and core user journey — and rebuild those while the rest of the site continues to operate. Then work through the remaining sections over weeks or months.
This approach reduces risk, lets you test assumptions with real users early and spreads the cost. It also means your business is never stuck with a half-finished site or a months-long "coming soon" page.
Making the call
Whether you optimise or rebuild, the key is to base the decision on evidence rather than gut feeling. Measure first, identify the real problems and choose the approach that addresses those problems without overengineering the solution.
If you're not sure which path is right for your business, we're happy to take a look and give you an honest assessment.