Angular Performance Improvement

Shaikh Zaki Mohammed
2 min readJul 28, 2023

--

Gaining performance is not an easy job; a lot of hair loss cases has been reported in order to achieve tiniest bit of improvement in term of app speed.

In this series our focus will be to save those losing hairs by doing what best we can do to speeden up the app. This includes post related to Brotli, Gzip, Caching, API data caching, etc.

  1. Gzip Dockerized Angular App With Nginx — Ngdocker | CodeOmelet

Leveling up by taking performance improvement measures for our super friendly NgDocker app. In this article, we will explore how we can enable Gzip to improve performance at a hulking scale.

2. Nginx Cache Config For Dockerized Angular App — Ngdocker | CodeOmelet

App running so fast, even the cops are chasing! Not breaking any law here just configuring Nginx caching for our Dockerized Angular app. In this article we will address the need for speed for our super silly NgDocker app by setting up the Nginx cache configurations for static files.

3. Cache Angular Http Request Using @Ngneat/Cashew | CodeOmelet

The time of not wasting time on caching HTTP request data has come. Presenting @ngneat/cashew package to do the needfully; it takes our stress of manually creating service variables to hold up the HTTP requests data again and again. In this article we will explore @ngneat/cashew dope package for caching HTTP requests.

4. Brotli Dockerized Angular App With Nginx — Ngdocker | CodeOmelet

Patience is the key to success; not heard or followed by any of the web app visitors. We want everything to be loaded within blink of an eye. This is the place where Brotli shines. In this article, we will explore how we can enable Brotli in the NgDocker app to improve performance at a marvelous scale.

Originally published at https://codeomelet.com.

--

--

Shaikh Zaki Mohammed
Shaikh Zaki Mohammed

Written by Shaikh Zaki Mohammed

Learner, developer, coder and an exceptional omelet lover. Knows how to flip arrays or omelet or arrays of omelet.

No responses yet