Lighthouse report says my start_url isnt cached

621 views Asked by At

Having run a Lighthouse report on my budding PWA, the report tells me that:

User will not be prompted to Install the Web App Failures:
Manifest start_url is not cached by a Service Worker.

But it is! I can SEE it in the cache in the "Application" tab on Chrome's F12 tools

enter image description here

I can confirm that the entry in the manifest.json is correct too as the "App Manifest" area in F12 tools shows this

enter image description here

I have tried changing it to work with just a basic HTML only page and get the same issue in the report. I have also tried changing the URL to just / but no change in the Lighthouse report.

What am I doing wrong?

1

There are 1 answers

1
Jimbo On BEST ANSWER

This was due to a "buggy" Lighthouse. Its being constantly updated and improved and no longer reports my start_url as being problematic.

Another issue I came across that was driving me mental was Lighthouse reporting that the site was using HTTP/1.1 (with no compression) when various online resources were showing me it was using HTTP/2 (with compression) (IIS 10 automatically serves HTTP/2 if client supports it) It turns out that my antivirus was messing with HTTPS traffic - soon as I turned off HTTPS threat detection, Lighthouse was reporting HTTP/2 with compression.

enter image description here