Should You Fix Your WordPress Site or Rebuild It?

Something is wrong with your website. Maybe it is painfully slow. Maybe it got hacked and is redirecting to spam. Maybe your hosting provider sent an email about a PHP upgrade and now nothing works. Maybe you just tried to update a page and the editor is broken. Whatever brought you here, the question is the same: is this fixable, or do you need to start over?

The Five Scenarios

Most WordPress problems fall into one of five categories. Where you land determines whether a fix or a rebuild makes more sense.

Your site got hacked

Redirects to spam. Google showing a security warning. Your hosting provider suspended your account. This is stressful, but a hack on its own is usually fixable. A specialist removes the malware, patches the vulnerabilities, and hardens the site. Cost: $125-$500 for a cleanup.

The exception is a site that has been hacked multiple times. Repeat hacks usually mean there is a structural problem. Outdated core files, abandoned plugins with known vulnerabilities, or hosting that is not secure enough. At that point, you are patching a leaking boat. A rebuild with tighter security defaults and a cleaner codebase makes more sense.

Your site is painfully slow

Takes 5-15 seconds to load. Mobile PageSpeed score under 40. Visitors leave before the page finishes rendering. Slow sites lose both customers and Google rankings.

Sometimes this is fixable. Install caching, optimise images, remove unused plugins, upgrade hosting. If the theme is clean and the site architecture is sound, a speed optimisation can bring load times under three seconds for $300-$800.

If the site is built on a heavy page builder (Elementor, Divi, WPBakery) and the theme itself is the bottleneck, no amount of caching fixes the underlying problem. The page builder generates bloated HTML and loads scripts you cannot remove without breaking the design. In that case, a rebuild on a cleaner foundation is the only real fix.

You cannot update content

You try to edit a page and the visual builder crashes. Or the layout breaks when you change text. Or the page builder shows a different version of the page than what visitors see. This usually happens with older page builders that have not been updated, or themes where content is hard-coded rather than editable.

If it is a plugin conflict, a developer can usually sort it out in a few hours. If the page builder itself is abandoned or fundamentally broken, you are stuck. You cannot maintain a site you cannot edit.

Your developer disappeared

The person who built the site is no longer reachable. You do not have admin credentials. You do not know who hosts the site. Updates have stopped. This is more common than you might think.

The first priority is regaining access. Check your email for hosting invoices, try password recovery on WordPress, contact the domain registrar. Once you have access, a new developer can assess the site and advise on whether it is worth maintaining or better to rebuild.

Your hosting provider is forcing a PHP upgrade

You got an email saying your site will be upgraded to PHP 8.2 or 8.3. If your site runs on older PHP (7.4 or 8.0, both end-of-life), this upgrade may break things. Old themes and plugins that were never updated for newer PHP versions simply stop working. The result is a white screen or a site full of errors.

If the theme and most plugins are actively maintained, a developer can usually update them to work with the new PHP version. If the theme is abandoned (no updates in 12 months or more) or relies on deprecated functions, the upgrade path leads to a rebuild.

When a Fix Makes Sense

• The WordPress core and theme are still actively supported and receiving updates
• The problem is a single issue (one hack, one slow plugin, one broken form) rather than accumulated neglect
• The site design and structure still work for your business
• The site was built on a clean theme or custom code, not a heavy page builder
• Your mobile PageSpeed score is above 50 (performance issues are surface-level, not architectural)
• The fix cost is well under half of what a rebuild would cost

A targeted fix is almost always cheaper and faster than a rebuild. If the bones of the site are solid, it makes sense to repair rather than replace.

When a Rebuild Is the Better Option

• The theme is abandoned or unsupported (no updates in over 12 months)
• The site is built on a deprecated page builder that generates bloated code
• WordPress core is three or more major versions behind
• The site has been hacked multiple times, indicating structural weaknesses
• Your business has changed significantly since the site was built (different services, different audience, different positioning)
• Nobody has admin credentials and the site cannot be recovered
• The estimated cost of fixing everything exceeds 60-70% of a rebuild cost
• Mobile PageSpeed is below 40 and the bottleneck is the theme itself

Cost Comparison

These are NZ industry ranges, not just our pricing. The actual cost depends on the complexity of your site and how much has gone wrong. A good developer will assess your site before quoting and tell you honestly which option makes sense.

Does It Have to Be WordPress Again?

If you do decide to rebuild, it is worth asking whether WordPress is still the right platform. WordPress powers a huge share of the web and it is a solid choice for many businesses. But it is not the only option, and for some use cases, other approaches work better.

When WordPress is still the right choice

• You need a CMS that lets you or your team update content easily
• You need e-commerce with WooCommerce
• You want access to a large ecosystem of plugins
• Your developer specialises in WordPress
• Your site needs a blog or regularly updated content

When to consider something else

• Your site is mostly static (a few pages that rarely change). A framework like Next.js with static generation will be faster, more secure, and need almost no maintenance.
• You are tired of plugin updates, security patches, and database maintenance. Static or hybrid sites have a much smaller attack surface.
• You need very fast load times and high performance. Custom-built sites without WordPress overhead consistently score higher on Core Web Vitals.
• You want a site that will run for years without needing constant software updates.

There is no universally right answer. WordPress is great when you need its flexibility. But if your site is five pages that change once a year, running a database-driven CMS is unnecessary overhead.

How to Protect Yourself Next Time

• Register your domain in your business name. Not your developer's.
• Keep admin credentials for your CMS, hosting, domain registrar, and all third-party services.
• Insist on backups stored somewhere you can access.
• Get a maintenance plan or at least a relationship with someone who can apply updates.
• Ask for documentation. A simple handover document listing what the site is built on, where it is hosted, and how to access everything.
• Choose a developer or agency that will still be around in two years. Check their track record.

Not Sure What Your Site Needs?

If your WordPress site is giving you trouble, <a href="/contact">get in touch</a>. We will take a look and tell you whether it is worth fixing or whether a rebuild is the better path. No obligation, no pressure. Just an honest assessment.