Yes, sure. I will cooperate with you, and I have a good news for you!
Here is the test score of WP-Minify standalone with JS minified by it:
Page Speed Score: 99/100
Remove query strings from static resources
Resources with a “?” in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:
http://example.com/blog/wp-content/plugins/wp-minify/min/?f=wp-content/themes/graphene/style.css,wp-content/plugins/wp-pagenavi/pagenavi-css.css&b=blog&m=1379134744
Here is the test score of Autoptimize standalone with JS minified by it:
Page Speed Score: 100/100 (Autoptimize alone fetches this good score and that is the good news.)
So I don’t need WP-Minify anymore! Now only I have that issue of autosearch in 404.
Feel free to revert if I can of any further help.
Ah, but the solution for the autosearch in 404 is in my previous answer (éxclude window.location.replace and jquery.js) 🙂
Sorry, I messed up a bit, didn’t empty the cache.
Here are the standalone results for Autoptimize with Javascript minified by it:
Page Speed Score: 98/100
Defer parsing of JavaScript
95.8KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.
http://example.com/blog/wp-content/cache/autoptimize/autoptimize_b452c5faaea19a4171c47af758897faf.php (95.6KiB)
http://example.com/ (215B of inline JavaScript)
Here are the standalone results for WP-Minify with Javascript minified by it:
Page Speed Score: 99/100
▾Remove query strings from static resources
Resources with a “?” in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:
http://example.com/blog/wp-content/plugins/wp-minify/min/?f=wp-content/themes/graphene/style.css&b=blog&m=1379134744
Now, with Autoptimize standalone and using the solution that you said above:
Page Speed Score: 96/100
▾ Optimize the order of styles and scripts
The following inline script blocks were found in http://example.com/ between an external CSS file and another resource. To allow parallel downloading, move the inline script before the external CSS file, or after the next resource.
Inline script block #2
▾Defer parsing of JavaScript
95.8KiB of JavaScript is parsed during initial page load. Defer parsing JavaScript to reduce blocking of page rendering.
http://example.com/blog/wp-includes/js/jquery/jquery.js?ver=1.10.2 (83.7KiB)
http://example.com/blog/wp-content/cache/autoptimize/autoptimize_73888be765e20d6744365c693bfa40ab.php (11.9KiB)
http://example.com/ (215B of inline JavaScript)
▾Remove query strings from static resources
Resources with a “?” in the URL are not cached by some proxy caching servers. Remove the query string and encode the parameters into the URL for the following resources:
http://example.com/blog/wp-includes/js/jquery/jquery.js?ver=1.10.2
regarding the 404+autosearch; the way the theme people coded it, you need jquery loaded before the window.location.replace-part. there’s no simple solution I can think of that will allow you a perfect pagescore (which is very exceptional by the way, congrats) and a working 404+autosearch (unless the theme-guys would alter their approach for one that didn’t involve jquery or even javascript).
I think I can sacrifice autosearch for a good page speed score.
Meanwhile, it was a nice experience working with you Frank. Thank you so much.
Nice experience indeed, thanks for the feedback!
excluding css is coming in 1.7.0 and I could use some testing-help there. 🙂
