The load time is contingent on ping, for instance with TLS over TCP you need 3 full round trips to get a pipe that can carry HTTP, this is 3x as many as with TC

The load time is contingent on ping, for instance with TLS over TCP you need 3 full round trips to get a pipe that can carry HTTP, this is 3x as many as with TCP alone. In the author's scenario there's a 500ms delay, so naively that's ping of 250ms which is really high. In the case of HTTP/1.1 or asset loads from other origins, there may be additional connections that are made which will all incur the extra overhead as well, though the author's blog is served over HTTP/2 which wouldn't incur this cost for same origin asset requests. For me best case for author's blog (just the HTML via curl) is 250ms plaintext and 600ms TLS. What's more interesting is that plaintext is a lot more consistent for me because I have pretty bad packet loss and the HTTP request fits into a single TCP segment.