![\"HTTP2_AhmadAwais\"](\"https:\/\/ahmadawais.com\/wp-content\/uploads\/2015\/09\/HTTP2_AhmadAwais.jpg\")
<\/p>\nCan you imagine what would happen if you try to develop a website with a computer which you bought in 1997? \u2014 Yes! That’s even before Google \u2014 I want you to stop reading for a moment \u2014 stop everything and close your eyes \u2014\u00a0just imagine how it would be to do what you do now on a computer that old?<\/p>\n
<\/p>\n
If you read my previous post about Advanced Gulp Workflow for WordPress<\/a>, chances are you already know a lot about the pain points of front-end development. So, instead of explaining what they are, let’s shift our focus towards HTTP\/2 in this post.<\/p>\n If you’re still reading this post, it means you have an above average interest in how the internet works, while you’re at it take a look at super cute web comics about How DNS Works<\/a>\u00a0by good folks at @DNSimple<\/a>.<\/p><\/blockquote>\n So, let’s begin with the front-end development pain points, shall we.<\/p>\n So, what’s the deal?<\/p>\n HTTP 1.1\u00a0was standardized in 1997.\u00a0While it did a good job, it is no more efficient and to top it off, it was designed 16 years ago. Just like the\u00a0desktop you had in 1997, this protocol was not designed to deal with today’s internet. It was designed before we even knew what the world wide web would become.\u00a0So, to get it working in this age, we had to improvise hacks that could help make our websites fast and more optimized.<\/p>\n Let’s review why we needed these performance techniques in the first place.<\/p>\n HTTP\/2 is efficient and fast.\u00a0HTTP\/2<\/a> is almost here. The fun fact is that your browser most probably is already using HTTP\/2.<\/p>\n I ain’t no expert on this topic, which is why I won’t go into details, though, as James Spader<\/strong><\/em> would say in Boston Legal \u2014”I know enough to be dangerous”.<\/p><\/blockquote>\n If, like me, you develop WordPress themes, then here is what you really need to know. Hacks and performance fixes which we had for HTTP 1.1 will actually slow down your theme’s page loading speed in HTTP\/2<\/strong>.<\/p>\n How?<\/p>\n Why?<\/p>\n What?<\/p>\n Well, let’s see what makes HTTP\/2 so much better when compared with the 16 years older version.<\/p>\n In context of HTTP\/2 being rapidly accepted by browsers here’s what\u00a0you could be doing wrong in an ideal world with browsers, hosts and CDNs serving sites over \u00a0HTTP\/2<\/p>\n If you are developing a site which you know is going to be served over HTTP\/2\u00a0then don’t use any of these legacy performance hacks.<\/p><\/blockquote>\n Here’s the mini-cherry on top of the regular cherry on top of the sundae of awesomeness i.e. HTTP\/2 \u2014 A\u00a0few demos and implementations of HTTP\/2<\/p>\n There’s an excellent write-up<\/a> by Daniel Stenberg<\/em> going into much more detail available as a PDF.<\/p>\n We are at the verge of HTTP\/2 being introduced as a new standard. If you develop WP Themes being a front-end developer, you need to read this. Hacks and performance fixes which we had for HTTP 1.1 will actually slow down your theme’s page loading speed in HTTP\/2.<\/p>\n","protected":false},"author":2,"featured_media":989,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"webmentions_disabled_pings":false,"webmentions_disabled":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[10],"tags":[],"class_list":["post-962","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress"],"yoast_head":"\n\n
Why We Needed These Hacks?#<\/a><\/h3>\n
\n
Why HTTP\/2#<\/a><\/h2>\n
Advantages of HTTP\/2#<\/a><\/h2>\n
\n
What Can YOU<\/em> Be Doing Wrong?#<\/a><\/h2>\n
\n
I Want a Demo?#<\/a><\/h2>\n
\n
Which Browser Support HTTP\/2<\/span><\/h3>\n
\n
HTTP\/2 Support for HTTP\/HTTPS Servers<\/span><\/h3>\n
\n
What Is Your Take on This?#<\/a><\/h4>\n","protected":false},"excerpt":{"rendered":"