All the site, none of the WordPress.

Why almost every client site I look after is now static – and what that could mean for yours.

Blue network cables plugged into a rack of servers
The case for going static

WordPress needs constant care.

A static site doesn't.

WordPress runs a huge share of the web, and for years it was the sensible default – it's what I built on too. But every WordPress site is a piece of software running on a server, and software has to be updated, secured, backed up and watched, whether or not anything on the site has changed.

A static site is just the finished pages, served as plain files – and this site runs that way too. Here's the reasoning, including when I'd still tell you to stay put.

Updates · Plugins · Attacks

What WordPress really costs to keep

None of this is a criticism of how your site was built. It comes with the platform – and it carries on for as long as the site is live.

WordPress is capable, well-supported software, and a well-kept WordPress site can be fast and secure. The point is the keeping: the work described here has to be done by someone, month after month, and it's rarely part of the original quote.

For a site that mostly presents information, that's upkeep on machinery it doesn't need.

It never stops needing updates

WordPress itself, the theme and every plugin release updates regularly – many of them security fixes. Leave them and known weaknesses stay open; apply them and something can break. Either way, somebody has to be watching.

Every plugin is someone else's code

A WordPress site often leans on a dozen or more plugins from different developers. Each one is a possible conflict, often a licence to renew, and a potential way in if it stops being maintained.

It's a permanent target

Because WordPress is so widely used, attacks on it are automated. Bots routinely try login pages and probe for known plugin weaknesses – on small business sites as much as big ones.

It needs a server to match

Each visit normally has the server build the page from a database. Keeping that quick usually means caching, a properly specified server, and PHP and database upgrades every few years.

And most of it only keeps you where you are

It's why a WordPress site needs ongoing care, security measures and regular backups just to stay as good as it was on launch day – and why a neglected one tends to get slower, less reliable and more exposed over time.

What changes

What a static site gives you

  • Far less to attack – no database, no admin login and no plugins running on a server
  • No software updates – the pages stay exactly as they are until you change them
  • Speed everywhere – pages are served from Cloudflare's global network, close to each visitor, with no server building them on demand
  • Fewer moving parts – no plugin licences to renew and no server software to keep in step
What stays the same

What you keep

  • The same design, wording and page addresses, with redirects for anything that does move – set up so search rankings carry over
  • Contact forms that still reach your inbox, with spam protection built in
  • Visitor statistics without cookies – so, on most sites, no cookie banner
  • Editing for your own team – change text, swap images and publish from a simple editor, with the design and code safely out of reach
White and red light trails from traffic on a road at night
The move

From WordPress to static in four steps

Your live site carries on untouched until the new one is ready and you've approved it.

Audit

I go through the current site: every page, form, redirect and plugin, and what each one actually does. Most plugins turn out to be solving problems a static site doesn't have. You get a fixed price and a clear list of anything that will work differently.

Rebuild

The site is rebuilt as static pages on a private preview address, matched to the original page by page – or redesigned, if that's what it needs. Nothing changes on the live site while this happens.

Review

You check the preview on your own devices and sign it off. Titles, descriptions, page addresses and redirects are all checked against the old site, so search engines find the same site in a faster form.

Switch-over

The domain is pointed at the new site – a quick change, planned to avoid downtime. The old WordPress site is archived as a restorable copy, and the old hosting can be closed once you're happy.

The honest answer on whether it's right for your site starts with a look at what you've got.