Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

Overview of Web Application Performance Optimization Techniques

Juho Vepsäläinen, Arto Hellas, Petri Vuorimaa

TL;DR

This paper surveys the current landscape of web application performance, arguing that rapidly growing page sizes create wasted resources and lost conversions. It systematically analyzes performance aspects, techniques, and the influence of web frameworks, anchored by Core Web Vitals as a practical measurement frame. Key contributions include mapping techniques (rendering strategies, offloading, caching, tooling, and compression) to their impact on performance, and discussing how frameworks adopt or impede these optimizations, with attention to edge computing and local-first models. The work highlights the importance of measurement-driven development and suggests future directions for standardization and tooling to sustain performance gains across evolving web platforms. The practical impact lies in guiding developers and framework authors toward high-impact, implementable strategies that balance user experience, performance metrics, and architectural trade-offs in distributed, modern web applications.

Abstract

During its thirty years of existence, the World Wide Web has helped to transform the world and create digital economies. Although it started as a global information exchange, it has become the most significant available application platform on top of its initial target. One of the side effects of this evolution was perhaps suboptimal ways to deliver content over the web, leading to wasted resources and business through lost conversions. Technically speaking, there are many ways to improve the performance of web applications. In this article, we examine the currently available options and the latest trends related to improving web application performance.

Overview of Web Application Performance Optimization Techniques

TL;DR

This paper surveys the current landscape of web application performance, arguing that rapidly growing page sizes create wasted resources and lost conversions. It systematically analyzes performance aspects, techniques, and the influence of web frameworks, anchored by Core Web Vitals as a practical measurement frame. Key contributions include mapping techniques (rendering strategies, offloading, caching, tooling, and compression) to their impact on performance, and discussing how frameworks adopt or impede these optimizations, with attention to edge computing and local-first models. The work highlights the importance of measurement-driven development and suggests future directions for standardization and tooling to sustain performance gains across evolving web platforms. The practical impact lies in guiding developers and framework authors toward high-impact, implementable strategies that balance user experience, performance metrics, and architectural trade-offs in distributed, modern web applications.

Abstract

During its thirty years of existence, the World Wide Web has helped to transform the world and create digital economies. Although it started as a global information exchange, it has become the most significant available application platform on top of its initial target. One of the side effects of this evolution was perhaps suboptimal ways to deliver content over the web, leading to wasted resources and business through lost conversions. Technically speaking, there are many ways to improve the performance of web applications. In this article, we examine the currently available options and the latest trends related to improving web application performance.

Paper Structure

This paper contains 31 sections, 1 figure, 4 tables.

Table of Contents

  1. Introduction
  2. Aspects of Web Application Performance
  3. What is performance
  4. Search Engine Optimization
  5. Transport protocol
  6. Offloading work
  7. Impact of server latency on user experience
  8. Caching at different levels of development stack
  9. Overview of aspects of web performance
  10. Review of Web Application Performance Techniques
  11. Progressive enhancement
  12. HTML-first development
  13. Utility-first styling
  14. HTML-first state management
  15. Local-first software – shifting responsibilities between the client and the server
  16. ...and 16 more sections

Figures (1)

  • Figure 1: In the workflow, a developer is working that triggers a build on a CI server, which deploys build artifacts to a web server that then serves a website to a client using a standard request/response flow. Caching is possible at each phase of the flow. In addition, a web server may generate a page per request using SSR or return it from a cache using DPR or ISR. During a CI deployment, SSG may be performed. Optionally, a page may be rendered on the client by leveraging CSR. vepsalainen2023implications