Autoptimize minor update and beyond

I just released an update to Autoptimize, bumping the version to 1.9.2. Main new features;

  • New: support for alternative cache-directory and file-prefix as requested by a.o. Jassi Bacha, Cluster666 and Baris Unver.
  • Improvement: hard-exclude all linked-data json objects (script type=application/ld+json)
  • Improvement: several filters added to the API, e.g. to alter optimized HTML, CSS or JS
  • Some bugfixes
  • Swedish translations updated & Ukrainian added, courtesy of Zanatoly of SebWeo.com

I’m already thinking about version 2.0 (which should fix the 2 big issues some people face; exploding cache size due to page-specific inline code & the rare but nasty white screen of death due to CSS minification issues) and about some powerful new features that could extend Autoptimize for professionals and power-users in need of something more. 2015 is going to be great, hope you guys & girls will be part of that!

Anyway, enjoy the end-of-year festivities and above all, have fun & share some of the happiness!

 

6 thoughts on “Autoptimize minor update and beyond

      1. Dirk

        Hi Frank, thank you for your help! However, the first link is the (cached) result of your plugin. Being a rookie, I don’t know where to find the appropiate css within. Do I have to turn it off first? Cheers, Dirk

      2. frank Post author

        That link was there just as a referral to the google pagespeed insight remark. You should really have a look at the parts about “inline” and “inline & deferred” CSS in the FAQ, those are the two approaches that can fix the “render blocking CSS”-remark.

        frank

  1. Rudra

    Hi Frank,

    A belated Merry Christmas to you and a Happy New Year in Advance ;) Yes Autoptimize is striking the right chords as far as I am concerned. No issues when I updated to 1.9.2. Its a really nice plugin.
    And As Mr.Dirk said, google’s pagespeed tells me the same story… But the best part is… I don’t give it a damn anymore because page load time has improved greatly for me with autoptimize… below the one second mark…
    Also I would like to mention here.. google has got a pagespeed module for apache and nginx… and many a times I have deployed it in conjunction with PSOL libraries and it works beautifully…. and whatever optimization, PSOL brings in “with respect to” html, js and css…. autoptimize does the same… ngx_pagespeed and PSOL fail to remove the querry strings…. but autoptimize takes care of that as well…. so that way I have found autooptimize to be far better…

    Reply
    1. frank Post author

      You’re correct that Autoptimize does some of the things mod_pagespeed does, but one of the truely great things about mod_pagespeed is that it can automagically decide what CSS is needed for the above-the-fold and that it only injects that in the HTML, differentiating between user agents and using javascript to report back to improve.

      I’m really happy you prefer to focus on real-live page speed instead of just limiting your performance improvements to getting a good PSI-result, which is but one indication of good practices being followed. Esp. deferring CSS is not trivial (see FAQ & this blogpost).

      Have a nice end-of-year,
      frank

      Reply

Leave a Reply

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