Mitigating Redundant Data Transfers for Mobile Web Applications via App-Specific Cache Space

Redundant transfer of resources is a critical issue for compromising the performance of mobile Web applications (a.k.a., apps) in terms of data traffic, load time, and even energy consumption. Evidence shows that the current cache mechanisms are far from satisfactory. With lessons learned from how native apps manage their resources, in this paper, we propose the ReWAP approach to fundamentally reducing redundant transfers by restructuring the resource loading of mobile Web apps. ReWAP is based on an efficient mechanism of resource packaging where stable resources are encapsulated and maintained into a package, and such a package shall be loaded always from the local storage and updated by explicitly refreshing. By retrieving and analyzing the update of resources, ReWAP maintains resource packages that can accurately identify which resources can be loaded from the local storage for a considerably long period. ReWAP also provides a wrapper for mobile Web apps to enable loading and updating resource packages in the local storage as well as loading resources from resource packages. ReWAP can be easily and seamlessly deployed into existing mobile Web architectures with minimal modifications, and is transparent to end-users. We evaluate ReWAP based on continuous 15-day access traces of 50 mobile Web apps that suffer heavily from the problem of redundant transfers. Compared to the original mobile Web apps with cache enabled, ReWAP can significantly reduce the data traffic, with the median saving up to 51%. In addition, ReWAP can incur only very minor runtime overhead of the client-side browsers.

💡 Research Summary

The paper addresses a pervasive performance problem in mobile web applications: redundant data transfers that increase traffic, page load time, and energy consumption. Existing web caching mechanisms, which rely on browser‑wide cache spaces and developer‑specified expiration policies, often fail on mobile devices due to limited cache size, heuristic expiration, and common development practices such as appending random query strings to URLs. The authors categorize redundant transfers into three types: (RT1) resources evicted from cache because of space constraints, (RT2) resources incorrectly judged as expired due to poor cache configuration, and (RT3) resources requested with different URLs but identical content. Their prior measurements on the mobile versions of Alexa’s top‑100 sites showed that while over 70 % of resources could be cached for a day, actual cache hit rates were below 50 %.

Inspired by native applications, which separate static resources into an installable package and load them locally, the authors propose ReWAP (Resource‑Web‑App‑Packaging). ReWAP introduces a package‑based resource management model for web apps while preserving the benefits of the web’s incremental update model. The system consists of two main components: a Package Engine deployed on the server and a Wrapper that runs in the client browser.

The Package Engine continuously crawls an app, records all resource URLs, and estimates each resource’s update frequency. Resources that are stable (i.e., change rarely) are grouped into a resource package together with a manifest that lists version identifiers, hashes, and dependency information. The package is compressed and stored on the web server or CDN, ready for download.

The Wrapper intercepts the app’s entry point, checks whether a package is already present in the browser’s local storage (IndexedDB or Cache Storage), and verifies its version against the manifest served by the server. If the package is missing or outdated, the Wrapper downloads the new package, stores it locally, and then serves subsequent requests for any resource listed in the manifest directly from local storage, bypassing the network. Dynamic resources (e.g., API responses, personalized content) continue to be fetched through the normal browser cache pipeline, so existing application logic does not need to be rewritten.

Key advantages of this design are: (1) App‑specific cache space – each web app gets its own isolated storage, eliminating cross‑app cache eviction; (2) Batch update semantics – the entire static set is refreshed in one operation, removing the need for fine‑grained cache‑control headers; (3) Transparency – end users see no UI change, and developers only need to add a small script tag that redirects to the Wrapper.

The authors evaluated ReWAP on 50 real mobile web apps (news, e‑commerce, social media) using 15 days of actual user access logs. Compared with the baseline of standard browser caching, ReWAP achieved a median traffic reduction of 51 % and a maximum reduction close to 100 %. The additional client‑side overhead was negligible: page‑load time increased by less than 5 ms on average, and CPU/memory usage rose by only 1–2 %.

Limitations discussed include the cost of generating and distributing packages, especially for very large apps, and the potential for duplicate storage when multiple pages share the same resources (the current implementation treats each page independently). The authors suggest future work on hierarchical packaging (global vs. page‑level packages) and machine‑learning models to predict resource volatility more accurately, which could further shrink package size and update frequency.

In related work, the paper contrasts ReWAP with prior efforts that focus on improving individual cache headers, service‑worker prefetching, or resource hinting. Those approaches still operate within the browser’s shared cache and cannot guarantee that a stable resource will stay cached across visits. ReWAP’s package‑centric approach fundamentally changes the resource lifecycle, offering native‑app‑like guarantees while remaining fully compatible with existing web infrastructure (HTTPS, CDNs, service workers).

In conclusion, ReWAP demonstrates that a modest, server‑side packaging engine combined with a lightweight client wrapper can dramatically cut redundant data transfers in mobile web apps, with minimal impact on performance and developer effort. The approach paves the way for more efficient mobile web experiences, especially as web applications continue to grow in size and complexity. Future extensions that automate package granularity and integrate predictive analytics could make ReWAP a standard component of mobile web deployment pipelines.