A slow or outdated website does not automatically need to be thrown out. Sometimes the honest answer is a repair. Sometimes it is a rebuild. And the worst outcome is paying for the wrong one — a full rebuild when three fixes would have done it, or another year of patches on a foundation that was never going to hold.
So before you spend a dollar, the useful question is not “should I get a new website?” It is “what is actually wrong, and what is the smallest thing that fixes it?”
Start with a baseline, not an opinion
Most “your site needs a redesign” conversations start with a feeling — it looks dated, it feels slow, a competitor’s looks nicer. Feelings are a fine reason to look closer. They are a bad reason to buy.
A free technical audit checks the public baseline instead: real load performance, mobile behavior, the technical SEO foundation, and whether search engines and AI assistants can actually read the page. That gives us a starting point grounded in what the site does, not how it feels on a Tuesday.
From there, the decision usually sorts itself into one of three buckets.
When a repair is enough
Some sites are built on a sound foundation and just carry a few fixable problems. If the site is already custom-coded, owned, and structurally healthy, repair territory looks like this:
- It is slow because of a few oversized images or one heavy script — not the whole build.
- Content is thin or outdated on a few pages, but the structure and URLs are sound.
- It is awkward on a phone, but the layout can be corrected without starting over.
- The Google Business Profile and local signals are neglected, and the site itself is fine.
If targeted fixes will genuinely move the needle, that is what I will tell you — and we scope the fixes, not a rebuild. Focused rescue work starts at $250, written down before you sign.
One honest exception: if your site lives on Wix, Squarespace, GoDaddy, or a drag-and-drop builder, “just make it faster” usually is not a repair. The platform is the weight. You can optimize images all day and still hand every visitor a bloated page carrying a page-builder runtime it never needed. That is rebuild territory — and no amount of tuning changes it.
When a rebuild is justified
When the foundation is the problem, repairs just paint over it. Rebuild territory looks like this:
- The site is on a page builder or template that fights every change, so small fixes keep breaking other things.
- There is no real technical SEO foundation, no analytics, and no clear path from visitor to phone call.
- Mobile is broken in a structural way, not a styling way.
- You do not own the code, and cannot move it without starting over anyway.
Here is what a rebuild means with me — and what it does not. It is not a new coat of paint on the same slow platform. I take what is worth keeping — your content, your structure, the pages and URLs you already rank for — and rewrite the site as a hand-coded static build, served straight from Cloudflare’s global edge network. No page-builder runtime, no plugin bloat, no database call on every page load. Just lightweight HTML delivered from a server close to the person visiting.
That is the whole difference between lipstick on a slow site and an actually fast one. A tuned-up Wix page is still a Wix page; a static site on the edge loads in a different weight class. Custom, hand-coded builds start at $499, you own the source code, and Flex Pay is available so it is not one lump sum.
The gray zone — and how it gets decided
Most sites are not a clean “repair” or “clean rebuild.” They are somewhere in the middle, and the split depends on how much of the existing site is worth keeping.
That is exactly what the written scope is for. After the audit, a rescue scope spells out which pages carry over, what redirects protect the URLs you already rank for, how content migrates, and what gets fixed versus rebuilt — with a fixed price before any work starts. Larger migrations are quoted in writing after the same audit. There is no second surprise number.
No part of this comes with a ranking or lead promise. I do not sell those, because no honest person can. What you get is a clear read on the site you have, a written scope for the work, and a price.
What this is not
A few things worth saying plainly, because the web-design industry has earned the skepticism:
- The audit is not a sales trap that always ends in “you need a full rebuild.” Repairs are a real outcome, and a common one.
- There is no incentivized-review offer, no fake urgency, no expiring discount clock.
- You work directly with me from the audit through launch — not an account manager reading a script.
The practical next step
If your site is slow, dated, or just not bringing in calls, start with the free technical audit. I will give you the baseline and a straight answer: repair, rebuild, or leave it alone for now.
If a rebuild does make sense, the posted pricing is right there — no “contact us for a quote” wall. And if a repair is all you need, that is what the scope will say.
Either way, you will know what is actually wrong before you decide what to spend.