Pith. sign in

REVIEW 3 major objections 6 minor 85 references

Overview of Web Application Performance Optimization Techniques

T0 review · 3 major / 6 minor · reviewed 2026-08-11 · deepseek-v4-flash

Challenge this review Re-run · record.json Download PDF Read on arXiv ↗ Review JSON

Pith's one-line read The paper finds surprisingly many ways to speed up web applications and maps them against Google's Core Web Vitals.

desk verdict A solid, current narrative review of web performance techniques; the Core Web Vitals premise is explicit rather than hidden, so the main soft spot is the lack of a stated selection methodology, not the premise itself. read the letter →

arxiv 2412.07892 v1 pith:2COF3ARL submitted 2024-12-10 cs.SE cs.ETcs.PF

Juho Vepsäläinen , Arto Hellas , Petri Vuorimaa This is my paper · ORCID
classification cs.SEcs.ETcs.PF
keywords webapplicationperformanceCoreVitalsprogressiveenhancementlocal-firstsoftwarepartialloadingdeadcodeeliminationcompressionframeworks
verification ladder T0 review T1 audit T2 compute T3 formal

The pith

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The reading

This review asks what ways are currently available for improving web application performance, and answers that there are surprisingly many. It organizes the options around four performance aspects—server latency, transport protocol, offloading work, and caching—then surveys nine technique families: progressive enhancement, HTML-first development, utility-first styling, HTML-first state management, local-first software, partial loading, performance tooling, dead code elimination, and compression. The paper argues that Google's Core Web Vitals provide a good approximation of what web performance means, and that web frameworks both codify best practices and risk staying conservative. If the review is right, developers have a structured map of existing levers, and frameworks can be compared by which levers they build in.

What carries the argument

The organizing mechanism is a classification: a table of performance aspects (server latency, transport protocol, offloading work, caching) paired with a table of technique families (progressive enhancement, HTML-first development, utility-first styling, HTML-first state management, local-first software, partial loading, performance tooling, dead code elimination, compression). Google's Core Web Vitals serve as the yardstick, defining which performance targets the techniques are evaluated against. The client-server request flow, with caching possible at each stage, is the architectural picture that ties the aspects together.

What would settle it

A concrete check would be to measure a set of real web applications where Core Web Vitals are good but users report poor experience or business conversion is low, or where a technique that improves a non-Vital aspect such as offline capability or battery usage worsens Vitals. Such cases would show that Core Web Vitals are not a complete proxy for web performance as experienced by users.

Watch

Extended reading notes

Core claim

The central claim is that the currently available ways for improving web application performance are numerous and diverse, and that Google's Core Web Vitals give a good approximation of the performance aspects these techniques target. The survey treats performance as multifaceted, covering loading speed, interactivity, visual stability, and time to first byte, and it catalogs techniques that range from markup-first development strategies to moving work off the main thread, deferring code, eliminating dead code, and compressing payloads. It also observes that frameworks influence how—and whether—these techniques reach developers, since mainstream frameworks may favor developer experience over user experience while newer 'disappearing frameworks' push performant defaults.

Load-bearing premise

The review's map is only as good as the premise that Google's Core Web Vitals capture the main aspects of web application performance, a premise the paper states but does not empirically defend.

Editorial extensions

If this is right

  • Developers can choose from at least nine distinct optimization directions, several of which are compatible and can be combined without abandoning an existing stack.
  • Frameworks can be assessed by which techniques they bake in—rendering approach, partial loading, tooling, dead code elimination, and compression—rather than by brand or popularity.
  • Because the review treats performance as multidimensional, improving one Core Web Vital does not guarantee improvement in another, so optimization must be metric-aware.
  • The shift from FID to INP in Core Web Vitals shows that the measuring standard itself changes, which will redirect where optimization effort is spent.
  • The survey's list is explicitly non-exhaustive, suggesting that new techniques will keep reshaping the performance landscape.

Reading between the lines

