Nazaqat

Please update to the latest version of Cookiebot that we released today, and check if that resolves the issue. If the problem persists, I will escalate the case to our developers for further investigation and resolution.

Thank you Martin.

The theme author did not respond to the question about cookies. Anyhow, this means the scripts in the scripts.min.js are setting non-essential cookies and consequently the Cookiebot auto-blocking mode (currently implemented on the domain in question) blocks the slider functionality (scripts.min.js) until and unless relevant/full consent is given.

There a couple of options in this scenario:

Find the cookies set by the scripts.min.js and update their category to “Necessary” in the Cookiebot manager

OR

You may apply the data-cookieconsent=”ignore” attribute to the scripts.min.js using the instructions https://support.cookiebot.com/hc/en-us/articles/360009063660-Disable-automatic-cookie-blocking-for-a-specific-script

OR

Consider switching to Cookiebot manual blocking mode. 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 parts will not be affected at all – all elements of the domain will be visible as expected. 
• Here you have a great amount of freedom, you decide what scripts/iframe will be blocked until relevant consent is given. 

However, remember to control the non-essential cookies/scripts via manual markup using the instructions Step 4 – Mark up cookie-setting script tags on your website to control cookies

Remember to initiate a fresh scan to see the difference.

Feel free to return if the case is not resolved or you got any questions 🙂

Thank you for the explanation Martin.

Would it be possible for you to provide a script associated with the slider and cookies set by the script (if you are aware of them)?

Hello,

Thank you for contacting Cookiebot support.
According to the latest scan results, Youtube cookies are under control until the relevant consent is given and furthermore, I see the issue marked as “Resolved”.

Has the issue been resolved or please come up with the steps to reproduce the scenario?

Hej Mattheo,

Thank you for reaching out to Cookiebot support.

I have responded to your issue in support ticket 103504 created by Roberto. Thank you.

Hej thomas174,

Thank you for reaching out to Cookiebot.

Generally, the Elementor sets non-essential cookies on the domain, and when the Cookiebot with the auto-blocking mode is active/enabled, it (the auto blocker) blocks the scripts/iframes/sources that set non-essential cookies. Consequently, elements/contents on the domain are not rendered as intended.

Since you have updated the Elementor cookies to essential in the Cookiebot manager, make sure to initiate a fresh scan to see it’s impact on the live domain.
When the scan is complete, clear the domain/browser cache to experience the difference.

Furthermore, Ensure the Cookiebot script(uc.js) with auto blocking mode is NOT manipulated and deferred by Rocket loader or similar Plugin/solutions to avoid unexpected results.
To prevent this from happening add the following under Load JavaScript deferred → Excluded JavaScript Files:
consent(.*).cookiebot.(.*)/(.*).js

<script type=”rocketlazyloadscript” data-rocket-type=”text/javascript” id=”Cookiebot” src=”https://consent.cookiebot.com/uc.js&#8221; data-cbid=”b2f8c2f4-5ec4-47a4-b91f-b01125293a34″ data-blockingmode=”auto” defer></script>

Please note – for the best and fast possible support, always reach out to Cookiebot support directly via https://support.cookiebot.com/hc/en-us/requests/new

Feel free to return if the case is not resolved or you have further questions. Thank you.

Hej andre90,

Thank you for reaching out to Cookiebot.

Since the Cookiebot has not been configured on the domain https://sifaformazione.it/ currently, I’m afraid, it’s challenging to investigate the matter.

Generally, due to the nature of the auto-blocking functionality, loading speeds will always be affected to some extent. The cause of the 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:
1- Bundle scripts requiring the same consent level in a single .js file – This reduces the number of scripts that need to be checked and processed.
2- 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.
3- 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: https://www.cookiebot.com/goto/manual-implementation-guide/

Thank you.