"263 HTTP requests" Seems reasonable. bwahahaha! Shall we discuss the number of DNS requests? And how many of those offsite servers are using something conv

"263 HTTP requests" Seems reasonable. bwahahaha! Shall we discuss the number of DNS requests? And how many of those offsite servers are using something convoluted like Amazon for DNS? (which I find is more and more prevalent thanks to AWS) The blog author, e.g., is using Amazon for DNS. Alas, for each and every name, this adds more than a few lookups to what could be a 1-2 request process. Amazon uses multiple levels of indirection. This dance is not of much consequence in the case of a single name. But in the aggregate, e.g., many names requested from one overloaded site (such as one author singles out) after another, it does add up. This also creates a larger margin for errors (failed lookups getting retried and timing out, again and again... while the user sits and waits).