Published back in 2015, HTTP/2 is a major revision of the world wide web protocol. It is best known as a new way of making your website faster as it eliminates many of the inefficiencies associated with the current version of HTTP. The main improvement over HTTP is that HTTP/2 has the ability to cover multiple requests in a single connection. As HTTP/2 is binary rather than text based, it makes it inherently more efficient, as binary protocols is much faster when transferring and parsing data. Further, HTTP/2 allows the server to start sending resources that it knows the web browsers will need, such as JS, CSS, etc. All this, among other optimizations, such as compressing headers before sending the requested data, has resulted in a performance boost of around 50%. Essentially, that means that if your website currently takes up to 3 seconds to load, then your website served over HTTP/2 could load in as little as 1.5 seconds (you can test the difference between HTTP/1.1 and HTTP/2 right here).
Though it all sounds great, moving to HTTP/2 might be a little tricky. Firstly, this is something done at the web server level, so you will need to check with your web server to see whether they support HTTP/2. Most web servers, including Apache, Nginx, IIS, etc, already do. If you run your own web server, you just need to install and enable the HTTP/2 libraries. However, the catch is that you must have a Secure Server Licence (SSL) Certificate before it can be enabled. Though HTTP/2 doesn’t actually require a secured website by itself, browsers only support it over SSL. As of which, your first step before moving to HTTP/2 should be to get an SSL Certificate.
Be sure to contact us if you would like some more information about HTTP/2 and how to enable it for your website.