On this page, we present the recorded measurement data for our large scale assessment of global HTTP/2 adoption, based on
i) scanning the entire IPv4 address space and ii) the complete .com/.net/.org domains.

In our papers, we analyzed how HTTP/2 Server Push, a feature that promises to further reduce the page load time, is utilized in the wild. In the absence of standardization and recommendations for concrete strategies, we identified current undocumented practices having potential influence on page load time and network resource usage, and how this impacts the human perception.

Results & Publications

HTTP2 Adoption & User Peception

We publish HTTP/2 (Server Push) adoption statistics on this website on a regular basis. The lists of discovered HTTP/2 (push domains) can also be downloaded. Moreover, (concise) results of our study on end-user perception are also available.

Information on our methodology and further results can be found in the following publications:

Latest News

  • 2017-09-22: Apparently, Cloudflare reactivated Server Push for their customers, as observable in our Adoption Results.
  • 2017-09-08: We experience a significant drop in websites utilizing HTTP/2 Server Push among several data sets, most of them hosted by Cloudflare. Update: Cloudflare has temporarily deactivated the Server Push feature for maintenance (Source).
  • 2017-09-04: irs.gov is the first HTTP/2 Server Push capable .gov domain. irs.gov enabled HTTP/2 support on Wed, Aug 30th and started to push 2 stylesheets on Fri, Sep 1st. The site is hosted by Akamai.
  • 2017-09-03: We added the .at (incomplete zone!) set to our measurements.
  • 2017-05-17: We added the .gov set to our measurements.
  • 2017-05-06: Our paper A QoE Perspective on HTTP/2 Server Push got accepted at ACM SIGCOMM Internet-QoE 2017.
  • 2017-04-07: Our paper How HTTP/2 Pushes the Web: An Empirical Study of HTTP/2 Server Push got accepted at IFIP Networking 2017.
  • 2017-01: We started scanning various domain lists (Alexa 1M, .com, .net, .org, .fi, .se, .nu) and analyze the HTTP/2 (Server Push) Adoption.