Is the web ready for HTTP/2 server push?

Abstract

HTTP/2 supersedes HTTP/1.1 to tackle the performance challenges of the modern Web. A highly anticipated feature is Server Push, enabling servers to send data without explicit client requests, thus potentially saving time. Although guidelines on how to use Server Push emerged, measurements have shown that it can easily be used in a suboptimal way and hurt instead of improving performance. We thus tackle the question if the current Web can make better use of Server Push. First, we enable real-world websites to be replayed in a testbed to study the effects of different Server Push strategies. Using this, we next revisit proposed guidelines to grasp their performance impact. Finally, based on our results, we propose a novel strategy using an alternative server scheduler that enables to interleave resources. This improves the visual progress for some websites, with minor modifications to the deployment. Still, our results highlight the limits of Server Push: a deep understanding of web engineering is required to make optimal use of it, and not every site will benefit.

Modeling User-Centered Page Load Time for Smartphones

“…The motivation for designing muPLT est is to allow developers to scalably compare their page load optimizations with respect to a user-centered metric. To this end, we show how muPLT est can be used by developer in practice using a case study with the Server-Push [29,49] optimization. We show that developers can accurately evaluate different push strategies without requiring extensive user studies by using using muPLT est .…”

Measuring Web Quality of Experience in Cellular Networks

“…Server push reduces energy consumption, which is one of the challenges in provisioning better web performance and QoE for mobile devices. The authors [114] studied if the current web is ready for HTTP/2 server push.…”