Chrome Inspect Error

  • Resolved hl247

    (@hl247)


    5 years, 3 months ago

    Hi,

    We would appreciate any kind of advice or information about an error we receive when we use the “Inspect” tool on Chrome. It just started happening and we tried to resolve the issue by unplugging all plugins but had no luck. Is anyone else receiving this error?:

    beacon.min.js:22 Cross-Origin Read Blocking (CORB) blocked cross-origin response https://metrics-collector.s-onetag.com/metrics with MIME type application/json. See https://www.chromestatus.com/feature/5629709824032768 for more details.

    The error above will actually reproduce itself a few times while using Chrome Inspect. Again, we are not very familiar with errors and would appreciate any help or advice.

    Thank you!!
    Cindy

    • This topic was modified 5 years, 3 months ago by Jan Dembowski.
    • This topic was modified 5 years, 3 months ago by Jan Dembowski. Reason: Moved to Fixing WordPress, this is not an Everything else WordPress topic

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Disable any and all extensions you have in Chrome. (The easy way is to use an incognito browsing session.) I don’t get any errors in the inspector, so I’m assuming it’s your Chrome config.

    Thread Starter hl247

    (@hl247)

    Hi Steve,

    Thanks for the suggestion and help! It takes a minute or two for the error to show up but will appear quicker if you switch pages or move around the site.

    As you suggested, I disabled all extensions, cleared History, rebooted computer, and used Incognito but the warning is still there. I also tried using a different network and different computer that is brand new.

    The reason I’m so concerned is because the number of warnings increase, like the problem is active. If you have any other ideas I would be glad to try….I really appreciate your help!!

    Thank you,
    Cindy

    Thread Starter hl247

    (@hl247)

    Update:

    I was able to identify what the warning is and locate what causes the problem. The error is caused by an embed piece of code that a company request we add to all pages so that we can track affiliate links we publish. The code is in our footer and when we remove it, the warnings from Chrome are resolved.

    Thanks again for the support!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Chrome Inspect Error’ is closed to new replies.