Term
Static website
A website whose pages are generated in advance as finished files that the server simply sends, with no database or processing on each visit. It is very fast, cheap to run and more secure because there is little to attack, and it suits company websites and glossaries.
Updated
What it means
A static website is a site whose content is generated in advance, at build time, as finished HTML, CSS and JavaScript files. On each visit the server simply sends them, without running database queries or scripts. The opposite is a dynamic site, such as a classic content management system that assembles every page on each request.
Static sites today are mostly built with generators that combine templates with content from text files or a headless CMS. The output is deployed to hosting or distributed through a CDN to servers around the world. Static does not mean unchanging: content is updated by a new build, often automatically after every change.
A static site can still have interactive features: forms, calculators, search or multiple languages. These run in the browser or through separate server functions called only when needed. This website, including the glossary and the price calculator, is built this way.
How it works in practice
The main advantage is speed. Pre-built pages load almost instantly, improving Core Web Vitals, user experience and search rankings. For company websites, blogs, documentation or glossaries, where content does not change every minute, the static approach is also ideal for SEO.
The second advantage is security and low cost. With no database and no publicly reachable admin area, the attack surface is minimal. There are no plugin security updates to chase, and hosting static files is cheap or free. The site also handles sudden traffic spikes without going down.
The drawback is that editing content usually requires technical skills or a connection to a headless CMS, where editors write in a friendly interface. For online stores with thousands of products and frequent price changes, or sites with user login, hybrid solutions combining static pages with dynamic parts are used.
What to watch out for
When moving from a dynamic to a static site, redirects for old addresses must be prepared and the URL structure and metadata preserved, or the site will lose search rankings. Forms, analytics and cookie consent, previously handled by plugins, also need solving.
A static site is not automatically secure in every respect. Server functions for forms, API connections and third-party keys must be protected as carefully as on any site. Secret keys must never end up in code sent to the browser, and processing personal data from forms must comply with the GDPR.
Need the term explained on your own situation? Consulting from €55 / hour excl. VAT, depending on topic and complexity.