What runs on this site, and what deliberately does not
Static HTML, a server in Germany, no requests to outside domains. And what that means day to day.
This site went live today. It is a set of pre-built HTML files sitting on a server in Germany, handed out as they are when someone asks for them. No PHP process, no database, no runtime that has to warm up first.
No third-party server involved
The fonts are ours, the icons sit in the HTML as SVG, and there is no visitor counter, no map widget and no video embedded from somewhere else. Open the network tab while reading this post and you will not find a single request that leaves this server.
The reason is arithmetic. Every outside domain costs a DNS lookup, a TLS handshake, and a processor that has to be named in the privacy policy.
One single script
For the whole site the browser loads exactly one JavaScript file. It keeps a link click from rebuilding the entire page. On top of that there are a few lines inline in the HTML, for the menu and the contact form. That is all of it.
The contact form posts to a small service of our own on the same server. A mail goes out from there.
Why this is written down
Because “fast” and “GDPR-compliant” appear on every second agency site and cost nothing to say. The sentences above you can check instead, in two minutes, with the developer tools already built into your browser.