Rebuild or Redesign? Read Your Site Like a Foreman

The Quick Test: Is This a Paint Problem or a Foundation Problem?

Every contractor who calls us thinks they need "a redesign." Half of them are right. The other half have a site that looks fine on the surface and is rotting underneath: a WordPress core that has not been updated in two years, forty-some plugins fighting each other, hosting that chokes when three people load the site at once. You cannot see that from the homepage. You feel it in the load time and the missed leads.

Here is the test we walk owners through on a strategy call. Answer these five questions honestly:

• Does the site take more than 2 seconds to load on a phone with average signal?
• Do you need to hire a developer every time you want to change a phone number or add a service page, instead of doing it yourself in ten minutes?
• Is your form data, your booking requests, or your call tracking sitting disconnected from whatever CRM, ServiceTitan, Jobber, or Housecall Pro instance you actually run the business on?
• Has anyone ever told you the site "broke" after a plugin update, a theme update, or a hosting migration you did not ask for?
• Do you not actually know who owns the domain, the hosting account, or the codebase, because the last agency set it all up under their own login?

Answer yes to two or more, and you are not shopping for a redesign. You are shopping for a rebuild: new code, new hosting, and a site your business owns outright instead of rents from an agency.

If you answered no to all five and your complaint is that the site looks like it was built in 2016 or the copy reads like a brochure instead of a business, that is a redesign. Same foundation, new face. Cheaper, faster, and the right call. The mistake is doing a redesign on top of a foundation that needed to come out.

Sign #1: Your Site Runs on Plugins You Cannot Name

Open your WordPress admin panel and count the plugins. If you cannot explain what half of them do, or if a past agency installed them and never told you, that is your first sign. Every plugin is a piece of software written by a third party, running on your server, with access to your database. Contractor sites we have inherited have shown up with SEO plugins, page-builder plugins, form plugins, security plugins, caching plugins, and slider plugins all stacked on top of each other, each one adding its own JavaScript and CSS to every page load whether that page needs it or not.

That stack is why the site is slow. It is also why it is a security surface. Plugin vulnerabilities are the single most common way small business WordPress sites get hacked, defaced, or turned into spam-link farms overnight. You do not find out until Google flags the site or a customer calls asking why your homepage is selling watches.

A hand-coded rebuild has zero plugins by definition. There is no plugin surface to patch, no plugin conflict to debug at 11pm before a big bid deadline, and no update that can break the site out from under you. That is not a preference, it is a different category of maintenance risk.

Sign #2: You Do Not Control Your Own Hosting, Domain, or Code

Ask yourself who can log into your hosting account right now. If the answer is "the agency that built it" and not you, you do not own your website. You rent it, and the rent is whatever that agency decides to charge for changes, hosting, or the day you finally want to leave.

We have taken over sites for contractors who paid a monthly "hosting and maintenance" fee for years, only to find out the actual hosting cost was a small fraction of that and the rest was a lock-in tax. When they asked for their login credentials to move, the agency stalled, or claimed the domain was registered under the agency's account, not the business's. That is not a redesign problem. That is an ownership problem, and the fix is a rebuild on infrastructure you control from day one.

• Domain: should be registered in your business's name, on your own registrar account, full stop.
• Hosting: for a hand-coded site, that means a Cloudflare account you control, not a third-party server the agency manages behind a paywall.
• Codebase: you should be able to ask for a full export of every file, every asset, every line of code, and get it same-day.

A rebuild on your own Cloudflare account fixes all three at once. The code lives in a repository you have access to. The domain and DNS live under your login. If you ever want to switch developers, or just want peace of mind, you hand over the keys and walk away clean. No hostage situation, no plugin lock-in, no "our proprietary CMS" excuse.

This matters more for contractors than most industries, because trades run on relationships and referrals that outlast any one vendor. A roofer who signed with a web agency in 2019 and wants a different partner in 2026 should be able to make that switch on a Tuesday afternoon. If making that switch requires threats, a lawyer's letter, or starting over from a blank domain, the agency built the site to be un-leaveable, not to serve you. A rebuild severs that dependency permanently, because ownership is designed into the handoff instead of negotiated after the fact.

A redesign cannot fix this. You can repaint every page on a rented platform and still be renting it the day you're done.

Sign #3: Load Times Are Costing You Bids Before You Know It

Every contractor searching for you on a job site, in a truck, or standing in a customer's driveway is on a phone, often on mediocre signal. If your site takes several seconds to load a page, a chunk of those people bounce before they ever see your number. Google also uses load speed (part of what it calls Core Web Vitals) as a ranking factor, so a slow site does not just lose the visitor in front of it, it loses future visitors who never see it in search results at all.

The fix depends on why it is slow. If it is one or two oversized images, that is a redesign-level fix: recompress the images, add lazy loading, done in an afternoon. If it is slow because the platform itself is heavy (WordPress core, a bloated theme, a dozen render-blocking plugin scripts, shared hosting that throttles under load), no amount of image compression gets you under 2 seconds. You are fighting the architecture, not the content.

