<\/p>\n
Imagine working on the first desktop you ever used right now. Like seriously imagine doing serious work on it now. Sounds preposterous right? We thought so too. <\/span><\/p>\n Similarly it\u2019s absolutely ridiculous to still stick to HTTP 1.1 for your WordPress websites, a protocol which was <\/span>ratified back in 1997.<\/span><\/a> Just like the desktop that you used back in 1997, the HTTP 1.1 was not designed to deal with today\u2019s internet. In fact it was created long before anyone understood what the World Wide Web will turn out to be like. Naturally, we have to improvise and learn our way through to make sure that our websites keep up with the present times; work faster and are optimized.<\/span><\/p>\n As we were trying to explain above, 20 years is a lot of time in tech years; anything that is from before the last 5 years is arguably ancient when we are talking tech, and the same applies for HTTP 1.1. <\/span><\/p>\n The size of normal websites has increased from a few kilobytes to few megabytes. The actual number of files needed to run a website easily cross a hundred or more by norm. This evolution, the explosion in size and number of files that run a website, is too much for the older HTTP to handle. <\/span><\/p>\n The HTTP\/2 (standardized in 2015) is much more evolved version that is ready to tackle the new age internet and its challenges.<\/span><\/p>\n \u201c\u2026 Decrease latency to improve page load speeds in web browsers.\u201d \u2013 <\/span><\/i>Wikipedia<\/span><\/i><\/a><\/p>\n <\/p>\nWhy HTTP\/2?<\/b><\/span><\/h6>\n