There is a quiet architectural shift underway in how business websites get built, and it runs against fifteen years of received wisdom. The default is moving from dynamic-first — a database, a CMS, server-rendered everything — back to static-first: pre-built HTML, with dynamic behaviour added only where it earns its place.
We want to be careful here, because “WordPress is dead” is a genre of blog post and it has been wrong every year it has been published. WordPress runs an enormous share of the web and will continue to. The question is not whether it works. It is whether it should be your default.
What changed
Static used to mean limited. No forms, no search, no comments, no personalisation — fine for a brochure, unworkable for a business. Modern build tooling removed most of those constraints. Forms, search, e-commerce and interactive components all work cleanly within a static architecture now, because the dynamic parts get delegated to services designed for them rather than bolted onto a monolith.
The security calculus shifted too. WordPress vulnerability disclosures continue to climb — on the order of eight thousand in 2024 — and the overwhelming majority originate in plugins rather than core. A static site has no database to inject, no admin login to brute-force, and no plugin surface to keep patched at 2am.
When static wins
- Marketing sites, brochure sites and content-led businesses — the large majority of business websites.
- Anything where speed is a conversion factor, which is now essentially everything.
- Teams without someone whose job includes patching a server.
- Sites that need to survive traffic spikes without a hosting conversation.
When it does not
This is where most articles on the subject go quiet, so to be direct — static is the wrong default when:
- Content changes many times an hour and rebuild latency becomes operationally painful.
- You need per-user personalised content at scale as the core of the product.
- The team's entire skill set is in an existing stack and there is no capacity to retrain. Architectural purity is not worth a team that cannot ship.
- There is a genuine dependency on a mature plugin ecosystem — complex membership, LMS or booking systems where rebuilding from scratch would cost more than it returns.
Our actual position
We do not think there is a universally correct answer, and we are suspicious of anyone who does. We think static should be the starting assumption for a content-led business website, and that anything else should have a specific reason behind it. A reason is fine. The absence of one is the problem.
The part that matters more than the stack
A fast static site with unclear messaging, no accessibility and no structured data will lose to a well-run WordPress site every time. Architecture is a multiplier on the fundamentals, not a substitute for them.
Which is the honest summary of this entire subject: the stack matters considerably less than most technical debates imply, and considerably more than most marketing teams assume. Somewhere in that gap is a sensible decision, and it depends on your situation rather than on what is fashionable this year.
Key takeaways
- The default is shifting from dynamic-first to static-first for content-led sites
- Modern tooling removed the old limits — forms, search and commerce work fine on static
- The attack surface argument is real: no database, no admin login, no plugin patching
- Static is the wrong call for high-frequency content, deep personalisation, or when it would strand your team
- Architecture multiplies the fundamentals; it does not replace them
Want this handled properly?
Tell us what you're working with and we'll scope it with you — no obligation.