Run your site through a free speed test and look at what is actually loading. If you see dozens of third-party scripts you did not put there yourself, plugin-generated CSS files, or a hosting response time ("time to first byte") over half a second before a single pixel renders, that is architecture, not content. A hand-coded static site with no plugin layer and Cloudflare's edge network in front of it loads in under 2 seconds anywhere in the US, because there is nothing left to strip out. That is a rebuild outcome, not a setting you toggle on an existing platform.

Think about what a slow site actually costs a trade business. A homeowner with a burst pipe or a failed AC unit in July is not patiently waiting for your gallery images to render. They have four other tabs open to four other contractors, and they call whoever answers the phone or whoever loads a number in front of them fastest. Every extra second of load time on a service page is a second where that homeowner is looking at a competitor's number instead of yours. You never see that bid. It never shows up as a complaint. It just quietly does not happen, and the slow site gets blamed on "the market being slow" instead of the actual cause.

Sign #4: Your Site Cannot Talk to the Software You Run the Business On

This is the sign most contractors do not know to look for, because they have never seen it work correctly. If a lead fills out your contact form and that lead does not show up automatically in your CRM, your booking calendar, or wherever your office manager actually works, you have a wiring problem, not a design problem.

Established trades run on specific software: ServiceTitan, Jobber, Housecall Pro, a call-tracking line, a payment processor for deposits, a review-request tool. A brochure site built on a page builder usually connects to none of it beyond a basic contact form that emails you and dies there. Someone on your team is re-keying every lead by hand, if they remember to.

• Booking: should push straight into your scheduling software, not into a generic form inbox.
• CRM: lead data (name, phone, service needed, urgency) should land in your CRM automatically, tagged by source.
• Call tracking: the number on your site should be trackable back to the specific page or campaign that generated the call.
• Payments: deposit or invoice links should work without sending the customer to a third-party portal that does not match your brand.

This is squarely engineering, not decoration, and it is the reason "just redesign it" often is not the right answer. You can make a page-builder site look sharper, but you usually cannot bolt real API and webhook integrations onto a platform that was never built to hold them. That takes a rebuild with the integrations planned into the architecture from the first line of code, wired to the specific booking, CRM, phone, and payment tools you already run.

Sign #5: When a Redesign Is Actually the Right Call

Not every contractor needs a rebuild, and we will tell you that on the call if it is true. If your foundation is sound, a redesign is faster, cheaper, and the correct move. The signs point the other way:

• The site loads fast (under 2 seconds) already, on a lean plugin count or a codebase you understand.
• You and your team can make basic edits without begging a developer.
• You own the domain, the hosting, and the code outright, no third party holding the keys.
• The integrations you need (booking, CRM, forms) already work, even if clumsily.
• The complaint is purely visual: dated photography, weak copy, a layout that buries your phone number, no clear path to a quote.

In that case, a redesign means new copy, new visual identity, better calls to action, and a conversion-focused layout, built on the foundation you already have. It is a fraction of the cost and timeline of a rebuild, and it is the honest answer when the foundation does not need to come out.

The failure mode we see most is contractors who get talked into redesign after redesign, three or four times over several years, on the same broken WordPress foundation, because it is an easier sell than telling them the truth. Each redesign looks better for six months, then the same load-time complaints, the same plugin breakage, and the same missed-lead problem come back, because nobody touched the foundation. If you have redesigned twice already and still have the same complaints, that pattern itself is a rebuild sign.

There is also a middle path worth naming: a partial rebuild. Some contractors have a foundation that is mostly sound but has one rotten integration, like a booking widget that never actually reaches the office, or a contact form that silently drops submissions during peak traffic. In that case the right move is not tearing out the whole site, it is replacing the broken piece and hand-coding a bridge to the software you actually run. An honest audit tells you whether you are looking at a full rebuild, a redesign, or a targeted fix to one integration. Anyone who quotes you a full rebuild before looking at your actual site is guessing, and anyone who quotes you a redesign without checking your plugin count and load time is guessing too.

What a Rebuild Actually Involves (and What It Does Not)

A rebuild means new hand-coded pages, hosted on infrastructure you control, with your booking, CRM, and phone tools wired in from the start. It does not mean starting your reputation from zero. Your Google Business Profile, your reviews, your rankings for terms you already show up for, and your domain's history all carry forward if the migration is handled correctly, with every old URL redirected to its new address and your on-page content preserved or improved, not gutted.

A typical rebuild timeline runs from a content and sitemap audit of the existing site, through page-by-page hand coding, integration wiring, and a redirect map, to a pre-launch QA pass checking every old URL resolves and every form fires correctly. Expect several weeks of real work, not a same-day flip, and expect to be asked for your existing analytics and search console access so nothing about your current rankings gets thrown away in the move.

1. Audit: every existing page, every integration, every plugin, cataloged before anything gets touched.
2. Content and URL map: what stays, what gets rewritten, what old URLs need 301 redirects to new ones.
3. Build: hand-coded pages on your own Cloudflare account, integrations wired to your actual booking, CRM, and phone tools.
4. QA: every form tested end to end, every redirect checked, every page timed for load speed before launch.
5. Handoff: full codebase, domain, and hosting access in your name, not the agency's.

Done right, a rebuild is the last website project you have to think about as an emergency. Done wrong, or skipped in favor of another cosmetic redesign, it is the same conversation again in eighteen months.