Editorial extensions of the paper, not claims the author makes directly.

  • Editorial inference: the paper's own Pareto remark hints that a small set of levers—likely payload size and render-blocking—accounts for most practical gains; this could be tested by measuring the marginal contribution of each technique family on a benchmark corpus.
  • Editorial inference: if Core Web Vitals are not a complete proxy for user experience, techniques that improve non-Vital aspects such as offline behavior, battery use, or perceived responsiveness may be underweighted in framework adoption.
  • Editorial inference: the 'what you measure is what you get' observation suggests that search-engine visibility creates evolutionary pressure on both frameworks and techniques, so changes to the metrics could steer the entire web platform's direction.
  • Editorial inference: the local-first shift carries consequences beyond latency, including data ownership and privacy, which the paper notes but does not develop into evaluation criteria.
Share X Bluesky LinkedIn Reddit HN

Signed reviews

No signed human review yet.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, and a circularity audit.

Referee Report

3 major / 6 minor

Summary. This paper is a narrative overview of techniques for improving web application performance. It frames the topic through Google's Core Web Vitals, presenting LCP, FCP, FID, INP, CLS, and TTFB as the relevant metrics (§2.1, Table 1), and discusses latency, transport protocol, offloading work, caching, and several modern development approaches including progressive enhancement, HTML-first development, utility-first styling, HTML-first state management, local-first software, partial loading, performance tooling, dead code elimination, and compression (§3). It then surveys how web frameworks relate to these techniques (§4, Table 4) and concludes that there are many available ways to improve performance and that Web Vitals provide a good approximation of web performance (§6).

Significance. If corrected, the paper would be a useful and accessible synthesis for practitioners and researchers who want a compact map of current optimization directions. Its strengths are the breadth of recent topics covered, the useful summary tables, and the inclusion of current support statistics and evolving standards (e.g., Brotli, WebP, INP). It does not claim new empirical results and explicitly notes that its list is likely non-exhaustive. However, the paper's organizing premise is not sufficiently supported: the identification of Core Web Vitals is factually imprecise, and the claim that they approximate web performance is asserted without empirical backing. Because the scope of the survey depends on this premise, the manuscript needs revision before the synthesis can be fully relied upon.

major comments (3)
  1. [§2.1 and Table 1] The statement that 'Google evaluates the following six parameters known as Core Web Vitals to rank site speed: LCP, FCP, FID, INP, CLS, and TTFB' is inaccurate. Google's Core Web Vitals are LCP, INP, and CLS; the others are Web Vitals but not part of the Core Web Vitals set. Since the paper organizes its entire scope around this notion, the error is load-bearing and should be corrected, with Table 1 and the surrounding discussion aligned to the actual distinction.
  2. [§2.1 and Conclusion (§6)] The claim that Core Web Vitals 'capture the main aspects of web application performance' and later 'provide a good approximation' of performance is a load-bearing assumption, but the cited sources [78]–[83] are metric documentation pages, not empirical validation studies linking these metrics to user experience, task success, or business outcomes. Please either add supporting evidence or explicitly reframe this as a working assumption, and acknowledge performance aspects not covered by Core Web Vitals (such as energy consumption, memory footprint, accessibility, and server-side cost).
  3. [Introduction and Discussion] The paper poses a research question about 'currently available ways' to improve web performance, but no literature search or inclusion methodology is described. The resulting coverage is therefore a narrative selection rather than a systematic answer, and this limitation is only implied by the statement that the list is non-exhaustive. Please add a brief methodological note in the Introduction or Discussion that acknowledges the non-systematic nature of the survey and the risk that relevant techniques or studies may be under-represented.
minor comments (6)
  1. [Table 3, Compression row] The 'Related examples' cell lists '[24]' where the text in §3.9 correctly names 'gzip [24]'; please fix the table entry to name gzip explicitly.
  2. [Table 1, FID row] The phrase 'can be considered an obsolete [80]' is ungrammatical; it should read 'can be considered obsolete [80]'.
  3. [First page note] The venue name 'Lecture Notes in Business Processing (LNBIP)' is a typo; the correct name is 'Lecture Notes in Business Information Processing'.
  4. [§3.3] The statement that generated CSS from utility-first styling is 'generally a tiny amount compared to conventional techniques according to our experience' presents a personal observation as a general claim; please mark it explicitly as the authors' experience or add a supporting reference.
  5. [§2.6] The transition 'Developers exist at the other extreme' is confusing; rephrase to clarify the developer's position in the workflow described by Figure 1.
  6. [Reference [50]] The page range '291–401' appears implausibly long; please verify and correct the page numbers for the SANER 2018 paper.

Circularity Check

