proxareResidential IPs run over real home connections, so some latency is normal. These eight changes usually make the biggest difference.
A residential proxy sends your traffic from your machine to the provider's gateway, then to a real home device, then to the website, and back the same way. Each hop adds time. A first response in 1 to 3 seconds is normal; 10 seconds or timeouts are not. Here is what to check, roughly in order of impact.
1. Use the gateway closest to you
Many providers run gateways in several regions. If you are in Europe and connect to a US gateway, every request crosses the Atlantic twice before it even reaches the residential IP. Pick the EU or Asia endpoint when it is closer to your server.
2. Target the country you need, not more
City and state targeting narrows the pool. Fewer available IPs means busier ones and slower connections. Only use city targeting when the city really changes the result.
3. Reuse connections
Opening a new connection costs a TCP handshake plus a TLS handshake through the proxy. Use a session or client object that keeps connections alive (requests.Session() in Python, an agent with keep-alive in Node) instead of a fresh one per request. On rotating lines, note that a kept-alive connection usually keeps the same IP.
4. Raise your timeouts
A 5-second timeout that works on datacenter IPs will cut off healthy residential connections. 30 seconds is a reasonable ceiling, with a retry on a new IP.
5. Retry smartly
When a request fails on a rotating line, retry once or twice; you get a different IP each time. On sticky lines, a dead IP will not come back, so start a new session ID.
6. Load less
A full browser page can be 2 MB or more. Blocking images, fonts and video in your headless browser makes pages load faster and uses less data.
7. Check whether it is the proxy or the site
Measure where the time goes:
curl -x http://user:pass@host:port -o /dev/null -s \
-w "connect %{time_connect}s first byte %{time_starttransfer}s total %{time_total}s\n" \
https://example.comIf the connect time is fast but the first byte is slow, the target site is slow or is rate limiting you. If CAPTCHAs or 403 errors appear, slow responses may be the site throttling you, not the proxy.
8. Do not overload one sticky IP
Pushing 50 parallel requests through one home connection will make it crawl. Spread the work across more session IDs or use rotation.
Still slow?
Try a different provider for the same target. Pools differ by country and by site, and the best one for one target is not always the best for another. That is why Proxare lets you buy from several networks in one account.
More guides
Also in: Français · العربية · Tiếng Việt · 中文 · Українська