When a WordPress site is worth rebuilding, and when it isn't

Most businesses ask for a rebuild when what they really want is for the site to stop feeling like a chore. Before committing to a full project, it helps to separate the problems that are genuinely structural from the ones that are the result of years of small decisions nobody revisited.

Problems you can fix without rebuilding

Slow pages are usually caused by unoptimised images, a bloated page builder, missing caching or a cheap host. Each of those can be addressed in days rather than months. The same is true of a cluttered admin, a broken contact form or inconsistent typography. If a site's content and structure still match how the business works, repair is almost always the better investment.

Problems that justify a rebuild

A rebuild makes sense when the foundation itself is the obstacle. Common signs: a commercial theme that has not been updated in years, content locked inside page-builder shortcodes, a structure that no longer reflects your services, or a codebase that only the original developer understood. In those cases, every improvement costs more than it should, and you are effectively paying rent on a bad decision made years ago.

A simple test

Write down the five changes you would most like to make to the site. If a developer can make all five without fighting the theme, fix what you have. If three or more require working around the build, plan a rebuild and reuse the content you already have.