Wolfox: Checked the console and there are some errors there:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at
https://www4-static.gog-statics.com/js/customSection-16d9dc7.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at
https://www4-static.gog-statics.com/js/customSection-16d9dc7.js. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing).
Uncaught Error: [$injector:modulerr] Failed to instantiate module gogFrontpage due to:
[$injector:modulerr] Failed to instantiate module frontpageCustomSectionModule due to:
[$injector:nomod] Module 'frontpageCustomSectionModule' is not available! You either misspelled the module name or forgot to load it. If registering a module ensure that you specify the dependencies as the second argument.
Sounds like a misconfiguration, maybe related to CDN, since some locations might be working and others not.
So the mystery as to why some people are affected and others are not is a simple one: different browser policies. Now, the real mystery is why it affects people completely differently depending on what page they're on. How is that missing header inconsistently missing?