You mentioned reproducing it in incognito which rules out a browser extension.
If you’re seeing it on, different computers, browsers and networks, without browser extensions… that’s a fairly clear signal that it’s either something specific to your site, or something server-side.
Are the test machines all in the same general geography? Might try testing against other CDNs using a VPN to another country. That would help you isolate it if you run the test on the same machine that’s giving you problems.
The only other thing I noticed is the large number of WebGL warnings like GL_INVALID_FRAMEBUFFER_OPERATION. I suppose it’s possible that a script in your head is running and creating a blocking effect on resource loads.
However I mostly see that on the homepage, which you mentioned is working for you.
I’d try;
- Publish to staging, try to reproduce on staging
- Clone the site, publish to staging, try to reproduce in the clone
- Comment out all custom scripts and custom CSS in the clone, republish, retest on staging
If the problem seems specific to your main published site, you could try;
- Unpublishing and republishing the site to see if the “resets the CDN”
- Cloning the site, and swapping over the site plan and domain to the working clone