CookieYes? No thanks!

I just reviewed the performance of a customer’s WordPress site. Things got a lot worse he wrote and he assumed Autoptimize (he was a AOPro user) wasn’t working any more and asked me to guide him to fix the issue.

Instead it turns out he installed CookieYes, which adds tons of JS (part of which is render-blocking), taking 3.5s of main thread work and (fasten your seat-belts) which somehow seems to increase DOM size to over 60K elements in this case.

I knew cookie consent solutions can have a performance impact, but this? Thanks but no thanks!

5 thoughts on “CookieYes? No thanks!”

  1. CookieYes, just say no.

    I installed CookieYes to keep my site running for Google. Installation was painful. Support was bad. Performance greatly impacted.

    Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.