Show HN: Dependency-based prioritization makes HTTP/2 much faster than SPDY

Are your timings based off of a single run each for Firefox and Chrome? The web is a very noisy place; to get good timing data you need to run many tests. WebPageTest (www.webpagetest.org) can be a good way to do this.<p>(I work on PageSpeed, and we need to run tests like this often.)

Seems like there is still a significant amount of initial latency by waiting for the first-byte of the HTML before making the subsequent requests for the dependent resources.<p>To actually minimize latency the server should understand what resources the HTML file is dependent on, and eagerly send those in addition to the request resource. i.e.<p><pre><code> client: send me index.html and dependent resources server: here is index.html, along with other initial resources you didn&#x27;t ask for but will need </code></pre> This avoids the latency of the second round-trip time to ask for dependent resources. Does anyone know if HTTP&#x2F;2 allows for a scheme like this?

I&#x27;m not sure I&#x27;m reaching the same conclusion.<p>- Chrome is taking 618ms to load &#x2F; vs 412 ms on FF.<p>- FF loads all the .css &amp; .js at 320ms as well as first 8 imgs<p>- CH loads all the .css &amp; .js at ~600ms as well as first 8 imgs<p>Before chalking up the advantage to dependency-based prioritization (which may be a good thing-I don&#x27;t know) I would first explain why fetching &quot;&#x2F;&quot; is so much slower on chrome.