Skip to main content

Cookiebot and page speed insights


1 comment

  • Permanently deleted user

    Hi Luca, 
    Thank you for your patience and for reaching out to Cookiebot support. 

    It's worth understanding the difference between Cookiebot with AUTO and MANUAL blocking mode!

    What if you select auto-blocking mode?

    • Most of the scripts on your domain that set non-essential cookies will be blocked/delayed by the Cookiebot script to make sure the domain is GDPR compliant.
    • Consequently, some parts of your domain will not be visible until consent is granted.
    • This is expected behavior.


    What if you select manual-blocking mode?

    • No script will be blocked that set non-essential cookies until you mark them up properly and manually.
    • Since nothing is being blocked automatically by the Cookiebot script, the domain contents/speed will not be affected at all - all elements of the domain will be visible as expected. Furthermore, here you have a great amount of freedom, you decide what scripts/iframe will be blocked until relevant consent is given. 


    Due to the nature of the auto-blocking functionality, loading speeds will always be affected to some extent. The cause of extended loading times is due to how the automatic cookie-blocking function works. As the page loads, elements are compared to a list compiled during the latest scan of the domain (configuration.js).

    If a match is found, the element is modified to prevent it from executing and setting tracking without the end user's consent.
    Do note, however, that if a user submits consent for all cookies, the auto-blocking function will become dormant, causing no more delays.

    To mitigate these delays, there are a few things that might speed things up though:

    • Bundle scripts requiring the same consent level in a single .js file
      This reduces the number of scripts that needs to be checked and processed.
    • Use Google Tag Manager for as many scripts as possible
      The content set by Google Tag Manager is simply not present on the page before consent is given, speeding loading times up drastically.
    • Pre-load scripts
      This fetches the resource so it can load (and execute) faster. Be aware though, that this exposes your visitor's IP address to the third party that the resource is fetched from.

    If these options do not reduce the delay to a satisfactory extent, you may also consider using the manual implementation, which causes absolutely no delays but does require that you mark up scripts in order for Cookiebot to prevent them from executing prior consent.

    Here is a guide that describes how to set this up:


    Feel free to return in case of questions/issues by creating a support ticket. Thank you :) 



Please sign in to leave a comment.