A lot of questions have come up this week about our proxy speeds. The answer I've typed out 100 times has not changed from customer to customer, so I am writing here to explain why your speeds in your software do not reflect our proxy speeds, but rather your server speeds (and if you're on a home computer, then you're in for some slowwww speeds... get a VPS: http://shoeservers.com/)
In any connection to a website through a proxy, the networking process goes as followed:
server (or home computer) -> proxy server -> website -> proxy server -> server
This gets your data sent to the website, and awaits the reply from the website.
Now imagine you having a server that is located in Florida, or even worse, a home computer that has 50 Mbps speed (most home internet does). If you're connecting from Florida, to a proxy server located in LA, then have to wait for that reply back after the website returns the data to the proxy server -- you're looking at TWO cross-country (3000+ miles each way) trips to get the connection closed. In no near future will you be able to have 100ms or less speeds when you're connecting to another server 3000 miles away.
This is why I discredit ANY speed tests anyone performs on our proxies because it is solely dependent on their server's speed (it must match our proxy speeds which are 1 Gbps), and their server's locations. The ideal situation for sneaker buying is having a server located in the same datacenter as the proxies, which we offer at http://shoeservers.com/. This makes the distance from server to proxy, and back, almost 0, which only leaves the latency to/from the website.