There’s any chance to do any of those?
Why exclude CSS you may ask. Well, some plugins include the css files only on single or homepage for example, this will generate 2 separate and quite large (in some cases) combined&minified files which is pretty bad.
PS. Awesome plugin by the way, I was using BWP minify before.
well, 1.6.6 (eta 2nd half of september) should come with support for “do not autoptimize” comment tags, like this;
this should allow you to exclude whatever CSS & JS you want?
Thank you for your reply.
I’ll add CSS-exclusion (much like it works for JS) in version 1.7.0 (eta somewhere in Q4). Removing CDN & YUI from admin will give me some space for the CSS exclusion input field.
The “do not autoptimize” comment tags will be a valuable improvement, because they will make it possible to greatly reduce the number of cached files where inline js or css code changes from page-to-page. For example, I have a site that has about 5,000 content pages. Each of those pages has a single line of inline js code that is different from page-to-page, resulting in the creation of about 5,000 unique js files in the cache. Masking that single line with <!– noptimize –> … <!– /noptimize –> tags will make it possible for all those content pages to share a single js file. Not only will that greatly reduce the number of files cached on the server, but also will reduce visitor webpage loading times after any first page has been loaded.
I’m pushing a “beta”-version of 1.6.6 out (download here), which has noptimize-support.
A simple example of JS being excluded;
<!--noptimize--><script>alert('this will not get autoptimized');</script><!--/noptimize-->
Looking forward to your feedback!
Did you have the chance to test this admintiger?
fyi: up until this morning the 1.6.6 beta-version contained a bug where multiple noptimize-blocks were considered as one big block, but that was solved with a new commit in trunk.
Looking forward to your feedback! 🙂
I have a good news for you Futtta. Autoptimize 1.6.6. along with WP-Minify gives me a Google page speed score of 100/100.
Great Rajasekharan! the <!–noptimize–><!–/noptimize–>-code is supposed to be in the raw HTML, not in the admin-screen (where exclusion is based on -part of- a filename).
Wow. Thanks for the lightning speed reply. As we talked about a theme update here, there came one update, Graphene 1.9.1 to 1.9.2.
well exclusions can be tricky, requiring trial and error. sometimes “look for scripts only in head” is the easier solution, maybe you could try that?
So I think now I may have to forgo either the full page speed score or the autosearch on a 404. However, I would love to have them both.
I did a quick test with graphene on my testblog (good thing graphene isn’t a “premium” plugin) and got it working.
I would be interested in seeing your pagespeed score for wp-minify standalone, autoptimize standalone and the two combined by the way, would you be willing to test and share that? 🙂