0 steps flagged · score 2.0 of 10

No significant circularity: the survey's technique catalogue is assembled from external literature, self-citations are descriptive rather than derivation-load-bearing, and the Web Vitals framing is a scope assumption rather than a circular reduction.

full rationale

This paper is a literature review whose central answer (that many web performance optimization techniques exist) is supported by an enumeration of techniques each tied to external sources such as [37], [76], [77], [83], and others; no equation, fitted parameter, or derived prediction appears anywhere in the text. The self-citations ([70]-[74]) are used to name and describe concepts (disappearing frameworks, resumability, Gustwind, edge-computing implications for SSG, islands architecture), but none of these is load-bearing for the conclusion: even if those prior works were absent, the survey would still contain a substantial catalogue of independently cited techniques. The claim in the Conclusion that "Google's Core Web Vitals provide a good approximation" restates the Section 2.1 scope assumption that "we will focus on Google's Core Web Vitals in this discussion as they capture the main aspects of web application performance"; this is an unvalidated premise about the chosen performance proxy, not a derived result, and it does not force the enumeration because the techniques were not derived from the metrics. The paper also honestly acknowledges scope limitations (e.g., not considering which techniques individual developers should apply), which further indicates the review is an organized survey rather than a self-justifying derivation. Thus there is no circular step that reduces a claimed result to its own input; the minor self-citations are not load-bearing and the Web Vitals proxy concern belongs to correctness risk, not circularity.

Assumptions & free parameters 0 free parameters · 3 assumptions · 0 invented entities

The paper introduces no free parameters or invented entities. It rests on domain assumptions about what constitutes web performance (Core Web Vitals), the scope of the web model (client-server), and the representativeness of the surveyed techniques.

assumptions (3)
  • domain assumption Google's Core Web Vitals provide a good approximation of web application performance.
    Adopted in Section 2.1 and the Conclusion without empirical defense; the review's organization of performance aspects relies on this premise.
  • domain assumption The client-server model is the mainstream model of the web and the focus of the review.
    Section 2 states that decentralized options such as peer-to-peer computing are out of scope.
  • domain assumption The selected set of techniques and sources is representative of 'currently available options'.
    No systematic literature search or selection criteria is described, so representativeness is assumed.

how reviews work

0 comments
Cite this review

Pith. "Pith review of Overview of Web Application Performance Optimization Techniques." pith.science (2026). https://pith.science/paper/2COF3ARL

