Хостинг от ERA Host
EraHost – Free Domain, Cheap Hosting!
Client Area
Support 24/7
USD
Menu

What was HTTP/2 created for?

http2 Since its inception in the early 1990s, HTTP has only undergone a few significant revisions. The most recent version, HTTP 1.1, has been in use for over 15 years. In an era of dynamic content updates, resource-intensive multimedia formats, and the constant drive for better web performance, the technologies of older protocols have become outdated. These trends call for substantial changes, which HTTP/2 addresses.

The main goal of developing the new version of HTTP was to deliver three key qualities—simplicity, high performance, and resilience—without relying on additional network technologies. These improvements were achieved by reducing delays in processing browser requests through techniques like multiplexing, compression, request prioritization, and server-initiated data sending (Server Push).

HTTP/2 includes enhancements like flow control, upgrade, and error handling, which help developers achieve high performance and resilience in web applications. The collective system allows servers to efficiently send more content to clients than requested, preventing repeated requests until the entire site is fully loaded in the browser. For instance, HTTP/2's Server Push feature enables the server to deliver all the page content at once, except for what’s already cached in the browser. Protocol overhead is minimized through effective compression of HTTP headers, improving performance with each browser request and server response.

Why is it important to look for ways to speed up website page loading times?

John Mueller, an analyst from the Google Webmaster Trends team, wrote in his blog that having HTTP/2 support on a website is not directly a ranking factor in Google. However, loading speed is a significant ranking factor in itself, so it makes sense to start using HTTP/2 for SEO purposes.

He added that simply speeding up a website should positively impact its ranking due to behavioral factors. Faster pages tend to have lower bounce rates, and more users are likely to take action on such pages, which can influence search rankings.

John Mueller also mentioned that Googlebot will soon start supporting HTTP/2. And who knows—perhaps in the future, having HTTP/2 on a website could become a ranking factor, as search engines are constantly updating their algorithms.

Does HTTP/2 offer anything to web developers?

Yes! HTTP/2 eliminates the need for several actions that were used to speed up page loading without HTTP/2. These include:

-
Domain sharding, or using multiple related domains to download files, allowing for more TCP connections to be established;
-
Image sprites — combining multiple images into one file to reduce the number of requests. However, the entire file must be loaded before any image can be displayed. Additionally, handling large files consumes more memory;
-
Combining CSS and JavaScript files, which is done to reduce the number of requests but also increases memory consumption;
-
Cookie-free domains: loading images, CSS, and JavaScript from a different domain where cookies are not used.
-
Domain sharding, or using multiple related domains to download files, allowing for a greater number of TCP connections to be established;

SSL Hosting + HTTP/2 Packages