Hand-coded & custom front-end

A CMS earns its keep when non-technical people need to publish regularly. When that's not true — a site whose content changes a few times a year, a landing page, a marketing site with a fixed structure — the CMS is pure overhead: a database, a login, an attack surface, and a monthly patching obligation, all to serve pages that never change.

Hand-coded output is just files. It loads faster because there's nothing to assemble on request, it costs less to host, and there's no plugin to update at midnight because a vulnerability was announced.

This one. Every page here's generated from source into plain HTML and pushed over FTPS — no framework, no client-side routing, no runtime dependency. The images are responsive WebP sets, the fonts are self-hosted so nothing third-party blocks first paint, and the whole stylesheet is one file.

It's also the honest test of the claim: a developer telling you hand-coded sites are fast should be able to point at one.

If you need to publish weekly, you want WordPress. If your site is a fixed brochure that has to be quick and cheap to run, you want this. Most people are told the first answer regardless, because it's the more profitable one to sell.

So — can you build a website without WordPress? Yes, and for a lot of small business sites it's the better call. No CMS, no plugins, no database, no login page, nothing to patch. Just fast pages that keep working while you ignore them.

You will get told which side of the line you're on before any work starts, and if it's the cheaper side, that's what you'll hear.