Most agencies and designers answer this question based on scope and budget. A developer answers it differently: based on where the performance failure actually lives. This is the diagnostic framework.
In Brief
A website redesign updates visual design, UX, and content within the existing technical structure. A rebuild replaces the foundation — CMS version, theme architecture, plugin stack, or hosting setup. The right choice depends on where the performance failure lives, not on how the site looks.
The question of rebuild vs redesign is almost always asked too late — after a developer has already estimated the cost of a redesign and the client has approved it. The correct time to ask it is before any scope document is written. Here is how to answer it.
Answer these honestly before requesting any quotes. If you answer "No" to 4 or more, the foundation is compromised and a redesign will not fix it.
1. Does your site load in under 3 seconds on mobile?
Test with PageSpeed Insights on a mobile throttled connection
2. Can your current plugin stack be updated without breaking the site?
If updates are avoided because "something breaks", the foundation is fragile
3. Does your CMS support the integrations you currently need?
Custom glue code to connect systems is a rebuild signal
4. Is your WordPress and PHP version within two major releases of current?
PHP 7.x with WordPress 5.x in 2026 is structural debt, not a cosmetic problem
5. Is your checkout or lead form conversion rate at or above industry average?
Persistent low conversion with good traffic usually indicates UX architecture, not visual design
6. Would fixing the visual design solve 80% or more of the complaints you hear?
If yes, a redesign is the right scope. If no, the problems are structural.
5–6 Yes
Redesign is likely right
Your foundation is sound. The issues are cosmetic, UX, or content. A visual redesign within the existing platform is the correct scope.
3–4 Yes
Partial rebuild warranted
Some foundation work is needed alongside the visual changes. Scope should include plugin audit, PHP upgrade, and performance remediation — not just visual design.
0–2 Yes
Rebuild required
The foundation is compromised. Redesigning on top of it produces a better-looking site with the same underlying problems. A rebuild is the only correct path.
| Factor | Redesign | Rebuild |
|---|---|---|
| Scope | Visual, UX, content | Technical foundation |
| Existing platform | Stays in place | Replaced or restructured |
| Data migration | Usually not required | Content migration planned |
| Timeline | 4–8 weeks | 8–16 weeks |
| Starting cost | ₪2,500–₪7,500 | ₪7,500–₪30,000+ |
| Performance impact | Moderate (visual weight) | High (structural + visual) |
| SEO risk | Low (with redirects) | Medium (requires full redirect map) |
| Best for | Sound foundation, cosmetic issues | Structural debt, broken integrations |
Your PHP version is below 8.0 (end of active support since November 2022)
Updates to plugins or WordPress core are avoided because they break the site
Your checkout or form completion rate is below industry average despite good traffic
You have custom glue code connecting systems that were never designed to integrate
Site performance does not improve meaningfully after caching plugin optimisation
Your theme was purchased, heavily modified, and now cannot be safely updated
Discovery and technical audit
Document every current feature, integration, user role, and custom behaviour. Audit the existing plugin stack, database schema, and performance baseline. Identify what must be preserved, what can be improved, and what should be discarded.
Architecture planning
Design the new plugin stack, theme approach, hosting configuration, and integration architecture before writing a line of code. This is where the rebuild earns its cost — decisions made here determine whether the new site has the same problems in 3 years.
Staging build
Build the new site on a staging environment completely separate from the live site. The existing site continues operating normally throughout. Content from the live site is not migrated until the build is complete and approved.
Content migration and QA
Migrate content, media, and user data to the staging environment. Test all functionality: forms, checkout flows, member access, integrations, payment processing. Document and resolve every issue found before go-live.
URL mapping and redirect implementation
Map every existing URL to its new equivalent. Implement 301 redirects for any URL that changes. Verify redirect chains. Submit updated sitemap to Google Search Console within 48 hours of launch.
Staged go-live and monitoring
Switch DNS, monitor Core Web Vitals and crawl errors for 48 hours post-launch. Address any issues found during the first live traffic cycle. Hand over documentation, plugin management guidance, and credentials.
Describe your current site, what is not working, and what you need it to do. I will review it and tell you which path is correct — no pitch, no commitment required.
Start the briefA short intro call. No commitment. Just a conversation to see if we're a fit.
15-minute intro. No obligation.