Just a guess: maybe Chrome by default uses Google’s DNS servers, which themselves act as a man in the middle between the server’s hosted pages and the client’s http requests, and compresses it there before returning the data to you
Just a guess: maybe Chrome by default uses Google’s DNS servers, which themselves act as a man in the middle between the server’s hosted pages and the client’s http requests, and compresses it there before returning the data to you