• Resolved periwinklefr

    (@periwinklefr)


    Since few days, we are experiencing a very strange behaviour with Jetpack Stats.

    The .js file is not loading from https://stats.wp.com/ on some 4G connections providers : SFR for example. On the same device connected to wifi with a fiber internet connection it’s working fine….

    It happens on Android or iOs devices regardless…

    On remote debug with Chrome (chrome://inspect/#devices) the file status in the Network inspection panel remains “pending” and never loads, so dom event loaded never fires, and so, all navigation and features waiting for this event aren’t initialized…
    Once Jetpack stats (both Stats and Woocommerce Stats) are disabled the website just work fine.

    The printscreen of the problem :

    https://pasteboard.co/KD6nkhsFctSs.png

    I’m pretty sure that we are not alone facing this issue but we didn’t find a solution.

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

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Tamirat B. (a11n)

    (@tamirat22)

    Hello @periwinklefr ,

    Thanks for reaching out to us.

    I checked from my side and I don’t see the pending status for the javascript file for Jetpack Stats. Please see the screenshot here: https://d.pr/i/FgtTkb.

    Some third-party plugins such as cookie consent plugins like the one installed on your site have been known to block the Jetpack Stats script from loading until users accept to be tracked. Browser extensions could also be the culprit here.

    Can you please try loading the script from a clean browser session with third-party extensions disabled, and after accepting the cookie consent banner shown on your site?

    Look forward to your updates!

    Thread Starter periwinklefr

    (@periwinklefr)

    The problem seems to be solved by itself !

    The problem was only occuring on 4G connexion operated by the french operator SFR… The problem should be on the operator side.

    Best regards

    Plugin Support Paulina H. (a11n)

    (@pehaa)

    Hi @periwinklefr,

    Thank you for the update. I’m glad you were able to sort it out.

    Best regards

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.