Every business site ages. The question is not whether yours will feel dated, slow, or hard to update; it is what to do when it does. The web industry has an obvious bias here: people who build websites tend to recommend new websites. So before any sales conversation, it helps to have an honest framework.
When fixing is the right call
A site is worth repairing when the bones are good. In practice that means:
- The structure makes sense. The pages map to what customers actually look for: services, prices or ranges, proof, contact. Nothing important is buried.
- The platform is standard. A site on a widely used, well-supported platform can be sped up, restyled, and corrected without archaeology.
- The problems are cosmetic or specific. Outdated photos, a dead booking link, a slow page, an awkward mobile menu. Specific problems have specific fixes.
- Google already trusts it. A site that ranks for searches that matter carries equity. Repair preserves it; a careless rebuild can squander it.
If that describes your site, a fix costs less and ships sooner, and any honest builder should say so. TenGlade has told owners to keep their sites, and will again. The first call costs you fifteen minutes either way.
When rebuilding wins
Repair stops making sense when the problems are structural:
- The site fails on phones. Most local customers arrive on a phone. A site that requires pinching and zooming is not a repair candidate; the layout itself is the problem.
- Speed is rotten at the foundation. Some sites are slow because of one heavy image. Others are slow because of the platform, the theme, and a decade of plugins. The second kind costs more to untangle than to replace.
- Nobody can update it. If changing your hours requires finding a person who left town years ago, the site has already failed at its job.
- The platform is abandoned. Old page builders and unsupported systems do not get better with time. Security and compatibility only decay.
- It misrepresents the business. A premium service with a bargain-bin site loses customers it never knows about. The site speaks before you do.
A useful rule: when repairs touch the layout, the platform, and the content all at once, you are already paying for a rebuild, just in installments and without the benefits.
The trap in the middle
The most expensive choice is usually the slow drip: a few hundred here for a patch, a few hundred there for a plugin conflict, every year, indefinitely, with the site never actually getting good. Owners fall into it because each individual payment feels smaller than a rebuild. Add up two or three years of patching and compare it to a fresh build with a known price; the arithmetic often surprises.
What a rebuild should cost in time
Rebuilds have a reputation for dragging on for months. They should not. Once the photos and answers are in hand, TenGlade builds in 4 to 5 days, with your approval at two checkpoints. The pace is possible because the studio builds lean, modern sites without committee overhead. Speed is not a corner cut; the same build is what passes Google’s own performance test.
How to decide this week
Three questions settle most cases. Does the site work properly on a phone? Can someone in your business update it today? Would you be comfortable if your best prospective customer judged you by it? Three yes answers point to targeted fixes. Two or more no answers point to a rebuild, and the decision is more about timing than direction.
Get the repair-or-replace answer for your specific site. Fifteen minutes, no pitch, and an honest recommendation, including when the answer is to keep what you have. Book a 15-minute call.