Switching from HTTP/1 to HTTP/2 protocol

in seo •  4 years ago 

grafik.png
Image source: Pixabay


It is really frightening how many domains and the servers responsible for them still communicate with the old HTTP/1 protocol. This protocol is almost as old as the web.

Congratulations to the admins of Steemit.com, the HTTP/2 protocol is running here.

In fairness I have to say that hive.blog runs too with HTTP/2.


Everyone can test their website here. https://tools.keycdn.com/http2-test
The tool checks the header and provides information about the version used.
There are even large sites whose servers are not properly configured.
Example Apple.com
If I check https://apple.com I get this result:

I test with www, i.e. https://www.apple.com i get this result:

This means that Apple's server admins have no idea and should be fired 😊.

Even the well-known GMX still looks very old here, both Domain.net and domain.de still use the old HTTP/1 protocol.

Regardless of whether with www or without, the transmitted header should be the same. I don't know any reason why it should be any different. I really wonder what the people there are paid for. There is no understandable reason to stick with HTTP/1.

The advantages of HTTP/2 are:

In contrast to the HTTP/1 connection, in which the data is sent uncompressed, HTTP/2 transmits the information compressed in binary code. This should also speed up the processing of the data. Further advantages of HTTP/2 compared to HTTP/1 are the prioritization of data packets, the server push and the elimination of head-of-line blocking. Data packets are sorted according to importance and transmitted in the appropriate order, whereby the files that are important for a fast page loading are transmitted to the browser first. JSS, CSS and other file formats can be transmitted via the server push without prior request from the client. With the elimination of head-of-line blocking, the problem in HTTP/2 can no longer arise that all subsequent data packets are blocked due to the delay in the transmission of a data packet. This problem still exists in HTTP/1.

Usually there is no question that HTTP/2 is better than HTTP/1.
The reason why many server administrators don't switch to HTTP/2 can ultimately only be due to laziness.

The configuration (the change from version 1 to version 2 of the HTTP protocol) usually only takes a few minutes. Everyone can find hundreds of tutorials in the web on how to do the change for the respective server operating system.

If you need help with Debian or Ubuntu, I am happy to help.

The answer to the question: Does the switch from HTTP/1 to HTTP/2 bring SEO benefits, is clearly YES!

11 Tipps für neue STEEMIANS

Ave Atque Vale!

사랑은 나에게 신성한

My better search for STEEMIT: https://bit.ly/steemit-search

Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE STEEM!
Sort Order:  

Really useful information that you did not know before. Thank you and always with my support for you continuously and welcome to my page

@seo-boss, Good to read about the Technical aspects. Have a pleasant time ahead and stay blessed.

Wow. I never really knew there is an important difference between the two until now. And please I have a problem posting in your community and even other communities, the POST button in blue color isn't functioning here at my end.

This post has been rewarded by #nutbox. Nutbox is the DApp Incubator of Steem , and you can mine PNUT token by staking to us via https://nutbox.io .Contact us at https://discord.gg/zPkMuGY