-
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
Issue with Google Tag Manager <noscript> #9748
Comments
Thanks for filing @alanablett! I'm not able to able to reproduce this issue though, everything passes on my end :/ Anything else about the repro steps might be relevant? Relevant settings or geo required to reproduce perhaps? |
Thanks for your swift response @patrickhulce There should be no difference in terms of geo or set up. I actually just ran the test via the CLI instead, using |
Ah thanks for the screenshots! Do you see the warning message about the interstitial and the question mark in place of the PWA score? Those are trying to indicate that something went wrong while loading the page, not that the site has done something wrong :) In your case with the iframe, it's a root cause of #9562 and fixed in 5.4.0 which was just released. If you update LH, it should go away 👍 Going to close for now, but if latest LH doesn't fix the issue, feel free to chime back in :) |
I can confirm that updating to 5.4.0 fixed the "issue". Many thanks for your help @patrickhulce |
Provide the steps to reproduce
Run LH on https://wd40.ca/
What is the current behavior?
Lighthouse reports PWA Issues
What is the expected behavior?
Lighthouse does not report those issues
Resolution
It seems that the behaviour is related to the existence of the google tag manager
<noscript><iframe>
element on the page. Upon removing that element we see that both of the errors reported below disappear.Environment Information
The text was updated successfully, but these errors were encountered: