Re: [pagespeed-insights-discuss] Re: PageSpeed Insights complains about Nginx+PageSpeed!

[Dave Mankoff]

Howdy folks. This discussion is probably better suited for the mod-pagespeed-discuss list. They'll be able to answer specific questions about settings in the module.

+mod-pagespeed-discuss

-pagespeed-insights-discuss

-dave mankoff

man...@google.com

[Jeff Kaufman]

This doesn't seem to include the earlier discussion?

> --
> You received this message because you are subscribed to the Google Groups
> "mod-pagespeed-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to mod-pagespeed-di...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/mod-pagespeed-discuss/CACsObMMOQDoBjfeW88hmSZSKuQPs_qai117HHEKdGFDTT2C1Lw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Otto van der Schaaf]

-pagespeed-insights-discuss +mod-pagespeed-discuss

Maybe something like the following happens:

When you let mod_pagespeed defer scripts that modify the layout (css, or dom) of a page, "/pagespeed_static/js_defer.XXX.js" gets marked by PSI.

It gets marked, because it performs deferred execution of the original scripts of the page. When these update the layout, it is has become render-blocking.

I think that rewriting the page to not depend on javascript for rendering a (sensible) first view is the only way to eliminate the resulting PSI complaint.

Scripts that are essential for rendering a sensible first view to visitors are probably better not deferred. (e.g. when they transform a desktop site to a mobile version).

mod_pagespeed offers the "data-pagespeed-no-defer" attribute, which you can declare on script tags that you want to exclude.

Otto 

On Sat, Feb 18, 2017 at 9:01 AM Manish Jain <contact.m...@gmail.com> wrote:

Hi KF,

I am also facing the same issue, Did you find any suitable solution for the same.

Thanks.

On Wednesday, 2 July 2014 07:12:26 UTC+5:30, KF wrote:

Hi guys,

I'm optimizing a website using Nginx+Pagespeed and I use the defer_javascript feature. When I run the site through PageSpeed it complains that the site needs to Eliminate render-blocking JavaScript and CSS in above-the-fold content with the file /pagespeed_static/js_defer.eX_CQDtaZA.js. Funny enough, this is the file autogenerated by the PageSpeed nginx plugin. How would I go about fixing this? I can't find an option to make the auto-generated JS file a deferred or async load? 

The score on my client's website used to be 90+ on both mobile and web. Now with the new metrics in place, it hovers around 70/85. The site: www . rksv . in

--
You received this message because you are subscribed to the Google Groups "pagespeed-insights-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-insights-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-insights-discuss/2288c1a8-b52c-40c5-a9f8-ea6c25d1ff7d%40googlegroups.com.