Ever since I bought this machine (and swapped the ISP) I came to understand that it was not my machine at fault; it's most websites that are turtle-slow.
When I visit a web page, I load 1 file. 1 file. Show the page and then start loading the images, if any.
You can gain much by not loading any javascript, not caring a bit about css and having a very fast HTML parser and renderer.
Surely the webpage can only use HTTP, and there is no concept of a connection in JavaScript or HTML/CSS.
So it must be the responsibility of the browser to reuse connections, or to response multiplex efficiently in HTTP/2.
(Although, to an extent, the contents of the webpage do determine how long the browser will keep the connection open. Also, WebSockets exist.)