Building a Website That Costs Almost Nothing (and Still Performs)
The modern web has a peculiar property: the fastest and most reliable sites are often the cheapest to run, while the slow and fragile ones tend to carry significant monthly infrastructure costs. This inversion is counterintuitive if you assume that performance scales with spend, but it makes perfect sense once you understand that most of the complexity that makes websites expensive is complexity they introduced themselves.
A static site served from a CDN edge node is faster than a dynamically rendered WordPress site on a VPS for a structural reason: it involves fewer moving parts. There is no database query, no PHP execution, no server-side rendering happening at request time. The HTML file exists, it gets delivered, the browser renders it. The chain from request to response is as short as it can physically be. Edge hosting providers like Cloudflare Pages, Netlify, and GitHub Pages offer this at zero cost for most traffic levels because the infrastructure cost to them is genuinely low.
The performance implications are not trivial. A site loading in under a second from anywhere in the world, served from an edge node close to the user, passing Core Web Vitals without optimization effort, is not a compromise — it is technically superior to most commercial hosting arrangements. The sites that rank well in search, load reliably under traffic spikes, and survive infrastructure incidents are disproportionately static. That is not a coincidence.
Building a static site requires choosing a static site generator, and the options here are genuinely good: Hugo builds at extraordinary speed, Jekyll has a mature ecosystem and GitHub Pages native support, Astro handles content and component needs with modern tooling. The learning curve for any of them is measured in days, not weeks. The content workflow is markdown files in a folder, which is both portable and version-controllable — meaning your entire site lives in git, can be restored from any point in its history, and can be migrated to any host in under an hour.
The cost structure for this setup is nearly zero. Domain registration is the primary annual expense — typically $10–15 for a standard TLD. Hosting is free up to very high traffic levels on every major static host. If you add a CDN layer, Cloudflare’s free tier handles it. A custom email address adds a few dollars per month. An entire content operation — multiple sites, substantial traffic, professional presentation — can run for under $200 per year in infrastructure costs. The margin this preserves for actual business development is not a minor consideration.
The objection that usually arrives here is that WordPress offers things static sites don’t: plugins, dynamic functionality, e-commerce, membership areas. This is true for complex requirements. It is irrelevant for the vast majority of content sites, portfolio sites, documentation sites, and early-stage SaaS marketing pages, all of which need fast, reliable delivery of text and images and nothing more elaborate. The additional capability of a CMS carries a real cost in complexity, hosting overhead, security maintenance, and update management. That cost is worth paying when the capability is needed. It is dead weight when it isn’t.
The discipline of building light is not a poverty mindset — it is an engineering mindset. Infrastructure is not an asset; it is a liability with an upside. The upside of a complex, expensive stack is capability. The liability is cost, maintenance, and failure surface. When the capability isn’t required, the liability is pure. Keeping it minimal is not frugality. It’s accuracy about what the system actually needs to do.