MManiRush
← All posts

Static Site or WordPress: The Real Cost

The headline numbers are not the real numbers

A static site on shared hosting and a WordPress site on the same hosting can show the same monthly invoice. The difference appears at year two, when plugins renew, a theme breaks after a core update, and someone has to spend a Saturday on a security patch.

Static pages are files. There is no database to compromise, no login page to brute force, and no plugin that stops receiving updates. That is not a marketing claim, it is the shape of the attack surface.

What WordPress gives you for the money

A writing interface, a media library, revisions, scheduled posts and a plugin for anything you can name. If two people who are not comfortable with markdown need to publish daily, that is worth paying for.

The cost is real though: a security plugin, a cache plugin, a backup plugin, and the time to keep them from arguing with each other. Budget an afternoon a quarter.

What a static site costs you instead

Your time up front. There is no editor, so publishing means generating files. That is fine once a build script exists, and painful before it does.

You also lose the ability to let a non-technical person change the layout without touching a template. If that person exists, factor their waiting time in.

On speed, a static file served from a cache is hard to beat. Google's own guidance on Core Web Vitals rewards a page that loads without waiting on a database query, and that is the default here rather than an optimisation project.

The costs nobody puts in the comparison

Plugin renewal stacking. Five plugins at 40 dollars each is a 200 dollar annual bill that arrives in five separate emails.

Cache invalidation. A page that serves stale content to half your visitors costs more in trust than in money, and it is the most common static hosting mistake too. Change the path, not the query string, when you need a file to refresh.

Your attention. A site that needs nothing done to it frees the hours that would have gone into maintenance, and those hours are what actually produce content.

The migration you will eventually want

Whichever you start with, assume you will move. Sites move because the editor stopped being updated, because the bill doubled, or because the person who maintained it left.

Moving out of a database is the expensive direction. Exporting files into a database is cheap, and there are tools that do it. So if the decision is genuinely close, starting static keeps the cheaper exit open.

What speed is actually worth

Fast pages earn more of the clicks they are offered, and they cost less to serve. Those two effects compound, which is why speed work pays back out of proportion to the effort.

Two changes get most of the benefit: serve images in a modern format and let the browser defer anything below the fold. On a site with many similar pictures, the image format alone is usually the largest single win. Converting a folder of illustrations from PNG to WebP cut one catalogue from five megabytes to under three hundred kilobytes.

Then check the delivered bytes rather than the folder size. What the browser fetches is the only number that matters.

How to choose without guessing

If one person writes and that person can run a command, go static. If a team writes and none of them can, pay for the editor. If the site takes money or stores accounts, neither default is enough on its own and the security work is the same either way.

Whichever you pick, own the content as files in a repository. That single decision makes migration a weekend job instead of a rewrite.

RS
Rahul Sharma

Writes about AI, automation and the practical tools behind them. Every article here is written by a human and illustrated with original artwork.

More about the author

Comments

Sign in with GitHub to join the discussion. Comments are stored in GitHub Discussions, not on this site.

↑