Cycle about HTTP part 5

I’m hungry — eats heading HTTP

HTTP 2.0 or HTTP 1.0

If anyone remembered in 2015, there was considerable publicity of the HTTP 2.0 protocol which replaced HTTP 1.0. In 2018, most networks use the HTTP 1.0 protocol, and with HTTP 2.0, 32% of the global network increases. HTTP 2.0 is multiplexing defined as performing more queries to the server at once. The HTTP 1.0 version is only queued.

Multiplexing can speed up the display of the website page when we have a large server computing power without this it can have the opposite effect than is anticipated. It is worth knowing that the Google corporation creates the HTTP 2.0 protocol known as SPDY. Google withdrew SPDY support for HTTP 2.0.

If Google has implemented HTTP 2.0 then it will support technologies in SEO?

Of course it increases the positioning of the page when the 2.0 protocol is used, but it is not confirmed.

Is it worth implementing HTTP 2.0 for our websites?

Depending on what are the websites. In certain situations, it is worth implementing HTTP 2.0. When we have to do such as pictures, css, js or movies the best solution is the HTTP 2.0 protocol. When the data is important, for example, content, transactions or forms, I recommend that the HTTP 1.0 protocol. It has more control of the data flow between the client and the server. That is why it is worth mixing the 2.0 and 1.0 protocol in websites.

References:

https://www.thewebmaster.com/hosting/2015/dec/14/what-is-http2-and-how-does-it-compare-to-http1-1/

https://www.keycdn.com/blog/http2-statistics


Cycle about HTTP part 5 was originally published in Qunabu Interactive on Medium, where people are continuing the conversation by highlighting and responding to this story.