jmarantz commented on issue #1790: pagespeed insights screams image optimisation even though all should be good? URL: https://github.com/apache/incubator-pagespeed-mod/issues/1790#issuecomment-412342934 Hi -- quick question and a couple of comments. Do you have another lazy-loader apart from mod_pagespeed running on your site? If so, could you try temporarily disabling your other lazy-loader and instead using ` ModPagespeedEnableFilters` [lazyload_images](https://www.modpagespeed.com/doc/filter-lazyload-images) I'm not saying mod_pagespeed's lazyloader is necessarily better than the other one you have, but I think mod_pagespeed's URL-renaming may not work well with the other lazy-loader. One other thing that can be confusing when bringing up mod_pagespeed for the first time is that its optimizations don't occur instantly. They are initiated the first time a web-page is seen, and are cached server-side. In order to see the fully optimized view you may have to visit the page and refresh a few times to warm up the server-side cache. This is confusing for two reasons: - if something is broken due to changed URLs interacting with JS on your page (e.g. another lazyload library) it may look like it works initially, and then fails later once the optimization is cached - if you are looking for optimized results you may not see them immediately and think you did something wrong, when that's the way it's supposed to work. By the way, the addition of Varnish downstream can also confuse things, but once you get everything configured properly it's a great combination. Please read https://www.modpagespeed.com/doc/downstream-caching for more details. In general, in the release you have, we believe the image optimization in all its forms should be working properly. So all of the disables and forbids you indicated above should not be necessary. Finally, if all you want to do is make your images smaller, you might want to consider mod_pagespeed's OptimizeForBandwith mode. See https://www.modpagespeed.com/doc/optimize-for-bandwidth for details.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
