Why is there a 150-second delay between my HTTP requests?

Why is there a 150-second delay between my HTTP requests?

eiwata
Visitor
2 0 0

I have encountered an issue regarding extremely long load times -- 150 seconds, and I do mean seconds, not milliseconds -- that I suspect is due to a CDN issue, and I believe I have done my due diligence to assert my point that it is not the theme code nor plugins causing the issue. Regardless, I cannot seem to get very far with Shopify chat support, so I am looking to see if there are any community members that may shed light on the issue that is occurring.

 

I can replicate the problem very simply from the command line, using cURL to request a specific asset from my site, i.e. `time curl https://shoplivylu.com/cdn/wpm/s181a54bfw1c85c3aepe58c984em7036152bm.js` and then immediately requesting it again. If it is requested immediately after, I appear to be put in a "penalty box" for two and a half minutes, after which the response will come back. If it is requested after some time has passed, the response will come back right away. I theorize that there some sort of cookie-based request throttling policy, as sending along a specific cookie will allow the requests to come through immediately.

 

Before stating the obvious that users will not be using cURL to navigate the site, realize that the problem occurs, albeit in a less predictable manner, when using a regular browser. I do not have the luxury at the moment to ascertain why certain site assets are not sent along with the cookie while others are, so I am looking to remove or at least greatly reduce this constraint on requests. Furthermore, this throttling behavior also appears inconsistent with how other Shopify sites act. Though this may not be an apples-to-apples comparison, I have attempted to cURL a featured Shopify site, https://hiutdenim.co.uk, and successive requests resolved immediately, so I'm not sure what's up with my configuration.

 

I'm hoping someone with some technical background can take this seriously and provide insight as to why such an onerous penalty is applied to successive requests to what appear to be CDN hosted assets. If someone here has some advice as to how this may be elevated, or, better yet, resolved, I would be very grateful.

 

Replies 2 (2)

eiwata
Visitor
2 0 0

Never mind, I discovered the problem.

Tryhard
Excursionist
25 2 25

Give us the actual answer. There is nothing more frustrating than people who discover the issue and just say "Nevermind, I fixed it", leaving other people hanging. Donät be part of the problem dude.