Static site
A static site is served as prebuilt HTML, CSS, and assets. The server does not run application code per request — it hands over files that were generated at build time.
A build step turns templates and content into a folder of files. A CDN ships those files to the visitor. That is why static sites are fast and cheap to host, and why Core Web Vitals are easier to keep green: there is no database round-trip on the homepage.
Most marketing sites should be this, even when they have a CMS. Framer, many Next.js sites, and a Git-backed studio site all pre-render. Forms, search, and personalisation can still be client or edge functions without making every page dynamic.
You give it up when the page is different for every user — an app, a dashboard, a logged-in account. Calling that a static site is a category error. We default to static for anything a stranger should load in a second, and we add a server only where a request has to know who you are.
Book a call