I noticed I sometimes get a "net::ERR_CONNECTION_RESET" when our site tries to get the munchkin.js file causing the site to be unresponsive for several seconds. I tried putting the munchkin code in both the head and at the end of the </body> but does not seem to make a difference. Does anyone know why this could be happening?
Thanks Sanford! It does not happen all the time but enough to make it noticeable and annoying.
We're also seeing the same thing on our end, the behavior seen is super slow responses, we're taking the code out of our website & other properties for now.
Loading the library JS asynchronously doesn't affect load performance unless you're also using old-school onLoad listeners (which you shouldn't be).
We are using the async code detailed in your developers guide:
There is a part that uses onload on line 20. Is that what you are referring to?
If anyone else was experiencing this issue, there was indeed an issue with the munchkin code server in the San Jose datacenter that was causing the error.
Obvs. not good, but if all assets are truly async (no accidental dependencies elsewhere in your code) a TCP reset wouldn't have side effects.