Most websites build every page fresh for every visitor: the server runs code, queries a database, assembles the page, and sends it. That flexibility has a cost in speed and security. A growing number of the fastest sites on the web skip all of it.
A static site is pre-built. Every page is turned into a plain, ready-made file in advance, so when someone visits, there is nothing to assemble, the finished page is simply handed over.
Why it's fast and safe
- Speed — no database query, no server work per visit; pages arrive almost instantly.
- Security — no database and no live code means far less to attack.
- Cheap and resilient — plain files are trivial to serve and hard to knock over.
This is the heart of the "Jamstack" approach, and it is exactly why this very site is built as fast, mostly static pages. The content is prepared ahead of time, so visitors get speed and search engines get a site that responds instantly.
The fastest page is the one that was already finished before you asked for it. Static sites simply do the work up front, once, instead of on every single visit.
Who it suits
Static shines for sites whose content doesn't change every second, marketing sites, blogs, documentation, portfolios. If you need constant, per-user dynamic content, you'll want more moving parts. But for a great many business sites, "no database" is a feature, not a limitation.
