Speeding up HTTPS and HTTP/3 negotiation with DNS

> The browser will first try to fetch the resources using plaintext HTTP,

In Chrome and friends, not since April 2021.

https://blog.chromium.org/2021/03/a-safer-default-for-naviga...

Given Chrome's dominant position (65% market share), if a blanket statement is given, it should reflect what Chrome does.

Also, for quite longer than that, if a site has any https-retrieved assets in the [Chrome] browser cache, it insists on loading https-only. This is a bit stronger than trying https first, then falling back. So only the very first visit per browser-cache-instance (profile, more or less) is penalized. This extra latency is easily absorbed/amortized.