Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    Hi Curtis,

    Thanks for getting in touch. When you mention you get this error when performing a lighthouse score, can you share whether you can view any PageSpeed Insights score from within the Site Kit dashboard? I ask as the issue may be specific to the tool you’re using to perform a score.

    If you’ve like me to perform some checks on your site you can also share your Site Health information privately using this form and I can see if I can determine anything blocking a score for your site.

    Thread Starter Curtis Stevens

    (@gotmerchant)

    Hi James,

    I’m referring to the inspecting tool through the browser. Under network, to see how things download and when, it pops up there. I’ve uploaded a screenshot online, you can see it here. I can’t attach anything to the forums.

    View post on imgur.com

    Plugin Support James Osborne

    (@jamesosborne)

    Hi Curtis,

    Unfortunately we can only provide assistance for any Site Kit specific queries. With that being said you the Lighthouse tool built into Chrome is used by PageSpeed Insights, so you can check your site across the same metrics using the Site Kit dashboard, the PageSpeed Insights platform or web.dev/measure. When doing so, you’ll find the same Core Web Vitals analysis results.

    Note also that while the 404 resources that you highlight refer to Google Analytics / Tag Manager scripts this may also be as a result of cookies or the scripts not running for logged in users. You can check does the same occur from a Chrome browser incognito window.

    I’m also happy to confirm that everything is setup and working as expected on your site, with regards any Site Kit placed snippet. In order for me to do so, feel free to share your site URL or Site Health information. You can do so privately using this form.

    Thread Starter Curtis Stevens

    (@gotmerchant)

    I submitted your form. I was doing it in incognito mode. I don’t understand, I can remove Kit and add the google tag manually and I don’t get the error, it is only with Kit. I’ve disabled the plugins that might interfere with it and no change.

    Thread Starter Curtis Stevens

    (@gotmerchant)

    Also, I’m not talking about PSI or anything about web core vitals, but the inspection tool to see what errors you have with your page’s code.

    Plugin Support James Osborne

    (@jamesosborne)

    Note that from reviewing the error on various forums the issue may also be from an unpublished Tag Manager container.

    Once we have your site URL I can check your set up. You may also wish to query the specific error from the Lighthouse project GitHub repository.

    Thread Starter Curtis Stevens

    (@gotmerchant)

    I gave you the staging url in your form. I don’t think I have anything in Tag mgr that’s unpublished.

    Plugin Support James Osborne

    (@jamesosborne)

    Hi Curtis,

    I’ve checked your site and I can confirm that both the Google Analytics and Tag Manager snippets are working as expected.

    Please check to ensure that your PageSpeed Insights score is working as expected from within Site Kit.

    Let me know if you have any further questions on the above.

    Thread Starter Curtis Stevens

    (@gotmerchant)

    Yes, I know they are working, it does in preview mode and yes I get PSI scores. I don’t understand why I’m getting that error message for. Something has to be wrong or why else is that error message popping up?

    Plugin Support James Osborne

    (@jamesosborne)

    Hi Curtis,

    It’s a browser console error, and not specific to performing any Lighthouse score from what I see after inspecting your site. I do see your Tag Manager and other snippets have additional attributes added to them (another example), which is likely coming from your CDN Cache Plugin or FlyingPress plugin.

    If you want to temporarily deactivate both, I’ll check does the same occur when checking your site once more.

    Plugin Support James Osborne

    (@jamesosborne)

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Get 404 Error’ is closed to new replies.