All the guides

Technology

WordPress or a static site

The question is not which is better. It is who is going to update it in year three. Almost the whole answer falls out of that.

The short answer

If your site is pages that change rarely — who you are, what you sell, where you are, prices, the odd article — a static site is faster, safer and cheaper to maintain. If you publish several times a week, have several people editing with different permissions, or need a particular plugin ecosystem, WordPress wins and there is no argument. For most small businesses the first description is theirs and the second is the one they were sold.

The underlying difference

WordPress builds each page at the moment somebody asks for it: it queries a database, runs the theme and the plugins, and delivers the result. A static site delivers a file that was already made.

Almost everything else follows from that. Static is faster because there is nothing to compute. It is safer because there is no database to inject into and no login screen to attack. And it costs less to host because any content network will serve a file for next to nothing.

What WordPress gives in return is an enormous ecosystem: thousands of extensions, plenty of people who know how to work on it, and an editing panel almost everybody recognises. None of that is a small thing.

The year-three question

A freshly built WordPress site is fine. The trouble arrives later and always by the same route: the theme and the plugins need updating, updates sometimes break things, and in a small business nobody’s job is to watch for it.

By year three, an uncomfortable share of small-business WordPress sites are out of date, throwing security warnings, with a plugin whose author abandoned it. That is not WordPress’s fault: it needs continuous maintenance, and almost nobody budgets for it at the start.

So the useful question is not which is better today. It is: who updates it in March three years from now, and is that cost in the budget?

  • WordPress: monthly updates, or debt that accumulates
  • Static: nothing to patch on the published site
  • Both need somebody watching; only one breaks when nobody does

When WordPress is the right answer

There are clear cases and they are worth stating, because this site is built without WordPress and that is not an argument. If you publish several times a week and several people edit with different permissions, the WordPress panel is designed for exactly that.

If you depend on a particular extension that only exists there — a sector-specific booking integration, an unusual payment gateway, a membership system — rebuilding it elsewhere costs more than you save.

And if whoever is going to maintain it already knows WordPress, that familiarity is worth more than any technical advantage. A tool people actually use beats a better tool nobody opens.

Where the figures come from

  • The Core Web Vitals Google uses as a page experience signal are LCP, INP and CLS, with "good" thresholds of 2.5 seconds, 200 milliseconds and 0.1 respectively.

    Source Google — web.dev, Web Vitals

Keep reading

Common questions

If your question isn’t here, write to us and we’ll answer it. Contact

Can a static site be edited without knowing how to code?

Yes. An editing panel is connected for text, photographs, hours and prices, and saving republishes it automatically within a couple of minutes. The difference from WordPress is that visitors never touch the panel, because the panel is not part of the published site.

Can I have a shop without WordPress?

Yes, and it usually works better. The catalogue and the payments are handled by a specialist service and the site displays them. You avoid the whole WooCommerce stack and its updates, which is the part that breaks most.

What about a blog?

It works the same way: write in the panel, publish. If you post twice a month, neither option will give you trouble. If you post daily with five editors, WordPress has the advantage.

What if I change my mind later?

Static to WordPress migrates without drama. The other direction too, though usually more work because the content has to be rescued from the database. In both cases what matters is that the content is yours and exportable, which is the question to ask before choosing anything.

We will tell you which one suits you

Tell us how often you publish, who edits, and which extensions you depend on. If your case calls for WordPress, we will say so and build it in WordPress.

Or directly
hola@appnweb.site
Monday to Friday, 09:00 – 18:00 (CET)

Send us a message

What you sell, who buys it, and what you’d like to happen.

A reply within two working days. Your details are not used for anything else.