Render-Blocking JavaScript from Autoptimze

sure; uncheck the “force JS into head” option (that might require some extra config though, as deferring JS can break stuff).

have fun,
frank

https://developers.google.com/speed/pagespeed/insights/?url=http%3A%2F%2Fmosquitonomore.com

only lists http://mosquitonomore.com/?sccss=1&ver=4.4.2 as render blocking actually.

the js/autoptimize file is mentioned in a separate tip;

Minifying http://cdn1.mosquitonomore.com/…mize_9454d458b97e420bf2adb0f7acbf212c.js could save 657B (1% reduction) after compression.

you can find more info on why this is so and how you could fix in this forum topic.

hope this clarifies,
frank

Hi Patrick;
If disabling “force into head” causes problems, you can try excluding just the right JS from optimization to load at least the autoptimized JS late. At that point the excluded JS would at probably be render-blocking, so you would be going in circles really. But once you know which JS (and which plugin) needs JS loaded early, you could look for alternatives for that plugin?

Hope this clarifies,
frank

Where can I find the file which the sequence of the scripts defines? It is the functions.php in theme folder or a other?

It’s not that simple, I’m afraid; your theme and each plugin request WP core to add JS, the full list of all enqueued scripts is kept in a variable of WP at runtime. If you’re into coding, you can print_r the contents of $wp_scripts (if I’m not mistaking) to see what JS has been queued for output.

frank