You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 21, 2023. It is now read-only.
See
http://serverfault.com/questions/585419/mod-pagespeed-own-js-and-css-render-bloc
king
The PSI report
http://developers.google.com/speed/pagespeed/insights/?url=pacifika.ru&tab=mobil
e indicates that http://pacifika.ru/mod_pagespeed_static/js_defer.IRaJtkfeqL.js
blocks onload. We should consider loading the defer_js helper script on a
timeout triggered from requestAnimationFrame, like we do with the non-critical
css.
Original issue reported on code.google.com by jmara...@google.com on 4 Oct 2014 at 2:13
The text was updated successfully, but these errors were encountered:
This is affecting me too. Without pagespeed my JS scripts are being loaded with the "async" attribute and the pagespeed insights analysis does not complain. When I run the tool against my page with pagespeed enabled, it get the message:
If your site is already using all async scripts, I'd suggest just turning
the defer_js filter off; it's meant for people who scripts aren't already
async, so it's extemely unlikely to benefit you if you're already all async.
(Perhaps it should notice it itself...).
This is affecting me too. Without pagespeed my JS scripts are being loaded
with the "async" attribute and the pagespeed insights analysis does not
complain. When I run the tool against my page with pagespeed enabled, it
get the message:
Original issue reported on code.google.com by
jmara...@google.com
on 4 Oct 2014 at 2:13The text was updated successfully, but these errors were encountered: