what are the advantages of HTTP 2.0 over HTTP 1.1?

Multiplexing - HTTP/1.1 loads resources one after the other, so if one resource cannot be loaded, it blocks all the other resources behind it. In contrast, HTTP/2 is able to use a single TCP connection to send multiple streams of data at once so that no one resource blocks any other resource. HTTP/2 does this by splitting data into binary-code messages and numbering these messages so that the client knows which stream each binary message belongs to.

Server push - Typically, a server only serves content to a client device if the client asks for it. However, this approach is not always practical for modern webpages, which often involve several dozen separate resources that the client must request. HTTP/2 solves this problem by allowing a server to "push" content to a client before the client asks for it. The server also sends a message letting the client know what pushed content to expect – like if Bob had sent Alice a Table of Contents of his novel before sending the whole thing.

Header compression - Small files load more quickly than large ones. To speed up web performance, both HTTP/1.1 and HTTP/2 compress HTTP messages to make them smaller. However, HTTP/2 uses a more advanced compression method called HPACK that eliminates redundant information in HTTP header packets. This eliminates a few bytes from every HTTP packet. Given the volume of HTTP packets involved in loading even a single webpage, those bytes add up quickly, resulting in faster loading

Multiplexing - HTTP/1.1 loads resources one at a time; as a result, if one resource cannot be loaded, all the resources that are loaded after it are blocked. Contrarily, HTTP/2 enables the simultaneous transmission of numerous data streams over a single TCP connection, ensuring that no resource obstructs another. In order for the client to identify which stream each binary message belongs to, HTTP/2 divides data into binary-code messages and numbers these messages.

Server push - Normally, a server will only provide material to a client device upon request. However, given that current webpages frequently require the client to request dozens of different resources, this strategy is not always feasible. This issue is resolved by HTTP/2, which enables a server to "push" material to a client before the client requests it. As if Bob had sent Alice the Table of Contents of his novel before delivering the entire thing, the server also sends a message informing the client of the pushed content that is to be expected.

Small files load more rapidly than large ones because to header compression. Both HTTP/1.1 and HTTP/2 compress HTTP messages to make them smaller and speed up online performance. HPACK, a more sophisticated compression technique used by HTTP/2, gets rid of extraneous data from HTTP header packets. Each HTTP packet is reduced by a few bytes as a result. These bytes quickly add up given the number of HTTP packets required to load even a single webpage, leading to speedier loading