0 
0 
We have upgraded to HTTP/2 and here is why.
Since the inception of the World Wide Web (www), the HTTP protocol has evolved over the years to deliver secure and fast digital content over the internet.
The most widely used version is HTTP 1.1 and while it packs with feature enhancements and performance optimizations to address the shortcomings of earlier versions, it falls short of a few other salient features that have been addressed by the HTTP/2.
What are the Limitations of HTTP/1.1?
The HTTP/1.1 protocol is fraught with the following shortcomings that make it less ideal especially when running high-traffic web servers:
- Delays in loading web pages due to long HTTP headers.
- HTTP/1.1 is only able to send one request for each file per TCP connection.
- Given that HTTP/1.1 processes one request for every TCP connection, browsers are forced to send a deluge of parallel TCP connections to simultaneously process the requests. This leads to TCP congestion and ultimately bandwidth wastage and network degradation.
The above-mentioned problems often led to performance degradation and high overhead costs in bandwidth usage. HTTP/2 came into the picture to address these problems and is now the future for HTTP protocols.
Advantages of Using HTTP/2
It offers the following advantages:
- Header compression that minimizes client requests and thereby lowers bandwidth consumption. The resultant effect is fast page load speeds.
- Multiplexing several requests over one TCP connection. Both the server and the client can break down an HTTP request into multiple frames and regroup them at the other end.
- Faster web performances which consequently lead to better SEO ranking.
- Improved security since most mainstream browsers loads HTTP/2 over HTTPS.
- HTTP/2 is considered more mobile-friendly thanks to the header compression feature.
See tecmint.com/enable-http2-in-apache-on-ubuntu/ for more info and a great guide that we used to enable our sites for HTTP2
