The essential points from this guide -- each one is explained in detail below.
Select proxy exit IPs geographically close to your target server to minimize round-trip latency.
Use connection pooling (HTTP keep-alive) to avoid re-establishing TCP and TLS handshakes on every request.
Switch to a provider with dedicated DNS resolution to eliminate DNS as a bottleneck.
Test with curl timing breakdowns to identify which phase (DNS, connect, TLS, transfer) is slow.
Upgrade from shared to dedicated bandwidth if your provider throttles high-volume users.
Every proxy request travels three legs: your machine to the proxy server, the proxy server to the target, and the response back through the proxy to you. If you are in New York, your proxy exits in London, and your target is in Tokyo, you are adding two transatlantic hops that a direct connection would avoid. The fix is simple: select exit IPs in the same region as your target. With KnoxProxy, you can target any of 195 countries -- pick the one closest to your target server.
Measure the impact with curl:
curl -x http://user:pass@gw.knoxproxy.com:7000 \
-w "dns: %{time_namelookup}s\nconnect: %{time_connect}s\ntls: %{time_appconnect}s\ntotal: %{time_total}s\n" \
-o /dev/null -s https://target-site.comIf time_connect is high (over 500ms), geographic distance is your bottleneck.
When many users share the same exit IP, each user competes for that IP's bandwidth. This is most common with smaller proxy providers that have pools under 1 million IPs. Symptoms include inconsistent latency -- some requests fast, others slow -- and occasional timeouts during peak hours. The solution is to use a provider with a large enough pool that IPs are not oversubscribed. KnoxProxy's pool of 90.4M+ residential IPs means individual IPs are rarely congested.
You can detect congestion by running the same request multiple times and comparing latencies. If times vary wildly (100ms to 3000ms) with no geographic change, you are hitting congested IPs.
A common mistake is opening a new TCP connection for every request through the proxy. Each new connection requires a TCP handshake (1 round trip) and a TLS handshake (2 round trips) -- that is 150-400ms of overhead before any data transfers. HTTP keep-alive reuses existing connections, eliminating this overhead for subsequent requests.
In Python with the requests library, use a Session object:
import requests
session = requests.Session()
session.proxies = {
'http': 'http://user:pass@gw.knoxproxy.com:7000',
'https': 'http://user:pass@gw.knoxproxy.com:7000',
}
# Connection is reused across requests
for url in urls:
response = session.get(url)In Node.js, use an http.Agent with keepAlive enabled. Without connection pooling, you pay the full handshake penalty on every single request.
DNS resolution happens on the proxy server side for HTTPS CONNECT requests. If your proxy provider uses slow or overloaded DNS servers, every request waits for domain name resolution. You can identify this by checking the time_namelookup value in curl output -- anything over 100ms suggests DNS problems.
Some proxy providers allow you to configure custom DNS servers. If yours does not, this is a provider-quality issue. Enterprise-grade providers like KnoxProxy run dedicated DNS infrastructure to keep resolution times under 20ms.
Some providers throttle bandwidth per user or per plan tier. If your speeds are consistently capped at a specific throughput (for example, always maxing at 2 Mbps regardless of target), your provider is likely throttling. Check your plan limits and usage dashboard. PAYG plans like KnoxProxy's $2.10/GB model do not throttle -- you pay for what you use at full speed.
To test for throttling, download a large file through the proxy and measure throughput:
curl -x http://user:pass@gw.knoxproxy.com:7000 \
-o /dev/null -w "speed: %{speed_download} bytes/sec\n" \
https://speed.cloudflare.com/__down?bytes=10000000Compare the result against your expected bandwidth. If it is consistently below your plan's stated limit, contact your provider.
Ready to put this into practice? Test your proxy speed
KnoxProxy Research Team · Technical Content
Network engineers and proxy infrastructure specialists with 10+ years in anti-bot systems, web scraping, and IP routing.
90.4M+ ethically sourced residential IPs across 195 countries. Start free -- no credit card required.