My view is that a full-screen consent banner pushed at a visitor on arrival costs you more conversion than any ad blocker ever will. The visitor cannot see what the company does until they have answered a question about cookies, and the first screen is where you can least afford to spend their attention.

The banner covers the page because somebody built it that way. None of the laws and regulator texts linked in this post sets a size for the consent request or a moment at which it has to appear. They set what may run before the visitor answers and how the choice has to be offered.

This is not legal advice. It summarises the primary sources linked below. For your own site, talk to a lawyer.

Ten seconds is the budget the research gives you

Jakob Nielsen’s How Long Do Users Stay on Web Pages? (Nielsen Norman Group, 11 September 2011) puts the design implication in one sentence: “To gain several minutes of user attention, you must clearly communicate your value proposition within 10 seconds.”

That reading comes from a Microsoft Research study of page-visit durations across 205,873 web pages and more than two billion dwell times. Time on a page turned out to follow a Weibull distribution, and 99% of the pages showed what the researchers call negative aging: the longer someone has already stayed, the less likely they are to leave. The article’s own summary of the shape is that the first ten seconds are critical, that visitors are still highly likely to leave through the following twenty, and that the curve only flattens after about thirty seconds.

A banner that covers the page spends those seconds on a question about tracking, asked of somebody who does not yet know who you are.

What the law in the EU requires

The legal core is small. Article 5(3) of the ePrivacy Directive permits “the storing of information, or the gaining of access to information already stored” on someone’s device only where that person “has given his or her consent”, or where it is “strictly necessary in order for the provider of an information society service explicitly requested by the subscriber or user to provide the service”. In Austria the same rule is § 165 Abs. 3 TKG 2021, which allows this data to be collected only after active consent given on the basis of clear and comprehensive information. In Germany it is § 25 TDDDG.

For a website in the EU, these points follow from those texts and the guidance on them:

  • Anything non-essential waits for a yes. An analytics or advertising script is not strictly necessary for the service the visitor asked for.
  • What is strictly necessary needs no consent. The Article 29 Working Party’s Opinion 04/2012 is the classic reference for what counts, such as a login session, a shopping cart, load balancing and security.
  • Consent is something the visitor does. The GDPR requires it “by a statement or by a clear affirmative action” (Article 4(11)), and recital 32 says “Silence, pre-ticked boxes or inactivity should not therefore constitute consent.” The EU’s Court of Justice ruled the same on pre-ticked boxes in Planet49 (1 October 2019).
  • Scrolling is not consent. The European Data Protection Board’s Guidelines 05/2020 say “scrolling or swiping through a webpage or similar user activity will not under any circumstances satisfy the requirement of a clear and affirmative action”.
  • Refusing has to be as easy as accepting. That is the position of European regulators, covered below. The GDPR’s own sentence is about taking consent back: “It shall be as easy to withdraw as to give consent” (Article 7(3)).
  • Seeing the page must not depend on a yes. The same EDPB guidelines say that consent collected by a script that blocks the content until the visitor clicks accept, a cookie wall, is not freely given. France and Italy do not treat every wall as unlawful. The French regulator and the Italian regulator both accept one only where the visitor gets a genuine, equivalent alternative without consenting.

Size, position and timing appear in none of these texts. German regulators say in their guidance for digital services that visitors may expect to simply stay inactive when they do not want to consent, and that where a banner blocks access, refusing must not take more clicks than accepting.

Why so many sites still show a page-blocking banner

A banner that blocks the page forces an answer. In a 2020 field experiment with 40 participants, Nouwens and colleagues found that the style of the request, a barrier that blocks the page or a banner that does not, had no effect on what people chose. The non-blocking banner was ignored 3.6 times more often than the barrier, where ignored meant no interaction for at least three seconds before the tab was closed. Removing the reject button from the first page raised consent by 22 to 23 percentage points.

My reading is that a blocking banner collects more answers without changing what people answer, and that the design choice which does move answers towards yes is hiding the refusal.

The second reason is the template. Most sites show the banner through a consent management platform, a tool that arrives with a ready-made design. The Dutch data protection authority says that in practice the default settings of such a tool’s banner often do not meet the GDPR. In my view the banner on many company websites is that template as it arrived, and nobody decided where it sits or when it appears.

