> For a small test page of 15KB, HTTP/3 takes an average of 443ms to load 443 milliseconds!! When typical user latency is sub 50 milliseconds, requiring 443

> For a small test page of 15KB, HTTP/3 takes an average of 443ms to load 443 milliseconds!! When typical user latency is sub 50 milliseconds, requiring 443 milliseconds to get a lightweight page displayed on the screen is terrible. Users perceive 100 milliseconds as near-instant, and that ought to be the target. With 50 milliseconds of network latency, and 0-rtt support, that gives 50 milliseconds for server and client processing+rendering. Ought to be very do-able. The fact it has not been done really is a failure of software engineering as an industry - we always favour more layers of abstraction over perfecting the user experience.