Autoptimize — Плагины для WordPress
Опубликовано: 27.12.2017Installation Instructions
Just install from your WordPress «Plugins > Add New» screen and all will be well. Manual installation is very straightforward as well:
It concatenates all scripts and styles, minifies and compresses them, adds expires headers, caches them, and moves styles to the page head, and scripts (optionally) to the footer. It also minifies the HTML code itself, making your page really lightweight.
Mejora la velocidad de wordpress hasta el limite con autoptimize y wp optimize
But I’m on HTTP/2, so I don’t need Autoptimize?
HTTP/2 is a great step forward for sure, reducing the impact of multiple requests from the same server significantly by using the same connection to perform several concurrent requests. That being said, concatenation of CSS/ JS can still make a lot of sense , as described in this css-tricks.com article and this blogpost from one of the Ebay engineers . The conclusion; configure, test, reconfigure, retest, tweak and look what works best in your context. Maybe it’s just HTTP/2, maybe it’s HTTP/2 + aggregation and minification, maybe it’s HTTP/2 + minification (which AO can do as well).
How to improve Wordpress Page Speed using Autoptimize Plugin (Page Speed Part 4)
Will this work with my blog?
Although Autoptimize comes without any warranties, it will in general work flawlessly if you configure it correctly. See «Troubleshooting» below for info on how to configure in case of problems.Why is jquery.js not optimized
Starting from AO 2.1 WordPress core’s jquery.js is not optimized for the simple reason a lot of popular plugins inject inline JS that is not aggregated either (due to possible cache size issues with unique code in inline JS) which relies on jquery being available, so excluding jquery.js ensures that most sites will work out of the box. If you want optimize jquery as well, you can remove it from the JS optimization exclusion-list (you might have to enable «also aggregate inline JS» as well or switch to «force JS in head»).Why is Autoptimized JS render blocking?
If not «forced in head», Autoptimized JS is not render blocking as it has the «defer» flag added. It is however possible another plugin removes the «defer»-flag. Speed Booster Pack was reported doing this, but the behavior has not been confirmed yet .Why is the autoptimized CSS still called out as render blocking?
With the default Autoptimize configuration the CSS is linked in the head, which is a safe default but has Google PageSpeed Insights complaining. You can look into «inline all CSS» (easy) or «inline and defer CSS» (better) which are explained in this FAQ as well.What is the use of «inline and defer CSS»?
CSS in general should go in the head of the document. Recently a.o. Google started promoting deferring non-essential CSS, while inlining those styles needed to build the page above the fold. This is especially important to render pages as quickly as possible on mobile devices. As from Autoptimize 1.9.0 this is easy; select «inline and defer CSS», paste the block of «above the fold CSS» in the input field (text area) and you’re good to go!