Lofesa commented on issue #1697: URL: https://github.com/apache/incubator-pagespeed-ngx/issues/1697#issuecomment-659298602
Well... you have allmost 2 big things to look in it: The site has headers to preload some things, so when the html is rewrited by pagespeed you have 2 diferent files with the same content, 1 loaded by the header and other loaded by the html code. These preload headers can come from Cloudflare.  When the 2 files are the same, is loaded only 1 time but in chrome dev tools network tab in the initiator column you can see is loaded by "other"  The other thing to look is Cloudflare. Cloudflare is a proxy-cache approach to do CDN work. This mean that the only User Agent that hit the real server is the UA used by Cloudflare, so some optimizations from pagespeed are missed because it are UA dependent. You need to configure Cloudflare in a way that the real UA from the final user hit the real server and headers from the real server go to the final user. For example, in the html request (hhtps://winterco.org) pagespeed set a cache-control header max-age=0, no-cache, this header forbid to store the html in any cache, why? cause the html can be, or not, rewrited by pagespeed. As a first step to make it work, you can put Cloudflare in by-pass mode, so the request from final users can to to the real server, once you got the server with pagespeed working well, the you enable Clodflare and face the issues that introduces. If I remember, Cloudflare can be set to respect original headers. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
