3 ms·
Using wget for a test is just terrible. Here's a better test (and I'll put it here, so everyone can criticize it): 1) start chrome in incognito mode. 2) pr
by rgbrenner 14y ago
Using wget for a test is just terrible. Here's a better test (and I'll put it here, so everyone can criticize it):
1) start chrome in incognito mode.
2) press f12, and then click on network
3) load each js
I'm in Denver, this is what I got:
Google:
DNS Lookup: 14ms
Connecting: 24ms
Sending: 0
Waiting: 46ms
Receiving: 42ms
TOTAL: 128ms (86ms latency)
Cloudflare:
DNS Lookup: 15ms
Connecting: 43ms
Sending: 0
Waiting: 46ms
Receiving: 49ms
TOTAL: 154ms (105ms latency)
I can't take a test run with wget seriously when there are better tools so easily available. It's beyond lazy.. it's incompetence, or worse, dishonest. He couldn't even be bothered to run it more than once from his own computer(!)