HTTP/2 is the latest encroachment of the Hypertext Transfer Protocol (HTTP). HTTP is the network protocol used to demand and obtain pages and data in the World Wide Web. The added technology will eventually supersede HTTP/1.1 which was standardized behind more two decades ago.
HTTP/2s main objectives were to shorten latency. It gets a little obscure but efficiencies were achieved using several techniques
HTTP/2 Headers are Compressed
Information sent encouragement on a demand describes the data, its lineage, type, length, how long it can be cached, etc. Unlike HTTP/1.1, this is now compressed in HTTP/2.
HTTP/2 Uses Pipelining
In HTTP/1.1, the server must send responses in the same order the requests were customary. HTTP/2 is asynchronous so smaller or faster responses can be handled sooner.
HTTP/2 is Multiplexed
In HTTP/1.1, unaccompanied one demand can be handled on a TCP association at any epoch. Browsers typically dealings together along with four and eight friends but large or slow assets can cause the download of supplementary files to be delayed. HTTP/2 permits compound demand and tribute messages more or less the same (single) relationship in the same period.
HTTP/2 Implements Server Push
Read more about HTTP/2 - https://http2.co/