Upcoming: Autoptimize 1.9.x, looking for testers

Hello,

I installed it on my site and it works. However, I didn’t test the Inline and Defer CSS option as it’s too much hassle for a low traffic personal website.

Thanks again for this great plugin!

most options tested and works perfectly as always.
Thank you for developing one of the most useful wordpress plugin <3

i found 1 tiny tiny problem and its about the above fold css textarea, when you go in to autoptimize option (if advanced option is open) above fold css textarea is not shown until you hide and then show advanced option…

OK, I’ll fix it. Do take into account that that box should (and will, after fixing) only be visible when “inline and defer” is selected ??

Hamed.T; this should be solved in the latest test-build.

just great

Hi, i’ve installed 1.9 and it’s really slowed down my site, i’ve the following config.
wordpress 3.9, apache 2.2, mod_pagespeed, memcached
In newrelic, it indicates that the delay is in JSMin::min 7.9s
https://www.shopdemo.cubecreative.ie
i’m happy to pm you the user credentials if needed.

Hi qvrb;
JSmin (and Cssmin) is pretty intensive, so Autoptimize tries to avoid having to do that wherever possible.

There are two important things in that context;
* have a page cache mechanism (e.g. a plugin as WP Super Cache or a caching reverse proxy such as Varnish), in which case Autoptimize only has to aggregate & minify once.
* check if Autoptimize can re-use previously cached code, by making sure that all code that contains unique strings is excluded from optimization. In your case it seems the newrelic-js-code contains unique strings, so I would add “NREUM” to the comma-seperated JS-exclusion-list.

Hope this helps,
frank

Frank,
I have added NREUM to the excluded list, enabled varnish (i did have varnish in the equation previously, and i’m fairly sure my vcl config is pretty solid), looking at new relic, the delay is in Jsmin:Action, and it looks like this calls is taking ~6.5s

Well, above actions will not make JSMin work faster (there’s no magic there), but will rather avoid it is executed on every page request. As you can see in this webpagetest.org test, once cached (page cache in Varnish + autoptimize’s cached jss/css-files) your site indeed is pretty fast.