Ask after the visitor has done something

Put the consent request at the first point where the visitor has shown they want to be there:

  • They scroll past the first screen.
  • They open a product, a case study or a pricing page.
  • They start filling a form.
  • They move to a second page.

Any of those is a visitor who has oriented themselves, and it is also the moment measurement starts to be worth something. The action only decides when the request appears. The yes still has to come from a button.

Delaying the question rests on one thing you have to build: nothing non-essential runs until the visitor says yes. Build it the other way round, with the tags loading on arrival and the banner collecting a yes afterwards, and the delay stops being a timing choice and becomes tracking without consent.

Moment in the visit What is allowed to run What the visitor sees
Arrival Only what the page needs to render The page
A meaningful action: past the first screen, into a product, into a form, a second page Still nothing non-essential The consent request, accept and reject side by side
The visitor says yes Analytics and marketing tags load The page, and a footer link to change the answer
The visitor says no Still nothing non-essential, and every function keeps working The page, and the same footer link

The last row is the one that gets skipped. A no has to leave the site fully usable, and a footer link that reopens the request makes it as reversible as the yes.

Accept and reject carry the same weight

Regulators have already published what they look at. In the European Data Protection Board’s Cookie Banner Taskforce report of 17 January 2023, “a vast majority of authorities considered that the absence of refuse/reject/not consent options on any layer with a consent button of the cookie consent banner is not in line with the requirements for a valid consent and thus constitutes an infringement” (paragraph 8). On colours and contrast the same report declines to set a general standard and says a “case-by-case verification must be carried out in order to check that the contrast and colours used are not obviously misleading” for users (paragraph 17). The report calls these coordinated positions a minimum threshold that does “not prejudge the analysis that will have to be made by the authorities of each complaint and each website concerned”.

National decisions point the same way:

  • In Germany, the Hanover administrative court ruled on 19 March 2025 (10 A 5385/22) that a banner with an “accept all” option needs a clearly visible “reject all” button on the first layer, as reported by the Lower Saxony data protection authority.
  • In Austria, the data protection authority ordered a broadcaster’s site on 28 October 2024 to offer an equal choice between accepting all cookies and only the necessary ones on the first layer, equal in colour, size, contrast, placement and emphasis. That decision is not yet final.
  • In the Netherlands, the regulator continuously monitors 10,000 Dutch websites and in October 2026 opened investigations into two organisations whose banners still had no directly visible button to refuse.

A yes collected from a banner that steers is worth less than it looks, because whether it was consent at all is arguable, and the measurement built on it inherits that argument. Open your own banner on a phone and see which button your thumb reaches for.

What to keep off the page until the visitor says yes

Moving the request to a later moment touches one piece of your tag setup. The larger job is making the page load nothing non-essential before the answer, which means going through everything the page fetches from other companies, because each fetch hands that company the visitor’s IP address. Besides the device rule quoted above, the GDPR applies to passing a visitor’s data on. A Munich court applied it in its judgment of 20 January 2022 (LG München I, 3 O 17493/20) and awarded a visitor € 100 because a page had passed their IP address to Google by loading Google Fonts without consent.

What loads on arrival What happens before any answer The fix
Fonts served from another company’s servers The visitor’s browser fetches the font there and hands over the IP address, which is the Munich case Keep the font files on your own site. The court noted that Google Fonts can be used without a connection to a Google server
Video, map and social media embeds The embed is fetched from the other company as the page renders. German regulators list maps, videos and social media content among the typical third-party content A placeholder with a button, and the embed loads when the visitor clicks it
A tag manager Loading a tag manager from Google’s servers is itself a request to a third party Load it after the yes
Google Consent Mode in advanced mode Google’s tags load before the visitor chooses and, while consent is denied, send cookieless pings that carry the browser type (user agent), the referrer and a timestamp. Google says it uses the IP address only to derive the country Basic mode, where Google says its tags do not load until the visitor interacts with the banner and no data goes to Google before that
Chat widgets, A/B testing tools, heatmaps and social buttons Where they are served by another company, their scripts load with the page Load them after the yes, or behind a click that says what will load. Share buttons can be plain links

In my view basic mode is the setting that matches “nothing before a yes” in the EU.

Outside the EU

The EU model is consent first. Other places start somewhere else.

