-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable text compression ON, but reported OFF #9963
Comments
Hi @dommm063 |
OK, but it seems to me that last version is best version, no ? |
I'm not able to reproduce this with 5.6.0 either. To @Lofesa's point, how are you running 5.6.0 in Chrome 78 DevTools? That's not the Lighthouse version that ships with 78... |
Hi @dommm063 |
I've seen the same issues with Lighthouse when testing our sites with Lighthouse CLI v5.6.0. Just to make sure our CDN is not doing something strange, I tested also using google.se and Lighthouse was reporting two static assets for the rule "Enable text compression". Loaded one of those files and checked the network tab in Chrome and the response had Content-Encoding: gzip. How I executed LH (Node v12.13.0, Chrome 78.0.3904.108): |
Hi @patrickhulce |
I'm running 80.0.3987.116 (Official Build) (64-bit) on Windows 10 and have experienced similar issues. I'm finding Lighthouse seems to be randomly reporting that Text Compression needs enabling on sites I've tested. By randomly I mean that I can run it a few times on the exact same page within a few minutes and it will sometimes report it needs enabling and sometimes not - there's no discernible pattern. I can run it 5 times and it will report 3 times it's off and 2 times it is OK! All with the same URL. I actually tested the https://www.roadtrippin.fr/ site mention in this report and found Lighthouse did report Text Compression was off the first time, but on the second time, then off the third time. See screenshot below showing it off: On all the sites I've tested where it warns me that Text Compression is off then I know that GZip is enabled. I've confirmed this with multiple other tools and checked the headers. So I believe the issue is with Lighthouse, though I appreciate it's not easy to reproduce on demand. Intermittent issues are difficult to debug, I know. Is there any more information that would be useful to provide? |
Thanks for chiming in @DanDiplo! Is it possible there is some intermediate proxy/anti-virus/extension running that could be mutating results? I'm still 0/12 on getting that URL to report a failure for "Enable text compression". In the past when we've seen reports of this sort of thing happening it ended up being something that injects itself into Chrome and messes with results (the most unexpected one was a random HP Printer driver that for some reason decided it needed to hook into the Chrome network stack... 🤦♂) |
Hi @patrickhulce So I tested Chrome in incognito mode (with no extensions) and still had same intermittent results. However, I then tried disabling the virus checker they have installed on my work PC, which is ESET Endpoint Security 7.1.2053 and this fixed the issue! I also noticed my page speed scores increased dramatically, too. I never realised how much it was interfering with network traffic, which isn't great! I will do more testing, but I definitely looks like this is the culprit. Thanks for the suggestion and for this very useful tool! |
Thanks for the extra info @DanDiplo glad you found it! Those pesky anti-virus tools always stick their noses in everything 😆 |
It seems there's no reproducible issue here. Please open a new issue with a URL if you run into a similar problem. |
Provide the steps to reproduce
Report says that compression is not active on this site for php, css, js files.
I checked with my provider and other tools, GZIP is enable (with htaccess file).
Environment Information
Related issues
The text was updated successfully, but these errors were encountered: