How Far Can Client-Only Solutions Go for Mobile Browser Speed? 1Zhen Wang, 2Felix Xiaozhu Lin, 1,2Lin Zhong, and 3Mansoor Chishtie 1Dept. of ECE and 2Dept. of CS, Rice University, Houston, TX, and 3Texas Instruments, Dallas, TX 1,2{zhen.wang, xzl, lzhong}@rice.edu and
[email protected] ABSTRACT the failure of Amazon Web Services’ cloud-computing infrastruc- Mobile browser is known to be slow because of the bottleneck in ture [17] took many websites down. Finally, solutions based on resource loading. Client-only solutions to improve resource load- proxy support violate end-to-end security, which is crucial to se- ing are attractive because they are immediately deployable, scala- cure websites. ble, and secure. We present the first publicly known treatment of Not surprisingly, solutions that do not rely on infrastructure sup- client-only solutions to understand how much they can improve port, or client-only solutions, are particularly attractive because mobile browser speed without infrastructure support. Leveraging they are immediately deployable, scalable, and secure. While an unprecedented set of web usage data collected from 24 iPhone client-only solutions are likely to be less effective than those leve- users continuously over one year, we examine the three funda- raging infrastructure supports, it has been an open question how mental, orthogonal approaches a client-only solution can take: effective client-only solutions can be for mobile browsers. The caching, prefetching, and speculative loading. Speculative load- challenge to answering this question has been the lack of data ing, as is firstly proposed and studied in this work, predicts and regarding the browsing behavior of mobile users.