A classic CMS rebuilds the page on every request. A static site builds it once and then simply serves a file. The difference shows up both in speed and in server bills.
Where static wins
Speed — the browser gets ready HTML with no database round-trip
Security — there is nothing to break into: no site code runs on the server
Cost — serving static files is cheaper than any application
Resilience — a traffic spike does not take the site down
Where static gets in the way
If you have user accounts, a cart with live stock or prices changing every minute, some pages still have to be computed on the fly.
Our compromise
We build public pages statically and move everything dynamic into the client and the API. An editor changes text in the admin panel and presses "Publish" — the build regenerates itself.
For a studio site, a mid-size online store or a corporate portal this is the right balance: editors are comfortable and visitors get the page instantly.