Back to blog
Why we build static sites (and when we don't)
Static generation makes a site faster, cheaper and safer. But it's not for everything: here's how we decide.
GRYFF Studio performancearchitecture
When a client asks for “a fast website”, the technical answer almost always starts the same way: generate the HTML ahead of time.
What “static” means
A static site isn’t assembled the moment someone visits it: it’s built once, when the content is published, and the server simply delivers ready-made files. The result:
- Near-instant loading, even on slow connections.
- Free or nearly free hosting (files are served from a CDN).
- A smaller attack surface: no exposed database, no server to maintain.
And when it’s not enough
If a page shows data that changes per user or per minute — a dashboard, a cart, a feed — pre-generated HTML won’t cut it. That’s where we combine approaches: the structure stays static and the live parts load as small interactive islands.
Our rule
Static by default, dynamic where justified. It’s the reason this very site loads the way it does.