Ability to double ping measurement. about speedtest HOT 8 CLOSED

Yes, that's probably a good idea.
I'll add that in the next version

from speedtest.

I'm sure I had that in the old version of the documentation.
Anyways, expect an update in the next few hours.

from speedtest.

Try asking him how he solved it. My guess is that it was incorrect server config.

from speedtest.

...or you can just remove the /2 at line 325 in worker.js

from speedtest.

@adolfintel Why do you divide the time by 2 anyway?

from speedtest.

Because of how HTTP works. When you make a XHR request, here's what typically happens:

• TCP connection is created (1 RTT)
• HTTP request is sent (0.5 RTT)
• HTTP response is received (0.5 RTT)

In total, that's 2 RTT, hence the /2.
The problem is if you're using a persistent HTTP connection because only the first request takes 2 RTT, then the next ones take only 1 RTT. This typically doesn't happen for XHR though.

from speedtest.

A good idea in theory, but not when your server sends a Connection: keep-alive header:

I'd suggest making keep-alive mandatory for the server setup and then just discarding the first ping result (the one that establishes the connection).

from speedtest.

You might also want to mention the limitations of the ping test more clearly: I came here after a hosting provider got called out for false advertising on a forum because the ping results from his speedtest page were half of what you would get from normal ping commands.

Disclaimer: I'm not that provider, just a curious bystander. ;)

from speedtest.