Static First Is Still the Best Deal on the Web
Most business sites do not need a server rendering pages on demand. They need to be fast, cheap, and impossible to knock over. Static gets you all three.
Every few years the industry rediscovers server rendering, gives it a new name, and tells you your site needs it. Meanwhile the sites I build for lawyers, accountants, and contractors keep doing the boring thing: render everything ahead of time, serve it from a CDN, and let the pages be pages.
Here is my honest position after years of building both ways. For most business websites, static generation is not a compromise. It is the better product.
What static actually buys you
- Speed you do not have to manage. A pre-rendered page served from an edge cache is fast in Michigan, fast in Manila, fast on hotel wifi. No tuning, no cold starts.
- A security surface close to zero. There is no server executing your code per request, which means most of the attacks that ruin weekends simply do not apply.
- Hosting costs that round to zero. The bill for a static site is lunch money, and it does not spike when you get featured somewhere.
- Uptime by default. When there is nothing to crash, nothing crashes.
But my content changes
This is the objection I hear most, and it made sense in 2015. It does not anymore. Modern frameworks rebuild individual pages when content changes, in seconds, triggered by your CMS. Your editor hits publish, the page regenerates, the CDN updates. Nobody is writing HTML by hand, and nobody is waiting on a full site rebuild.
The sites I run publish new articles weekly through an automated pipeline. They are still fully static. Publishing and static are not in tension; they compose beautifully.
Where I actually reach for a server
Real application state: dashboards, accounts, anything personalized per user. Search over large content sets. Form handling, which wants one small serverless function, not a whole server. If your site is a marketing presence with a blog and a contact form, that is one function and ten thousand static pages.
The test I use
Ask what on this page is different for each visitor. If the honest answer is nothing, that page should be built once, not per visit. Most business sites fail this test on every single page, which is exactly why they should be static.
Fast, cheap, and impossible to knock over is a hard combination to argue with. Your visitors feel the first one, your budget feels the second, and you sleep better because of the third.