Cookie Banner Load Time: How It Slows Your Site

Does a cookie banner slow down your website loading speed?

Yes, a cookie banner can noticeably hurt your website loading speed, especially on mobile and on a first visit. Many banners from well-known providers first load a script, then a configuration, stylesheets, fonts, translations and lists of every integrated service, often from several third-party servers. Only once all of that has arrived does the banner become visible. Because it appears on every page and for every new visitor, this delay hits the very first impression. So if you want to improve page speed, check not only images, theme and plugins, but the cookie banner too.

The issue is often overlooked because the banner rarely stands out on your own computer. You dismissed it long ago, your choice is saved, and on fast office Wi-Fi everything loads quickly anyway. A new visitor on a phone using mobile data, by contrast, goes through the whole loading chain: blank space, then the banner, then possibly a layout jump. And that is exactly the visitor who matters most for ad campaigns.

Why are many cookie banners so slow?

A cookie banner is often slow because it loads more than it needs. It really only needs to do a few things: show text, offer two or three buttons, save the decision, and pass it to Google and other services. Many solutions are built as universal platforms that aim to cover every language, legal jurisdiction, and hundreds of services. This versatility costs loading time, even if your site only needs a fraction of it.

• Many files: script, configuration, stylesheet, font and logo are each a separate request.
• Third-party servers: every new domain needs its own connection setup before the first file arrives.
• Language files and vendor lists: long descriptions of every service are loaded, even though hardly anyone opens the details.
• Blocking script in the head: if the script sits synchronously in the head, the browser waits before building the page.
• No reserved space: if the banner pushes itself into the page flow later, the content jumps down.

Each of these points is small on its own. Together, they create a chain where one file waits for the next. On mobile networks, it is not just the size in kilobytes that matters, but the number of requests and connections, as each one adds waiting time.

→ Cookie banner with Consent Mode v2: compliant, with no monthly licence

What the banner does to LCP, INP, and CLS

A slow cookie banner directly worsens Core Web Vitals, the three metrics Google uses to assess page loading speed, responsiveness, and stability. Largest Contentful Paint (LCP) measures when the largest visible element in the first viewport appears. A good score is up to 2.5 seconds. On mobile devices, the cookie banner is often this largest element itself, as its text block fills a large part of the screen. If it appears late, the LCP score is poor, no matter how fast the rest of the page is.

Interaction to Next Paint (INP) replaced the earlier metric First Input Delay (FID) on 12 March 2024 and measures how quickly the page responds to clicks. A good score is up to 200 milliseconds. There are two critical moments with a banner: while it loads, its script occupies the browser’s main thread. And after a click on ‘Accept all’, many tags often start at the same time. If the page then responds with a noticeable delay, INP suffers.

Cumulative Layout Shift (CLS) measures how much the content jumps around while loading. A good score is up to 0.1. A banner that sits over the page as a fixed layer shifts nothing. A banner inserted into the page flow at the top, however, pushes everything down. Anyone who was about to tap a link then hits something else. Moments like this are annoying and make visitors leave the page sooner.

How do you measure cookie banner performance?

The best way to measure cookie banner performance is to load the page the way a new visitor would. For a first assessment you do not need any special tools: the Chrome browser and PageSpeed Insights are enough. What matters are the conditions: no saved consent, no cache and a connection similar to a phone on the go.

• Open PageSpeed Insights in mobile view and note LCP, INP, and CLS. The hints about third-party code and blocking resources often name the banner directly.
• Open Chrome DevTools in a private window, disable the cache in the Network tab, and set throttling to Slow 4G.
• Reload the page and filter by the banner provider's domain. Count the files and add up the transferred kilobytes.
• Start a recording in the Performance tab and see when the banner becomes visible.
• Repeat each measurement several times and use the median, because individual runs vary a lot.

Make sure browser extensions such as ad blockers are disabled in the private window, otherwise requests are missing and the result looks better than reality. The field data in PageSpeed Insights comes from real Chrome users over the last 28 days, so it reacts to changes with a delay. The lab data below it shows straight away whether a change has had an effect.

→ Setting up Google Consent Mode v2 correctly: no warning in Tag Assistant

What a measurement on an empty test page shows

An empty test page shows how fast a cookie banner is on its own. This means a page on which nothing loads except the banner, so nothing else affects the result. Trackum measured banners under fixed conditions: empty test page, mobile emulation, Slow 4G throttling, median of 7 runs. Trackum’s own lean banner was visible after 0.4 seconds. Banners from well-known providers appeared after 1.3 to 4.3 seconds and loaded 7 to 15 files totalling 150 to 210 KB.

On a real website the figures look different, because images, fonts and scripts compete for the same bandwidth. The direction stays the same, though: the fewer files and third-party servers a banner needs, the sooner it appears on screen and the less it slows down the rest of the page.

Real-world example: a joinery firm with a contact form

A joinery firm advertises fitted wardrobes with Google Ads. The website runs on WordPress, the images are compressed and the theme is lean. Even so, PageSpeed Insights shows a poor LCP score on mobile. The Network tab shows why: the banner loads a good dozen files from two third-party servers, including translations for languages the site does not even use. Only then does the notice text appear, and on a phone it is the largest element.

Simply loading the banner later would not solve this. The default value for Google Consent Mode v2, the interface through which Google tags learn the visitor’s choice, must be set before the first tag fires. Otherwise data is sent without consent. The solution is a banner that is light from the start. After the switch to a lean banner, it appears on screen sooner, and the contact form is still measured correctly with and without consent.

How to recognise a lean cookie banner

• A single file of a few kilobytes instead of a chain of follow-up requests.
• Nothing loaded from third-party servers for texts, fonts or lists.
• Only the languages your site actually needs.
• A fixed-position layer that does not shift any content.
• Consent Mode v2 built in directly, without an additional script.
• ‘Reject all’ with equal prominence next to ‘Accept all’ on the first layer.

A lean cookie banner is not a cut-down banner. It still has to ask for consent properly, store it, prove it and pass it on to Google and other services. It just does so without detours. When you assess a provider, load a test page with only that provider’s banner and measure it yourself instead of relying on advertising claims.

Improve loading speed without jeopardising consent

The Trackum banner is a single 6.6 KB file, loads nothing else, works in German and English, includes Consent Mode v2 and shows ‘Reject all’ with equal prominence on the first layer. Consent records are stored in the EU without an IP address. The banner costs a one-off €50 plus €4.90 per month and is already included in the subscription at €19 per month. All prices plus VAT.

If you first want to know where your site stands, Trackum’s free check tests it in a real browser, shows the banner, the consent and the tags that fire, and gives a fixed price for each finding. It takes about two minutes and needs no sign-up.