Your statement is only possibly true for a single request. In any real world application, the ability to issue many requests without having to open a new connection each time and to receive results out of order is a massive win over HTTP, even before you consider things like server push allowing resources like stylesheets or scripts to be delivered immediately rather than waiting for the client to finish parsing an HTML document.
Sharding helps with only the connection limit at the expense of extra redundant DNS delays and poor scheduling of the total available network capacity. It cannot help with the need to request resources sequentially and has no equivalent to something like server push avoiding extra round-trips + client delays before even issuing requests for related resources.
>The majority of data has no need for encryption. Some of it does.
No. Wrong. Absolutely, incontrovertibly wrong. Everything that doesn't absolutely need to be plaintext should be encrypted; everything that can be authenticated should be.
