Get ready to move from HTTPS to this new technology

Many sites have recently moved from the Http protocol to the Https protocol. This transition was aimed at improving the site’s ranking in search results on Google (for more information about Https you can read the following article). After this transition, Google comes to us with a new statement to tell us that it is about to support a new protocol that is more advanced than the current Http and has better performance. This support will begin at the end of this year or at the beginning of next year. So what is this protocol? Continue reading with me.

What if I told you that this protocol will make your site

It loads on the user's browser more quickly, and the performance of the server that hosts your site will improve significantly. By using this new protocol, site developers will not have to spend hours and hours making your site faster in order to improve the ranking in search results. What is this magic protocol then? It's HTTP/2, my dear.

Topic Contents Toggle What is Http/2 Roots

Http/2 The basic improvements that were added in the Http/2 protocol Browsers that support Http/2 A comparison between HTTP/2 and HTTPS The benefits of Http/2 for the user The benefits of Http/2 for the developer The benefits of Http/2 for servers The benefits of Http/2 to improve ranking in search results What is Http/2 Http/2 is the latest version of the Http protocol For browsing Internet sites, this protocol is developed periodically by the IETF (Internet Engineering Task Force). The current version currently used of this protocol is Http/1.1, which was released in 1999, and since that time there has been no update to this protocol. However, with the increasing development in the world of the Web and the Internet, this protocol had to be developed to appear in its latest version. This update included many features, the most important of which are speed and security. The roots of Http/2 The new development of this protocol was built on a protocol called SPDY, which is an Internet protocol that was invented by Google and whose patent belongs to Google. This development took many of its features from the Google protocol, as it turned out that there are many common features and improvements between Http/2 and SPDY. We will not go into the technical details of this protocol, but rather we will discuss the points that only concern us as those working in the field of search engines. The basic improvements that were added in the Http/2 protocol - Opening a single connection: One and only one connection is opened between the browser and the server to load the site on the user’s browser, and this connection remains open as long as this site is open on the user’s browser. This has its benefits and is better than opening several communication channels between the user and the server.

– Multiplexing: It is a feature that allows the user to send more than one request at the same time to the server and within the same communication channel. In the previous version of this protocol, you had to wait until the previous request was completed so that you could send the next request, but in this update you can send several requests together. – Server Push: This feature enables you to send different types of data and is set for future use. – Priority: In the latest update to this protocol, every request sent to the server is given a priority indicating its importance, and based on these priorities, upcoming requests are processed so that the highest priority request is processed before others.

- Binary: A feature that enables the server to process HTTP/2 protocol headers more easily and reduces the possibility of errors. The HTTP protocol sends data in the form of text and then the server converts this text into zeros and ones in Binary. As for the new update, it sends the contents directly in the form of Binary, which speeds up the processing process on the server side. - Compressed headers: This protocol uses a technique for compressing information called HPACK. This technique reduces communication between the server and the client in order to transfer data, that is, by comparing the two cases (before and after updating the protocol). In order to send the same amount of data between the server and the client, you will need a smaller amount of headers and request headers in the Http/2 protocol compared to Http. Perhaps all of the previous talk for you is just theoretical talk and you want to see something practical that shows you the difference between the two protocols. Well, I will provide you with the proof that will make you make an immediate decision to move to Http/2. Please go to the following two sites and notice the difference in speed between the http and http/2 protocols: - https://http2.akamai.com/demo - http://www.http2demo.io/ Browsers that support HTtp/2 The percentage of browsers that support the technology is Http/2 is currently 67.89% of the browsers used by users. There are some things that you must take into consideration regarding these compatibility issues. For example, Internet Explorer 11 supports Http/2 only in Windows 10, and Chrome -– Firefox -– Opera both support Http/2, but under special conditions, which is that it must be used with Https.

You can check how your site is compatible with different browsers after moving to HTTP/2 by relying on Google Analytics by going to Audience, then Technology, then Browser & OS. On this page you can see the compatibility of browsers and web software (NGINX - IIS - Apache) with this protocol. The last thing I want to mention is that all CDNs have begun to support this protocol.

Comparing HTTP/2 and HTTPS is an important advantage

This protocol supports secure communications and unsecured communications, that is, it combines the advantages of Http and Https in one protocol. Unfortunately, some browsers do not support this protocol unless https, that is, supports you with a certificate that makes it reliable. Anyone who has converted his site from http to https fully understands what I am talking about. Let me explain the matter more: If you want to move to Http/2 and want your site to be supported by most browsers, you must purchase a certificate. In fact, this is not an issue worth thinking about for several reasons: First, most of the site currently has moved to Https, and therefore you have a certificate and you will not worry about this issue. If you have not moved yet and want to buy a certificate, its price is cheap and does not exceed $100 annually, and if you want to obtain a certificate for free, you can resort to Let’s Encrypt, which grants certificates for free. This project is currently in a beta version and will grant free certificates.

The benefits of HTTP/2 for the user are the most important for the user

The benefit he will get is speed, as he will notice the difference in speed and will be impressed by the speed with which your site opens, which relies on the Http/2 protocol. The benefits of Http/2 for the developer: The developer will no longer need many of the technologies that he used previously in order to speed up the site that relies on Http 1.1. Some of these technologies are expensive and some require time, but with the new update to Http, goodbye to these technologies. The benefits of Http/2 for servers: For servers that host websites that use the http/2 protocol, the performance of these servers will improve significantly due to the small number of incoming requests, the small number of connections, the lack of need to convert from text to zeros and ones, and other benefits that make moving to this update a very useful matter.

The benefits of Http/2 for improving rankings in search results for the field of SEO and for rankings in search results. Relying on http/2 with the use of a certificate proving that the site is secure means that your site is a secure site and fast loading in the User browser. Security and loading speed are factors in Google’s algorithm, so expect an improvement in your site’s ranking if you move to Http/2. Add to that the expectations that Google will add the site’s use of the Http/2 protocol as a factor in its algorithm, so you will notice We will start moving to this protocol soon. #SearchEngines #SearchEngineOptimization #SEO #HTTP2 #GoogleSEOtag