UTM Tracking addon causing lighthouse error

  • When I enable the UTM Tracking addon and running a Lighthouse audit, I’ve got “start_url does not respond with a 200 when offline The start_url did respond, but not via a service worker.” error. I tested with and without W3TC enabled.

    Further examining the issue, I noticed the error message is gone if I visit my website’s URL with the: ?utm_source=superpwa query string at the end. Is this how it should work? I’m testing in localhost SSL environment from browser.

    Enabling W3TC causing a whole new issue: ?utm_source=superpwa query string not added at the end of the installed PWA in desktop Chrome.

    • This topic was modified 4 years, 10 months ago by DJviolin.
    • This topic was modified 4 years, 10 months ago by DJviolin.
    • This topic was modified 4 years, 10 months ago by DJviolin.
    • This topic was modified 4 years, 10 months ago by DJviolin.
    • This topic was modified 4 years, 10 months ago by DJviolin.
Viewing 1 replies (of 1 total)
  • Thread Starter DJviolin

    (@djviolin)

    The last issue seems resolved, ?utm_source=superpwa query string appears if I open the PWA from Chrome’s Applications tab.

Viewing 1 replies (of 1 total)
  • The topic ‘UTM Tracking addon causing lighthouse error’ is closed to new replies.

Tags