Support » Plugin: Autoptimize » Feature Suggested: Remove render blocking CSS/JS

  • I have to said that I’m very satisfied with this plugin. It solved a lot of inconvenient that was giving me a low Page Speed Scores. I suggest to include a feature to move the css and js at the bottom of the page avoiding the page render blocking, since this is the worst part of handle in all themes and plugins integrations. This will give all users of Autoptimize 2-3 point extra on Page Speed at least.

    Cheers Guys

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Frank Goossens

    (@futtta)

    well, by default (except in version 2.0.x) autoptimized JS is loaded non-render blocking (the option “force in head” not being ticked) but js/jquery/jquery.js is excluded from autoptimization (as a lot of inline JS requires jquery and we don’t want to aggregate inline JS for cache-busting inline JS reasons).

    for CSS the option “inline all css” or (better but more difficult) “inline and defer css” does exactly what you want as well, but those -I feel- should not be defaults.

    so yeah, those features are already included I guess 😉

    I suggest to include a feature to move the css and js at the bottom of the page avoiding the page render blocking, since this is the worst part of handle in all themes and plugins integrations.

    Two things to add to Frank’s remarks:

    1.) As Frank alluded to, the majority of WordPress websites have jQuery dependencies. So, most people are going to have to leave jQuery loose in the <head>, uncombined with the rest of a website’s JavaScript. jQuery figures so prominently in all things WordPress that it is a part of WordPress’s core. In most instances a website will have to be built from the ground up with little or no reliance on jQuery in order for jQuery to not have to be a render blocking resource.

    2.) Forcing all CSS to the bottom of the source code will give you better scores on best practices tools like PageSpeed Insights, sure, but doing so will also break your website. It’s important to remember that best practices tools make suggestions… However, if these suggestions are not interpreted correctly they can be counterproductive.

    Because it makes for a superior user experience, Google likes to see progressive rendering, not high scores on PSI achieved by breaking your website in such a way that — by definition — provides a poor user experience.

    Be well,
    AJ

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Feature Suggested: Remove render blocking CSS/JS’ is closed to new replies.