Static or WordPress: one honest question decides it

Here's the question: how often will you genuinely change this website yourself?

Not how often you'd like to. Not how often you intend to. How often you actually will, given how your week goes.

If the honest answer is weekly or monthly, you want a content management system, and WordPress is the obvious one. If it's a few times a year, static is faster, cheaper to run and has almost nothing to go wrong. That's most of the decision.

Why the answer is usually "rarely"

Most small business owners install a CMS for the freedom to edit, then edit twice in three years. Meanwhile the site carries the weight and the maintenance burden of a system built for publishing, in service of publishing that never happens.

It's an entirely reasonable mistake. Nobody sells you the version where you don't need the flexibility.

What static actually means

The pages already exist as files. When someone visits, the server hands over the file. There's no database query, no plugin chain, no page being assembled on request.

The consequences are mostly good. It's fast, because there's nothing to compute. It's cheap to host. And there's very little to attack — no database to inject, no admin login to guess, no plugin with a known vulnerability.

The cost is that changing content means either editing code or asking someone. That's the whole trade.

What WordPress actually gives you

A login, an editor, and an enormous ecosystem of plugins that solve problems you'd otherwise pay to have built. Memberships, forums, event calendars, bookings — someone has already built it.

That ecosystem is genuinely WordPress's best feature, and it's also where its problems come from. Every plugin is code maintained by someone else, a potential conflict, and a potential vulnerability. Sites get compromised through outdated plugins routinely, usually found by automated scans rather than anyone targeting the business.

The maintenance question nobody raises during the sale

WordPress needs attention every month. Core updates, theme updates, plugin updates, PHP versions aging out, backups verified. Skipped for long enough, applying a year of updates at once becomes its own risk, which is exactly why people keep putting it off.

That's not an argument against WordPress. It's an argument for knowing the cost before you choose it, because it's either money or your own time, permanently.

The cases where the answer flips

Multiple people update the site. A team needs accounts and permissions. Static gets awkward.

You publish genuinely often. Listings, events, news, case studies. If waiting on someone would stop you doing it, you need the login.

You need a specific plugin. Membership systems and forums are solved problems on WordPress and expensive to build from nothing.

Selling products. That's a different question again, and usually the answer is a purpose-built store platform rather than either of these.

Whichever you choose

The platform matters far less than the execution. A well-built WordPress site beats a badly built static one comfortably. What determines whether a site gets found and converts is speed, structure, content and clarity — and you can get all four wrong or right on either.

Choose based on how you'll actually use it, then insist on it being built properly. That order round produces better outcomes than agonizing over the technology first.