7 signs your website needs rebuilding now
How to tell your site is costing you customers instead of bringing them.
A website is not a plaque you hang and forget. If any of these apply, you are losing work daily.
The signs
- It loads slowly on mobile — over three seconds means half your visitors left.
- It looks broken on a phone, or needs pinching and zooming.
- The content was last updated two years ago.
- It does not appear on Google when you search your own service.
- There is no clear way to contact you beyond a footer number.
- It shows stale information — prices or services that no longer exist.
- You feel awkward sending the link to a prospect.
That last sign is the most honest one. If you are not proud of it, it is not selling for you.
Refresh or rebuild?
If the structure is sound and the problem is look and content, a refresh is cheaper and faster. If it is slow at the foundation or built on old technology, rebuilding costs less than patching.
Measure growth as a business result
Traffic, followers and impressions are diagnostic numbers, not the final result. Choose the event closest to revenue—qualified lead, booked appointment, completed order or repeat purchase—and make it a key event in analytics. Record the current baseline before changing the site or campaign.
Review performance by channel, landing page and customer segment. Keep tests long enough to collect a useful sample and change one major variable at a time. Growth work also needs operational follow-through: fast replies, accurate stock and a clear offer can matter more than another increase in ad spend.
- Choose one revenue-linked key event and verify that it fires.
- Record cost, qualified conversions and resulting revenue by channel.
- Change one major variable per test and write the result down.
- Check response time, stock and sales follow-up before raising spend.
A topic-specific field checklist
- A redesign is justified by broken journeys, slow mobile pages, inaccessible content or an offer that no longer matches the business.
- Keep URLs and redirects planned before changing navigation so existing search value is not discarded.
- Benchmark Core Web Vitals and conversion events before release.
- Roll out high-risk templates first and watch errors, rankings and leads.
Details most proposals miss
Infrastructure quality appears when something changes or fails. Ownership, monitoring, recovery and controlled releases matter more than a long hosting feature table. The goal is not “never fail”; it is to reduce preventable failure and recover predictably.
- Business-owned domain, DNS, repository and production access.
- Separate development, preview and production release paths.
- Monitoring for uptime, application errors, performance and expiring services.
- Versioned backups with a tested restore objective.
- Patch and incident procedures with named responsibility.
The TechMate implementation layer
TechMate keeps the technical foundation understandable to the client. Releases have a visible history, important accounts are not trapped with one individual, and performance or security work is verified against a baseline.
- DNS and renewal inventory included in handover.
- Performance budgets for images, fonts and third-party scripts.
- Security checks aligned to actual data and privileged actions.
- Rollback route prepared before high-risk releases.
- Post-launch monitoring reviewed with business impact, not raw logs only.
Delivery phases that reduce risk
Improve infrastructure by reducing one known risk at a time and proving the control works. Configuration screenshots are not evidence of recovery, performance or security; tested outcomes are.
- Inventory assets, owners, dependencies and renewal dates.
- Capture a baseline for errors, speed and availability.
- Prioritise high-impact, likely failure modes.
- Release through preview with rollback prepared.
- Test monitoring and recovery after the change.
Questions that reveal implementation quality
- Who can recover each critical account?
- How old can restored data be?
- Which third party can block the service?
- What metric must improve after this change?
- What is the rollback trigger and procedure?
A realistic scenario
Example: if mobile visitors reach the contact page but rarely submit, inspect field friction and errors before replacing the visual identity. A redesign should protect working URLs and fix measured obstacles, not reset the site for fashion.
Sources directly related to this guide
Have a question this did not answer?
Send it over. We answer properly, whether or not you end up working with us.
