Designing a site that doesn't need a cookie banner
A checklist we now run on every project before the first wireframe.
On this page3 sections
A cookie banner is a design problem that starts in the tech stack. By the time a designer sees it, the decision is already made. So we moved the decision to the kickoff.
The kickoff checklist
List every third party
Fonts, maps, video, chat widgets, analytics, forms. Write down the domain each one loads from.
Self-host what you can
Fonts and icons go on the same domain. That alone removes two requests to Google on most sites.
Replace embeds with links or facades
A static map image linking to the map, a video poster that loads the player on click.
Pick cookie-free analytics
We use Plausible. Umami works too if the client wants to host it themselves.
Check the network tab on launch day
Load the homepage with an empty cache and count the domains. Our target is one, plus the analytics host.
What it costs
Usually less than a banner. A consent tool costs money every month, needs legal review and adds a layout shift on every first visit. Self-hosting fonts takes ten minutes.
When you still need one
If a client needs ad retargeting or a CRM that tracks visitors by name, they need consent, and we design a banner that is honest about it. That has happened twice in two years.