Guide · AT-R02REV. 2026-A
A website without a cookie banner: is it possible? Yes, here is how.

By Jordan WichertSenior backend developerLast updated:
Why do almost all websites have a banner, then?
Because most banners are self-inflicted. Three usual suspects are almost always behind it: first, tracking – analytics scripts and advertising pixels meant to recognise visitors. Second, third-party fonts – fonts that the browser fetches from Google servers when it visits the website, transmitting the visitor's IP address in the process. The font is then held in the cache, but the request has been made. Third, embeds – YouTube videos, map services, social media snippets, which send data to their providers as soon as they load.
Each of these ingredients sends visitor data to third parties. The legal reasoning is not the same in every case, though. Where something is stored on or read from the visitor's device – that is, with tracking and with embeds that set cookies – § 25 TDDDG requires consent. With the mere loading of a third-party font, by contrast, the question is the balancing of interests under the GDPR (DSGVO), and before the Regional Court of Munich I (Landgericht München I) that went against the site operator (judgment of 20.01.2022, case no. 3 O 17493/20): there was no overriding legitimate interest, because the font could just as well be served from the operator's own server. So the banner is not an obligation that applies to every website. It is the bill for the technology behind it.
Side noteAre cookies forbidden in general?
No. Technically necessary cookies – shopping basket, login, language setting – may be set without consent. What needs consent is whatever is not necessary to run the site, above all tracking and advertising. So an online shop does not necessarily need a banner – a shop with advertising tracking does.
How a website gets by without a banner
The recipe is unspectacular: leave out whatever sends data. Fonts and scripts sit on your own server instead of with a third party – to the visitor it looks exactly the same, except that nobody else is listening in any more. Third-party analytics services are dropped; if you want to know your reach, you count on your own server, as the page is delivered, what the browser transmits with the request anyway – which page was requested and, as a rough category, where the visitor came from. Nothing is stored in the browser for this, and only totals remain on the server. That matters because § 25 TDDDG does not turn on cookies but on any access to information on the end device. Anyone who instead reads device details and builds a recognition value from them (fingerprinting) needs consent just the same. “Without cookies” simply does not mean “without consent”. Videos and maps are loaded only after a click, or simply linked.
In the end it comes down to economical technology: the less third-party code a website drags along, the fewer legal questions it raises – and the less can break.
Enter your website address in the third-party check to see what it loads today. It lists Google Fonts, analytics, maps, videos and third-party scripts, together with the alternative that needs no banner.
How this website does it
This website is built to exactly this recipe: the fonts are hosted by us, visits are counted on our own server without any script in your browser, and without your consent it makes no requests to third-party servers apart from Cloudflare, which delivers it, and sets no advertising or analytics cookies. There is a single service that needs consent: the booking calendar on the appointments page. That is exactly what our slim banner asks about, before anything loads, not afterwards. That is the difference between a banner as the bill for dozens of trackers and a single, honest question. The parts list at the foot of this page lists every resource that is loaded; the details are in the privacy policy (Datenschutzerklärung).
Side noteHow to check any website yourself
Open your browser's developer tools (F12 key) and there the “Network” tab, then reload the page. Every line with a third-party domain is a call to a third party. Anyone who sees dozens of third-party servers there knows where the banner comes from – and what it is trying to manage.
What this means for loading time and trust
Every third-party resource costs time: name resolution, connection, download – all before the page is there. A website without third-party servers loads faster and, above all, predictably, because no third party can slow it down. When it comes to trust, what counts is not whether you are asked at all, but what for. The notice that this page also shows until you have decided anything can be declined without anything missing: the article is there in full, with or without consent. The question is not asked for a collection of services, but for the one appointment booking that must not load without your yes.
This is also how we build our clients' websites: written specifically for them and without third-party code, so that technically no service requiring consent is needed to run them. More under Web design & development.
One point remains even without third-party services: whoever runs your website has access to the data of your visitors and enquiries. That calls for a contract under Art. 28 GDPR (DSGVO). When it is needed and what belongs in it is covered in the guide “Do I need a data processing agreement (Auftragsverarbeitungsvertrag) – and when?”.
This article explains the technology and is not legal advice. Whether a website can do without consent is not decided by the technology alone, but also by what else the operator processes – from the contact form to the contract with the hosting provider. The data protection assessment in an individual case rests with the operator, if in doubt together with their legal adviser.