Quick KeyCDN’s Cache Enabler test

cache enablerCache Enabler – WordPress Cache is a new page caching kid on the WordPress plugin block by the Switzerland-based KeyCDN. It’s based in part on Cachify (which has a strong user-base in Germany) but seems less complex/ flexible. What makes it unique though, is it that it allows one to serve pages with WEBP images (which are not supported by Safari, MS IE/ Edge or Firefox) instead of JPEG’s to browsers that support WEBP. To be able to do that, you’ll need to also install Optimus, an image optimization plugin that plugs into a freemium service by KeyCDN (you’ll need a premium account to convert to WEBP though).

I did some tests with Cache Enabler and it works great together with Autoptimize out of the box, especially after the latest release (1.1.0) which also hooks into AO’s autoptimize_action_cachepurged action to clear Cache Enabler’s cache if AO’s get purged (to avoid having pages in cache the refer to deleted autoptimized CSS/ JS-files).

Just not sure I agree with this text on the plugin’s settings page;

Avoid […] concatenation of your assets to benefit from parallelism of HTTP/2.

because based on previous tests by smarter people than me concatenation of assets can still make (a lot of) sense, even when on HTTP/2 :-)

11 thoughts on “Quick KeyCDN’s Cache Enabler test

  1. Matthew

    “I recommend you read these two posts: https://brianjackson.io/speed-up-wordpress/ https://www.keycdn.com/blog/speed-up-wordpress/
    There are some great plugins like Cache Enabler and Gonzalez which I bet you haven’t tried. Gonzalez actually lets you disable scripts on a page/post level basis. Example, Contact Form 7 loads its script on every page of your site by default. With this plugin you can with one click, only let it load on your contact page. On all my sites I have been able to decrease HTTP requests on homepage by at least 5 or more. On an Avada install I decreased homepage by 11 requests! Definitely one of those hidden gem plugins.”

    Reply
  2. LQ2'

    Confirmed as working on shared hosting.

    And you should expand CDN support for other static assets, with the option to rewrite root-relative URLs. AO doesn’t work with two of CDN plugins I use: KeyCDN’s CDN Enabler and CDN Linker. (They are dedicated to CDN and supports root-relative URLs, and works nicely with other minifying plugins.)

    Reply
      1. LQ2'

        Both of them interferes with JS minification of AO.

        CDN Enabler causes a few “Class not defined” errors in aggregated JS in the footer. And CDN Linker makes JS minification fail to work.

        Of course, when I use AO alone (with its current CDN support), those errors don’t happen.

      2. frank Post author

        OK. Now does this also happen if you enter the same CDN in AO and one of those two other plugins?

      3. frank Post author

        I’ll have a look one of these days to see if I can reproduce and possibly solve (or pass on to the KeyCDN-guys).

      4. frank Post author

        well, it turned out to be this day and can’t reproduce this with keycdn’s cdn enabler. do you have a non-production site or can you set one up somewhere with a demo of the problem?

  3. Ramesh

    FYI, I use the same configuration. Autoptimize + CDN Enabler (+ Cache Enabler). Been using this combo for over a month. Absolutely no problems here.

    Reply
    1. Ramesh

      Would like to add some info here. I cleared the cache, loaded the page and ran Dev. Tools.

      Found this entry near Autoptimize JS URL:

      JQMIGRATE: Migrate is installed, version 1.4.1

      Don’t know if that counts as an error. (it was shown in the list of errors)..thought I’d just post it. However, web page renders just fine without any errors.

      It it’s trivial, pls ignore my reply..

      Reply
      1. frank Post author

        JQMIGRATE: Migrate is installed, version 1.4.1

        is not an error, nor a warning or notice, but a console.log message from jquery-migrate to confirm it has been loaded. you’ll also see this when AO is not active :)

Leave a Reply

Your email address will not be published. Required fields are marked *