At the moment our Lighthouse score fails to score HTTPS properly, the reason is that we are using a server side version of Lighthouse called Moonlight that has a bug on the HTTPS scoring.
We are working with the Lighthouse team to solve it soon.
@juliantoledo can you assign this to me? I'm working on updating server-side version. Hopefully it'll fix the issue.
Sure @x1ddos, thank you!
It feels like an issue with headless chrome after all.
I posted a question to headless-dev: https://groups.google.com/a/chromium.org/d/topic/headless-dev/RqxZAsYra0Y/discussion
See: https://bugs.chromium.org/p/chromium/issues/detail?id=609394 for the underlying cause.
@abdonrd The underlying issue has been finally resolved a few days ago. I will pull in the changes and see whether it fixes this bug.
Will update this thread soon.
Nice! Thanks @x1ddos!
Good news, https://airhorner.com/ now scores 97/100 on moonlight and has passes HTTPS checks:
@x1ddos Great!!! I will update our server.
@juliantoledo I'll start the OSS process for moonlight.
@x1ddos Thank you for your work on moonlight!
Deployed your new version to our server, it will take about 1 hour to score all PWAs again.
Yay! Thanks @juliantoledo!
Why the differences in Gulliver and Lighthouse extension?
Lighthouse extension: 97
@abdonrd we use a version of Lighthouse built on Headless Chromium which enables it to run as a server app, for that reason our Lighthouse score and report may deviate from the standard Lighthouse Chrome extension. We are trying to get as close as possible, the major issue we had was the HTTPS detection, but we still need to look into other broken signals.
Please file bugs for any differences you find.