<p>We had a lot of trouble finding where the problem was steming from because only on the first load would it take a very long time for a request to be made. This was because the event to trigger Safari in IOS 9.1 to do the request when the pool was overfull would not execute until the connection was closed. If some of the images or resources on the page were cached it would not cause a problem, but if the browser did not have a cache it would cause a problem.</p>
<p>This could have been avoided by "Spriting" the images together, making fewer requests, or sending the requests in sequential order instead of all at once.</p>
Get New Tutorials Delivered to Your Inbox
New tutorials will be sent to your Inbox once a week.