When WordPress Is Overkill

Knowing when WordPress is overkill is more useful than knowing how to install it, and far less commonly written about — because most of the people who write about WordPress make their living from people choosing it. We publish plenty of WordPress material ourselves. This piece is the other direction, and it is the one we would give a friend over coffee.

WordPress is a content management system carrying two decades of extensibility. If your project does not need extensibility, that machinery is not free — you pay in setup time, in monthly attention, and in the risk that comes with a plugin layer. Sometimes a hosted builder is simply the right answer, and it is not a consolation prize.

Four project types where the builder wins outright

The five-page brochure site

A restaurant, a plumber, a therapist, a two-person consultancy. Home, About, Services, Contact, maybe a gallery. No content velocity — the site changes when the phone number changes. No structured data, no taxonomies, no archive that needs designing. Everything WordPress is good at is irrelevant here, and everything it asks of you still applies. Build it on a hosted builder in an afternoon and go back to work.

The one-person business with nobody to call

This is the decisive one, and it is about the org chart rather than the site. If there is no developer, no agency, no retainer and no appetite to debug a white screen at nine on a Sunday evening, WordPress is handing you a responsibility you have no way to discharge. The five-hour median between a vulnerability being disclosed and the first exploit attempt is not a burden to give a sole trader who will not log in for four months. Hand them a platform where that entire category of problem belongs to somebody else.

Anything with an end date

Wedding sites, conference sites, campaign landing pages, a launch microsite that gets folded into the main brand next year. WordPress's advantages — ownership, portability, extensibility, the SEO ceiling — all compound over time, and a site with eighteen months to live never reaches the point where they pay back. Its costs, meanwhile, start on day one. A short-lived site should be cheap to build, cheap to abandon, and boring.

Portfolios where the work is the product

Photographers, illustrators, architects, designers. Here the site's job is to disappear behind the images, and hosted builders are genuinely excellent at that — their template systems are built by designers for exactly this brief, image handling and galleries are native, and there is no theme to fight. WordPress can do it, with a premium theme and a gallery plugin and a fortnight. The output will not obviously be better.

One more that does not need its own heading: if bookings or scheduling are the actual product — a clinic, a studio, a tutor — builders do that natively while WordPress does it through a plugin you now have to maintain forever.

The maintenance burden, priced in hours

Nobody quotes this line in a comparison, because it does not arrive as an invoice. These are our reasoned estimates rather than research findings, and we would rather label them than dress them up:

• Small site, managed host, auto-updates on: 15–30 minutes a month. Glance at the dashboard, confirm nothing broke, deal with the occasional plugin that needs a nudge.
• Manual updates with staging checks: 1–2 hours a month. The responsible approach for a site that earns money, and the one most owners abandon by month four.
• After a plugin conflict or a compromise: 4–20 hours, unplanned. Always urgent, never convenient, and the recovery is worse if your host only takes weekly backups.
• Hosted builder: effectively zero. Not "low." There is no update routine, because the platform updates itself and there is no plugin layer to break.

Now put those hours next to the money, because the comparison is brutal. Doing it properly is roughly eighteen hours a year. Pick whatever your own hour is worth and multiply. At almost any professional rate, that number dwarfs the entire three-year price difference between the two routes — which comes to $46.04 in the builder's favour on a realistic WordPress build. You are not saving money by maintaining a website yourself. You are choosing to be paid nothing for it.

That trade can still be worth taking, and our WordPress vs website builders comparison sets out the full arithmetic on both sides. It just has to be a decision rather than an assumption.

The argument nobody wants to hear

You will not keep it updated. Not you specifically — you might be the exception — but the median owner, on the median small site, absolutely will not. It goes the same way every time. Month one, you update religiously. Month four, an update breaks a layout and you learn to wait. Month nine, the notification badge is just part of the furniture. Month eighteen, there are fourteen pending updates and one of them is for a plugin whose developer stopped answering support threads in 2024.

An unmaintained WordPress site is worse than a builder site, not better. All of WordPress's advantages assume somebody is looking after it. Remove that assumption and you are left with the risks and none of the benefits.

The numbers say why this matters more than it used to. Patchstack recorded 11,334 new vulnerabilities across the WordPress ecosystem in 2025, up 42% year on year, with 91% of them in plugins. High-severity disclosures more than doubled. And the safety nets are thinner than their marketing: hosting-level defences blocked 26% of total attacks in that data, while traditional web application firewalls stopped 12% of WordPress-specific vulnerability attacks. Managed hosting helps. It does not replace you.

So answer honestly, and out loud: who is going to do the updates? If the answer is a name — yours, a retainer's, a managed-updates plan you are already paying for — WordPress is a reasonable choice. If the answer is a shrug, the decision is made, and choosing a builder is the responsible outcome rather than the lazy one.

The cost edge is shorter than you think

One more reason to be sceptical of the default advice. WordPress's price advantage over a hosted builder is real in year one — $190.28 against $348.00 on a typical build — and it is almost entirely a product of introductory hosting rates. SiteGround's GrowBig plan renews from $6.69/mo to $29.99/mo, a 4.5x jump; Hostinger's tiers climb by 3.3x to 4.3x. By month thirty-one of thirty-six, the builder is the cheaper of the two, and it was predictable the whole way through. Rocket.net is the one host in this set that advertises no renewal increases in writing, which is worth knowing if you go the WordPress route anyway.

Three signals you should have chosen WordPress

The argument runs both ways, and these three are the ones that show up early enough to act on.

1. Your page list is growing and the admin is getting slow. Builders are comfortable up to a few dozen pages and degrade past a few hundred. If you are publishing regularly and expect to pass fifty pieces of content within two years, you are heading for a wall that no plan upgrade removes.
2. You are duplicating a layout by hand. Copying a page template for each property, course, recipe, staff member or case study means you have structured content and no way to model it. Custom post types and custom fields exist for precisely this, and hosted builders have no real equivalent. Twenty hand-made copies is annoying; two hundred is unmanageable.
3. You need to leave and cannot. The moment a builder's pricing, policies or roadmap stops suiting you, you discover there is no meaningful export — you rebuild. WordPress hands you a database and a file tree, and every managed host in the market will migrate them free. WordPress moves anywhere; a builder site moves nowhere. If portability is a business requirement rather than a preference, that asymmetry decides it.

If you already built the wrong one

Going from an over-engineered WordPress site to a builder is easy and slightly humbling: you export the content, rebuild four pages, and cancel the hosting. Going the other way costs more, because there is no export worth the name and you are rebuilding the design regardless. That asymmetry is a reason to give the decision an hour now rather than a fortnight later — and a reason to lean towards WordPress if you genuinely cannot tell which way your site is going to grow.