Where Starting point What it means for the request
EU, including Austria and Germany Consent before anything not strictly necessary Regulators expect an equal refusal on the first layer. Scrolling and pre-ticked boxes are not consent
UK Consent, with exceptions since 5 February 2026 UK law lets a site store or read data without consent solely to collect statistics for improving its service, or to adapt how it looks, if it tells the visitor and offers a simple, free way to object. Under the regulator’s guidance, advertising still needs consent
US Mostly opt-out, state by state As of August 2026, 20 states had comprehensive privacy laws in effect and 12 require honouring the Global Privacy Control browser signal, by Usercentrics’ count. California’s Attorney General fined Disney $2.75 million on 11 February 2026 over opt-outs that did not apply across its linked services and devices. California wiretap lawsuits over tracking pixels continue, so a pixel-heavy site still carries risk there without consent
Brazil Consent or legitimate interest The data protection authority’s non-binding guide says analytics cookies can rest on legitimate interest in some cases. Where consent is the basis, it recommends a reject-all button on the first layer and no extra prominence for accept
Switzerland Information plus a right to object The federal commissioner’s guidelines (version 1.1, 6 October 2025) expect consent where non-essential cookies are used in ways visitors would not expect or that intrude seriously, and express consent for high-risk profiling

The EU rules may change. Under the Digital Omnibus proposal, the Council agreed its negotiating position on 21 October 2026. It would add six purposes that need no consent, including anonymous, aggregated audience measurement by the site or by a third party on its behalf, require a single-click refusal, and bar asking again for at least four months after a no. At the time of writing the European Parliament has not adopted its position. This is a proposal and its likely direction, and none of it is law.

Common beliefs, checked against the sources

The belief What the sources say
“Even essential cookies need consent.” In the EU, Article 5(3) exempts storage that is strictly necessary for a service the visitor asked for. Remembering the visitor’s consent choice is one of those uses: the Swiss commissioner’s guidelines say it is required so that the banner does not appear each time
“The banner has to appear as soon as the page loads.” None of the texts linked here sets a moment. GDPR recital 32 asks for a request that is clear, concise and not unnecessarily disruptive.
“Delaying the banner breaks analytics.” In the EU, analytics that needs consent does not run before the yes in either setup. Visitors who leave before the request appears are not counted. With a banner on arrival, they would have been counted only if they had said yes first. What the remaining numbers can answer depends mostly on traffic, as in what A/B testing costs in 2026
“A banner on arrival is the safe choice.” The decisions above are about the choice the visitor gets. A banner that blocks the page until the visitor accepts is the case the EDPB guidelines describe as consent that is not freely given

A last belief is that compliance takes a year and a legal team. My view is that this describes a company with many markets and dozens of tools. A marketing site with five tools in one or two markets has the same obligations and far less to go through.

What to do on your own site

Five steps you can take to your developers or your agency:

  1. List what loads before anyone answers. Open the site in a private browser window and click nothing. Ask for the list of every request the page makes and every cookie it sets, split into your own domain and everybody else’s.
  2. Take those entries off the first load. The table above is the checklist.
  3. Remove the tools nobody looks at. Each script you remove is one purpose less to ask about and one line less in the request.
  4. Pick analytics that fit your markets. In France, audience measurement that meets the regulator’s conditions can run without consent, and the regulator says most large analytics products do not qualify. The UK has the statistics exception in the table above. Elsewhere in the EU, assume analytics needs consent unless and until the Digital Omnibus becomes law.
  5. Design the request as part of the page. Show it after a meaningful action, in a form that leaves the page readable, with accept and reject on the same layer at the same size and weight, plain words on each button, and a footer link that reopens it. It is a real interaction element, so how fast it responds counts towards the Core Web Vitals a marketing site is judged on. Store a no and leave the visitor alone. Italy’s regulator says a refusal must be stored and not asked again for at least six months, unless the processing changes materially or the site cannot know a choice was stored.

Step 3 has an end point. In the EU, a site that stores and reads only what is strictly necessary needs no consent request at all. It still owes its visitors a privacy notice.

At Essential Code this is part of the work our Fractional Marketing Engineer service picks up, and you can get in touch if you want a second pair of eyes on what your site loads before anyone answers.

This post first appeared on the Essential Code blog.