@misc{pith2026241207892,
  author       = {Pith},
  title        = {Pith review of: Overview of Web Application Performance Optimization Techniques},
  year         = {2026},
  howpublished = {\url{https://pith.science/paper/2COF3ARL}},
  note         = {Machine review of arXiv:2412.07892}
}
read the original 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.

Figures

Figures reproduced from arXiv: 2412.07892 by the authors.

Figure 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,… view at source ↗

Discussion (0). Continue with ORCID to comment.

Reference graph

Works this paper leans on

85 extracted references · 79 canonical work pages

  1. [24]

    In: Proceedings of the third ACM international conference on Web search and data mining

    Ferragina, P., Manzini, G.: On compressing the textual web. In: Proceedings of the third ACM international conference on Web search and data mining. pp. 391–400 (2010)

    work page 2010

  2. [78]

    https://web.dev/articles/inp (2023), [Accessed 13-02-2024]

    Wagner, J.: Interaction to Next Paint (INP). https://web.dev/articles/inp (2023), [Accessed 13-02-2024]

    work page 2023

  3. [83]

    https://web.dev/articles/vitals (2024), [Accessed 12-02- 2024]

    Walton, P.: Web Vitals. https://web.dev/articles/vitals (2024), [Accessed 12-02- 2024]

    work page 2024

  4. [1]

    Master’s thesis, University of Oslo (2016)

    Akse, J.A.: Applying client-side state management on server-generated web pages. Master’s thesis, University of Oslo (2016)

    2016

  5. [2]

    Google Inc pp

    Alakuijala,J.,Kliuchnikov,E.,Szabadka,Z.,Vandevenne,L.:Comparisonofbrotli, deflate, zopfli, lzma, lzham and bzip2 compression algorithms. Google Inc pp. 1–6 (2015)

    2015

  6. [3]

    In: Applications of Digital Image Processing XLII

    Alakuijala, J., Van Asseldonk, R., Boukortt, S., Bruse, M., Coms,a, I.M., Firsching, M., Fischbacher, T., Kliuchnikov, E., Gomez, S., Obryk, R., et al.: Jpeg xl next- generation image compression architecture and coding tools. In: Applications of Digital Image Processing XLII. vol. 11137, pp. 112–124. SPIE (2019)

    2019

  7. [4]

    https://angular.io/ (2024), [Accessed 18-03-2024]

    Angular — angular.io. https://angular.io/ (2024), [Accessed 18-03-2024]

    2024

  8. [5]

    In: Proceedings of the ACM Internet Measurement Conference

    Aqeel, W., Chandrasekaran, B., Feldmann, A., Maggs, B.M.: On landing and in- ternal web pages: The strange case of jekyll and hyde in web performance measure- ment. In: Proceedings of the ACM Internet Measurement Conference. pp. 680–695 (2020)

    2020

Show all 85 references
  1. [6]

    https://astro.build/ (2024), [Accessed 18-03-2024]

    Astro. https://astro.build/ (2024), [Accessed 18-03-2024]

    2024

  2. [7]

    js: A fast compiler-augmented virtual dom for the web

    Bai, A.: Million. js: A fast compiler-augmented virtual dom for the web. In: Pro- ceedings of the 38th ACM/SIGAPP Symposium on Applied Computing. pp. 1813– 1820 (2023)

    2023

  3. [8]

    ACM Transactions on Information Systems (TOIS)36(2), 1–42 (2017)

    Bai, X., Arapakis, I., Cambazoglu, B.B., Freire, A.: Understanding and leveraging the impact of response latency on user behaviour in web search. ACM Transactions on Information Systems (TOIS)36(2), 1–42 (2017)

    2017

  4. [9]

    Journal of Organizational Computing and Electronic Commerce 31(1), 1–17 (2021)

    Basalla, M., Schneider, J., Luksik, M., Jaakonmäki, R., Vom Brocke, J.: On latency of e-commerce platforms. Journal of Organizational Computing and Electronic Commerce 31(1), 1–17 (2021)

    2021

  5. [10]

    Internet Research (1992)

    Berners-Lee, T., Cailliau, R., Groff, J.F., Pollermann, B.: World-wide web: the information universe. Internet Research (1992)

    1992

  6. [11]

    https://partytown.builder.io/ (2024), [Accessed 13-02-2024]

    Introduction - Partytown — partytown.builder.io. https://partytown.builder.io/ (2024), [Accessed 13-02-2024]

    2024

  7. [12]

    Support tables for HTML5, CSS3, etc — caniuse.com

    Can I use... Support tables for HTML5, CSS3, etc — caniuse.com. https://canius e.com/?search=web%20workers, [Accessed 13-02-2024]

    2024

  8. [13]

    Support tables for HTML5, CSS3, etc — caniuse.com

    Can I use... Support tables for HTML5, CSS3, etc — caniuse.com. https://canius e.com/?search=brotli (2024), [Accessed 12-02-2024]

    2024

  9. [14]

    Support tables for HTML5, CSS3, etc — caniuse.com

    Can I use... Support tables for HTML5, CSS3, etc — caniuse.com. https://canius e.com/?search=webp (2024), [Accessed 12-02-2024]

    2024

  10. [15]

    Support tables for HTML5, CSS3, etc — caniuse.com

    Can I use... Support tables for HTML5, CSS3, etc — caniuse.com. https://canius e.com/?search=jpeg%20xl (2024), [Accessed 16-02-2024]

    2024

  11. [16]

    In: Proceedings of the Sixteenth European Conference on Computer Systems

    Chen, X., Song, H., Jiang, J., Ruan, C., Li, C., Wang, S., Zhang, G., Cheng, R., Cui, H.: Achieving low tail-latency and high scalability for serializable transac- tions in edge computing. In: Proceedings of the Sixteenth European Conference on Computer Systems. pp. 210–227 (2...

    2021

  12. [17]

    Chinprutthiwong, P., Vardhan, R., Yang, G., Zhang,Y., Gu, G.:Theservice worker hiding in your browser: The next web attack target? In: Proceedings of the 24th International Symposium on Research in Attacks, Intrusions and Defenses. pp. 312–323 (2021)

    2021

  13. [18]

    Technological Forecasting and Social Change108, 28–41 (2016)

    Dedehayir, O., Steinert, M.: The hype cycle model: A review and future directions. Technological Forecasting and Social Change108, 28–41 (2016)

    2016

  14. [19]

    https://www.djangoproject.com/ (2024), [Accessed 18-03-2024]

    Django. https://www.djangoproject.com/ (2024), [Accessed 18-03-2024]

    2024

  15. [20]

    Dunford, R., Su, Q., Tamang, E.: The pareto principle (2014)

    2014

  16. [21]

    https://elixir-lang.org/ (2024), [Accessed 18- 03-2024]

    The Elixir programming language. https://elixir-lang.org/ (2024), [Accessed 18- 03-2024]

    2024

  17. [22]

    https://enhance.dev/ (2024), [Accessed 18-03-2024]

    Enhance: Enhance. https://enhance.dev/ (2024), [Accessed 18-03-2024]

    2024

  18. [23]

    Future Generation of Communication and Internet of Things1(4), 52–57 (2022)

    Eslamdoust, A.: An overview of search engine optimization techniques. Future Generation of Communication and Internet of Things1(4), 52–57 (2022)

    2022

  19. [25]

    https://github.com/vercel/next.js/is sues/3632 (2018), [Accessed 18-03-2024]

    How to minify a next js app· Issue #3632. https://github.com/vercel/next.js/is sues/3632 (2018), [Accessed 18-03-2024]

    2018

  20. [26]

    New Riders (2015)

    Gustafson, A.: Adaptive web design: crafting rich experiences with progressive enhancement. New Riders (2015)

    2015

  21. [27]

    https://rubyonrails.org/ (2024), [Accessed 18-03- 2024]

    Hansson, D.H.: Ruby on Rails. https://rubyonrails.org/ (2024), [Accessed 18-03- 2024]

    2024

  22. [28]

    https://svelte.dev/ (2024), [Accessed 18-03-2024]

    Harris, R.: Svelte. https://svelte.dev/ (2024), [Accessed 18-03-2024]

    2024

  23. [29]

    https://html-first.com/ (2024), [Accessed 12-02-2024]

    HTML First. https://html-first.com/ (2024), [Accessed 12-02-2024]

    2024

  24. [30]

    https://htmx.org/ (2024), [Accessed 18-03-2024]

    htmx - high power tools for html. https://htmx.org/ (2024), [Accessed 18-03-2024]

    2024

  25. [31]

    https://almanac.httparchive.org/en/2022/page-weight (2022), [Accessed 28-08-2023]

    Page Weight | 2022. https://almanac.httparchive.org/en/2022/page-weight (2022), [Accessed 28-08-2023]

    2022

  26. [32]

    In: The World Wide Web Conference

    Ikram, M., Masood, R., Tyson, G., Kaafar, M.A., Loizon, N., Ensafi, R.: The chain of implicit trust: An analysis of the web third-party resources loading. In: The World Wide Web Conference. pp. 2851–2857 (2019)

    2019

  27. [33]

    https://ec.europa.eu/commission/presscor ner/detail/en/ip_23_3718 (2023), [Accessed 25-01-2024]

    Johannes Bahrke, T.R.: Press corner. https://ec.europa.eu/commission/presscor ner/detail/en/ip_23_3718 (2023), [Accessed 25-01-2024]

    2023

  28. [34]

    O’Reilly Media, Inc

    Killelea, P.: Web Performance Tuning: speeding up the web. " O’Reilly Media, Inc." (2002)

    2002

  29. [35]

    https://github.com/automerge/trell is (2024), [Accessed 18-03-2024]

    Kleppmann, M.: GitHub - automerge/trellis. https://github.com/automerge/trell is (2024), [Accessed 18-03-2024]

    2024

  30. [36]

    arXiv preprint arXiv:2402.03239 (2024)

    Kleppmann, M., Frazee, P., Gold, J., Graber, J., Holmgren, D., Ivy, D., Johnson, J., Newbold, B., Volpert, J.: Bluesky and the at protocol: Usable decentralized social media. arXiv preprint arXiv:2402.03239 (2024)

    2024 arXiv

  31. [37]

    In: Proceedings of the 2019 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software

    Kleppmann, M., Wiggins, A., Van Hardenberg, P., McGranaghan, M.: Local-first software: you own your data, in spite of the cloud. In: Proceedings of the 2019 ACM SIGPLAN International Symposium on New Ideas, New Paradigms, and Reflections on Programming and Software. pp. 154–178 (2019)

    2019

  32. [38]

    Bachelor’s thesis, Hochschulbibliothek der Technischen Hochschule Köln (2021)

    Klimm, M.C.: Design Systems For Micro Frontends-An Investigation Into The De- velopment Of Framework-Agnostic Design Systems Using Svelte And Tailwind Css. Bachelor’s thesis, Hochschulbibliothek der Technischen Hochschule Köln (2021)

    2021

  33. [39]

    Authorea Preprints (2023)

    Korpal, G., Scott, D.: Decentralization and web3 technologies. Authorea Preprints (2023)

    2023

  34. [40]

    a case study of a map application

    Król, K.: Comparative analysis of selected online tools for javascript code mini- fication. a case study of a map application. Geomatics, Landmanagement and Landscape (2), 119–129 (2020) 18 J. Vepsäläinen et al

    2020

  35. [41]

    https://livewire.laravel.com/docs/alpine (2024), [Accessed 18-03-2024]

    Alpine | Laravel — livewire.laravel.com. https://livewire.laravel.com/docs/alpine (2024), [Accessed 18-03-2024]

    2024

  36. [42]

    In: Proceedings of the 16th ACM SIGSOFT international symposium on foundations of software engineering

    Livshits, B., Kiciman, E.: Doloto: Code splitting for network-bound web 2.0 appli- cations. In: Proceedings of the 16th ACM SIGSOFT international symposium on foundations of software engineering. pp. 350–360 (2008)

    2008

  37. [43]

    IEEE Transactions on Software Engineering (2023)

    Malavolta, I., Nirghin, K., Scoccia, G.L., Romano, S., Lombardi, S., Scanniello, G., Lago, P.: Javascript dead code identification, elimination, and empirical as- sessment. IEEE Transactions on Software Engineering (2023)

    2023

  38. [44]

    Available at SSRN 1152412 (2008)

    Morris, J.J., Alam, P.: Analysis of the dot-com bubble of the 1990s. Available at SSRN 1152412 (2008)

    2008

  39. [45]

    https://mswjs.io/ (2024), [Accessed 13-02-2024]

    Mock Service Worker. https://mswjs.io/ (2024), [Accessed 13-02-2024]

    2024

  40. [46]

    In: 13th USENIX Symposium on Net- worked Systems Design and Implementation (NSDI 16) (2016)

    Netravali, R., Goyal, A., Mickens, J., Balakrishnan, H.: Polaris: Faster page loads using fine-grained dependency tracking. In: 13th USENIX Symposium on Net- worked Systems Design and Implementation (NSDI 16) (2016)

    2016

  41. [47]

    https://nextjs.org/ (2024), [Accessed 18-03-2024]

    Next.js by Vercel. https://nextjs.org/ (2024), [Accessed 18-03-2024]

    2024

  42. [48]

    https://nextjs.org/docs/app/api-reference/nex t-config-js/compress (2024), [Accessed 18-03-2024]

    next.config.js Options: compress. https://nextjs.org/docs/app/api-reference/nex t-config-js/compress (2024), [Accessed 18-03-2024]

    2024

  43. [49]

    ACM SIGOPS Operating Systems Review 44(3), 2–19 (2010)

    Nygren, E., Sitaraman, R.K., Sun, J.: The akamai network: a platform for high- performance internet applications. ACM SIGOPS Operating Systems Review 44(3), 2–19 (2010)

    2010

  44. [50]

    Obbink, N.G., Malavolta, I., Scoccia, G.L., Lago, P.: An extensible approach for tamingthechallengesofjavascriptdeadcodeelimination.In:2018IEEE25thInter- national Conference on Software Analysis, Evolution and Reengineering (SANER). pp. 291–401. IEEE (2018)

    2018

  45. [51]

    IOSR Journal of Computer Engineering 16(1), 67–71 (2014)

    Oluwatosin, H.S.: Client-server model. IOSR Journal of Computer Engineering 16(1), 67–71 (2014)

    2014

  46. [52]

    https://open-ui.org/ (2024), [Accessed 18-03-2024]

    Open UI. https://open-ui.org/ (2024), [Accessed 18-03-2024]

    2024

  47. [53]

    In: 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering

    Pan, Y., White, J., Sun, Y., Gray, J.: Gray computing: An analysis of computing with background javascript tasks. In: 2015 IEEE/ACM 37th IEEE International Conference on Software Engineering. vol. 1, pp. 167–177. IEEE (2015)

    2015

  48. [54]

    https://www.phoenixframework.org/ (2024), [Accessed 18-03-2024]

    Phoenix Framework. https://www.phoenixframework.org/ (2024), [Accessed 18-03-2024]

    2024

  49. [55]

    https://alpinejs.dev/ (2024), [Accessed 18-03-2024]

    Porzio, C.: Alpine.js. https://alpinejs.dev/ (2024), [Accessed 18-03-2024]

    2024

  50. [56]

    In: Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security

    Rack, J., Staicu, C.A.: Jack-in-the-box: An empirical study of javascript bundling on the web and its security implications. In: Proceedings of the 2023 ACM SIGSAC Conference on Computer and Communications Security. pp. 3198–3212 (2023)

    2023

  51. [57]

    https://react.dev/ (2024), [Accessed 18-03-2024]

    React. https://react.dev/ (2024), [Accessed 18-03-2024]

    2024

  52. [58]

    Computer50(1), 30–39 (2017)

    Satyanarayanan, M.: The emergence of edge computing. Computer50(1), 30–39 (2017)

    2017

  53. [59]

    In: Proceedings of the 14th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM)

    Scoccia, G.L., Autili, M.: Web frameworks for desktop apps: an exploratory study. In: Proceedings of the 14th ACM/IEEE International Symposium on Empirical Software Engineering and Measurement (ESEM). pp. 1–6 (2020)

    2020

  54. [60]

    In: 2022 8th International Conference on Smart Structures and Systems (ICSSS)

    Sellamuthu, K., Ranjithkumar, S., Kavitha, K., Gowtham, S.: On page seo tech- niques for better ranking in search engines. In: 2022 8th International Conference on Smart Structures and Systems (ICSSS). pp. 01–06. IEEE (2022)

    2022

  55. [61]

    In: Advanced graphic com- munications, packaging technology and materials

    Si, Z., Shen, K.: Research on the webp image format. In: Advanced graphic com- munications, packaging technology and materials. pp. 271–277. Springer (2016)

    2016

  56. [62]

    Automation of technological and business processes 10(1) (2018) Overview of Web Application Performance Optimization Techniques 19

    Solovei, V., Olshevska, O., Bortsova, Y.: The difference between developing sin- gle page application and traditional web application based on mechatronics robot laboratory onaft application. Automation of technological and business processes 10(1) (2018) Overview of Web Appli...

    2018

  57. [63]

    In: 2012 USENIX Annual Tech- nical Conference (USENIX ATC 12)

    Song, X., Shi, J., Chen, H., Zang, B.: Revisiting software{Zero-Copy} for web- caching applications with twin memory allocation. In: 2012 USENIX Annual Tech- nical Conference (USENIX ATC 12). pp. 355–360 (2012)

    2012

  58. [64]

    Communications of the ACM 51(12), 36–41 (2008)

    Souders, S.: High-performance web sites. Communications of the ACM 51(12), 36–41 (2008)

    2008

  59. [65]

    https://www.statista.com/sta tistics/617136/digital-population-worldwide/ (2023), [Accessed 28-08-2023]

    Internet and social media users in the world 2023. https://www.statista.com/sta tistics/617136/digital-population-worldwide/ (2023), [Accessed 28-08-2023]

    2023

  60. [66]

    https://tailwindcss.com/ (2024), [Accessed 18-03-2024]

    Tailwind CSS. https://tailwindcss.com/ (2024), [Accessed 18-03-2024]

    2024

  61. [67]

    In: 2011 37th EUROMICRO Conference on Software Engineering and Ad- vanced Applications

    Taivalsaari, A., Mikkonen, T.: The web as an application platform: The saga con- tinues. In: 2011 37th EUROMICRO Conference on Software Engineering and Ad- vanced Applications. pp. 170–174. IEEE (2011)

    2011

  62. [68]

    https://twind.style/ (2024), [Accessed 18-03-2024]

    Tandel, S.: Twind.style. https://twind.style/ (2024), [Accessed 18-03-2024]

    2024

  63. [69]

    International Journal of Innovative Research in Science, Engineering and Technol- ogy 7(9), 9439–9444 (2018)

    Tandel, S., Jamadar, A.: Impact of progressive web apps on web app development. International Journal of Innovative Research in Science, Engineering and Technol- ogy 7(9), 9439–9444 (2018)

    2018

  64. [70]

    In: International Conference on Web Engineering

    Vepsäläinen, J., Hellas, A., Vuorimaa, P.: The rise of disappearing frameworks in web development. In: International Conference on Web Engineering. pp. 319–326. Springer (2023)

    2023

  65. [71]

    IEEE Access (2024)

    Vepsäläinen, J., Hevery, M., Vuorimaa, P.: Resumability-a new primitive for de- veloping web applications. IEEE Access (2024)

    2024

  66. [72]

    https://gustwind.js.org/ (2024), [Accessed 18-03-2024]

    Vepsäläinen, J.: Gustwind. https://gustwind.js.org/ (2024), [Accessed 18-03-2024]

    2024

  67. [73]

    In: WEBIST 2023: 19th International Conference on Web Infor- mation Systems and Technologies

    Vepsäläinen, J., Hellas, A., Vuorimaa, P.: Implications of edge computing for static site generation. In: WEBIST 2023: 19th International Conference on Web Infor- mation Systems and Technologies. pp. 223–231. Springer (2023)

    2023

  68. [74]

    In: WEBIST 2023: 19th International Conference on Web Information Systems and Technologies

    Vepsäläinen, J., Hellas, A., Vuorimaa, P.: The state of disappearing frameworks in 2023. In: WEBIST 2023: 19th International Conference on Web Information Systems and Technologies. Springer (2023)

    2023

  69. [75]

    Computing Systems8(1), 61–91 (1995)

    Viles, C.L., French, J.C.: Availability and latency of world wide web information servers. Computing Systems8(1), 61–91 (1995)

    1995

  70. [76]

    In: Companion Proceedings of the ACM Web Conference 2023

    Vogel, L., Springer, T.: How streaming can improve the world (wide web). In: Companion Proceedings of the ACM Web Conference 2023. pp. 140–143 (2023)

    2023

  71. [77]

    (eds.) Web Engineering

    Vogel, L., Springer, T.: Waiter and autratac: Don’t throw it away, just delay! In: Garrigós, I., Murillo Rodríguez, J.M., Wimmer, M. (eds.) Web Engineering. pp. 278–292. Springer Nature Switzerland, Cham (2023)

    2023

  72. [79]

    https://web.dev/articles/ttfb (2021), [Accessed 13-02-2024]

    Wagner, J., Pollard, B.: Time to First Byte (TTFB). https://web.dev/articles/ttfb (2021), [Accessed 13-02-2024]

    2021

  73. [80]

    https://web.dev/blog/inp-cwv-march-12 (2024), [Accessed 12-02-2024]

    Wagner, J., Viscomi, R.: Interaction to Next Paint becomes a Core Web Vital on March 12. https://web.dev/blog/inp-cwv-march-12 (2024), [Accessed 12-02-2024]

    2024

  74. [81]

    https://web.dev/articles/fcp (2023), [Accessed 13-02-2024]

    Walton, P.: First Contentful Paint (FCP). https://web.dev/articles/fcp (2023), [Accessed 13-02-2024]

    2023

  75. [82]

    https://web.dev/articles/tti (2023), [Ac- cessed 28-02-2024]

    Walton, P.: Time to Interactive (TTI). https://web.dev/articles/tti (2023), [Ac- cessed 28-02-2024]

    2023

  76. [84]

    Master’s thesis, Metropolia Ammattikorkeakoulu (2018)

    Wu, W.: React Native vs Flutter, Cross-platforms mobile application frameworks. Master’s thesis, Metropolia Ammattikorkeakoulu (2018)

    2018

  77. [85]

    https://vuejs.org/ (2024), [Accessed 18-03-2024]

    You, E.: Vue.js — vuejs.org. https://vuejs.org/ (2024), [Accessed 18-03-2024]

    2024

Pith tools

Reviewed August 11, 2026 · model on record in the stance chip above.