pagespeed on; pagespeed RewriteLevel CoreFilters; pagespeed FileCachePath /var/ngx_pagespeed_cache; pagespeed FetchHttps enable,allow_self_signed,allow_unknown_certificate_aut$ pagespeed ImplicitCacheTtlMs 31536000000;
--
You received this message because you are subscribed to the Google Groups "ngx-pagespeed-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ngx-pagespeed-discuss+unsub...@googlegroups.com.
Visit this group at https://groups.google.com/group/ngx-pagespeed-discuss.
For more options, visit https://groups.google.com/d/optout.
--
Kind of has me wondering though about the fact that misconfiguration, which i suppose was what i was doing can have adverse effects on speed rather than a sort of mechanism which recognizes that misconfiguration and cancels it out.
--
I have used and will probably use those you mentioned other than lazyload, as masonry on my site doesn't work well with lazyload. i'd categorize lazyload as an 'unsafe' filter for that reason. definitely not something i'd look forward to seeing in the core
--