• Installation is complicated. Documentation is confusing. Worst of all, this code is harming my Core Vitals. It’s render blocking and really slowed down my site, causing SEO to drop (a lot). I tried dealing with their support, but it was taking too long and I was getting different answers with each reply. As far as I can tell, the last update is broking. Now they inject the default consent tags from the plugin, so that script runs just before their (slow) script. But, their docs say we’re support to put Google Analytics between those two scripts, which isn’t possible. They also recommend modifying your theme’s source code (header.php) which is a bad idea. I’m in search for a Cookie Consent solution that does NOT harm performance and SEO.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @reekes,

    Greetings from CookieYes!

    We sincerely apologize for the delay in responding to your inquiry and understand your frustration. Your time is valuable, and we regret any inconvenience caused by our delayed support. The delay in our response was primarily due to an unexpected surge in support tickets, which temporarily overwhelmed our resources. Rest assured, we are actively working to streamline our processes and allocate additional resources to ensure that we can respond to your needs promptly.

    As CookieYes proactively blocks scripts before obtaining consent and then appends the banner after the page has loaded, a slight variation in performance may be expected. To help mitigate any potential impact on performance, we recommend prefetching our essential domains listed below:

    1. https://cdn-cookieyes.com
    2. https://directory.cookieyes.com
    3. https://log.cookieyes.com

    For further information on DNS prefetching and its benefits, please refer this documentation. We assure you that we are continually working to improve our script’s performance to provide the best experience possible.

    You might have referred to the wrong documentation while implementing Google consent mode using the option available in the plugin. Please refer to this documentation while using the plugin, and in this case, you shouldn’t add the gtag/GTM script between the other two scripts.

    If you are still facing any issues, please raise a query with your site URL via the support forum, and we will be happy to help you.

    Thread Starter Jim Reekes

    (@reekes)

    NOTE: from your docs:

    Step 3:Ensure the order of the scripts

    Ensure that the scripts are loaded in the following order for proper functionality:

    1. Custom Consent Mode script
    2. gtag / GTM script
    3. CookieYes script

    Maintaining this sequence is essential for the correct operation of the functionality.

    Previously, CookieYes had us adding the Consent Mode script manually. I was able to add it before adding Google Analytics gtag script. That’s how I got the sequence in the required order. Then the new version was released, which broke it. It’s no longer possible for me as far as I can determine (reading all of the docs).

    I don’t control when #1 is executed. Now, with the latest released, I only add #2.

    NOTE: I’m not using Google Tag Manager. I’m using classic Google Analytics gtag.

    If I add the gtag script to head, using standard WordPress API, I cannot control the sequence described by your docs. There is an implicit requirement to use Google Tag Manager with CookieYes. I don’t see how to integrate it otherwise.

    That requirement shows up again when the only way to verify the integration is to debug with Google Tag Manager. For the average person, this is all much. Still, why isn’t the requirement of using Google Tag Manger made more clear? Then the docs are incomplete to setup a new Google Tag Manager.

    Is it even possible for CookieYes to work with out Google Tag Manager. If so, how?

    Even if I go thru all the effort to install Google Tag Manager, which I don’t need because I’m just using basic Google Anlytics, the real problem is how CookieYes is significantly impacting performace. That’s the real problem. This then impacts Core Vitals, and lowers SEO.

    • This reply was modified 7 months, 3 weeks ago by Jim Reekes.
    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @reekes,

    Please read the documentation carefully. There are two methods explained for implementing Google Consent Mode. Please don’t mix them up. If you have already implemented GCM on your site before the latest feature is available in the plugin, you can keep it and shouldn’t worry about the new feature in the plugin.
    However, if you prefer to implement it via the plugin, please follow Method 1 as explained in the documentation. Step 3, which you mentioned in your last response, falls under Method 2.
    Also, you don’t need to have GTM installed. That’s why we have mentioned it as gtag/GTM Script.
    If you are still facing any issues, please raise a query with your site URL via the support forum, as moderators won’t entertain discussing support issues under the review section.

    Thread Starter Jim Reekes

    (@reekes)

    I contacted support on July 9th. As of July 31st I’m still waiting for answers.

    Even if we can get it working, with all the time and effort, I end up with a significant performance impact harming SEO.

    Plugin Support CookieYes Team

    (@cookieyesteam)

    Hi @reekes,

    We have already shared a solution for this issue in our first response. Please give it a try and let us know the status.
    Regarding your support ticket, please share the ticket number so we can check the status.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘cannot recommend’ is closed to new replies.