Small experiment; Autoptimize with page cache

So I integrated a page cache (based on KeyCDN Cache Enabler) in Autoptimize, just to see how easy (or difficult) it would be. Turns out it was pretty easy, mostly because Cache Enabler (based on Cachify, which was very popular in Germany until the developer abandoned it) is well-written, simple and efficient. :-)

No plans to release this though. Or do you think I should?

12 thoughts on “Small experiment; Autoptimize with page cache

  1. Alain

    Nice, having an added cache would be nice.

    One nice addition would be a optional shorter cache expiry for specific pages. Often home or a few other pages are updated without new posts…

    Reply
  2. marketaim

    So this would be a complete replacement for Wp-super cache? :D
    Bless you!

    PS I use your html js css minification plugin on most of our wordpress sites to speed them up. Cheers ;)

    Reply
    1. frank Post author

      if that experiment would *ever* be released, it would replace wp super cache for the simpler use cases (which suffice for most). but I currently don’t have plans to release AO with a page cache, it was just for fun (for now) :)

      Reply
  3. Matt

    Please keep AO easy! By adding caching you are going to make it more difficult to use.

    AO is the best plugin to optimize asset files (JS / CSS), and this is one people use it. The solid reputation of the plugin has been created by being the best one on what it does.

    By integrating caching, I’m afraid to see AO the new W3TC or Hummingbird with a ton of options. Hummingbird is a good example as it just integrates caching few weeks ago. It was a good plugin for optimizing assets and some other stuff but since caching is integrating this is a buggy plugin.

    Again, please keep your plugin for why is famous: simple to use and optimize assets.

    Reply
      1. Matt

        Hi Frank,

        Glad to hear you have the same thoughts!

        About the extra optimization, my feeling will be the same.

        Disabling the emoji doesn’t help to speed a website. This option is interesting for a blog website with lot of comments which include emojis. Other than that, it won’t help any websites to be faster.

        Same felling for removing query string, it will help only to be friendly with Google PageSpeed but it won’t help to have a faster website.

      2. frank Post author

        removing emoji’s does result in 1 js-file not being loaded, even if no emoji’s are used, so that one does have a (small but real) performance benefit.

        query-string; agreed, but it’s low-hanging fruit and the “performance score”-crowd love it ;-)

        and async’ing JS can have big perf. benefits, as some of the extra features I’m working on B-)

  4. vibhi

    well Im already using cache enabler so doesn’t matter
    But its the best Plugin for caching No Stupid Setting Like W3total cache and work like charm

    Reply

Leave a Reply

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