Why Is Speedtest.net Taking Longer to Find an Optimal Server?
Asked by
MellowPine47
Has anyone else noticed that Speedtest.net has become much slower at choosing a test server lately? It used to identify an optimal server within about 3–5 seconds, but over the past month it has often taken 15–20 seconds. I'm not sure whether the delay is caused by the website, advertisements, my local ISP, or something else between my connection and the server.
Answers
For a quick comparison, Fast.com, Cloudflare Speed Test, and Measurement Lab’s speed test are useful alternatives. Testing with more than one service can help determine whether the delay is specific to Speedtest.net.
Reply to this answer
The delay could be related to the page loading its advertisements and other site content before the server-selection process finishes.
Reply to this answer
It may be an issue somewhere between your connection and the automatically selected test node. Try running the test against a few different nearby servers to see whether the delay follows one particular endpoint.
Reply to this answer
You can bypass the automatic selection by manually choosing a test server. That’s especially useful when running the command-line version, since it avoids waiting for the optimal-server lookup.
Reply to this answer
Add your answer
Answers are reviewed before publication.
Related Discussions