Just imagine: a web server sending resources to a web browser before the later has even got the chance to explicitly request for them! Yes, I'm talking about the HTTP/2 server push instant performance-booster! And it's precisely this kind of "latency killers” that you, a performance-minded Drupal developer must be "hunting for", right? Well, let me explain to you how it works exactly, what planning it requires and how it impacts a site's performance: First of all I need to put the spotlight on the two main "culprits" for the version 2 of the HTTP's protocol's impact on a web page's load time...