# Addressing Frontend Performance Bottlenecks in OpenELIS Global 2 after two week analysis

**URL:** <https://talk.openelis-global.org/t/addressing-frontend-performance-bottlenecks-in-openelis-global-2-after-two-week-analysis/2157>\
**Category:** Ask OpenELIS\
**Tags:** dev, gsoc2026\
**Created:** [March 18, 2026, 7:11pm UTC](https://talk.openelis-global.org/t/addressing-frontend-performance-bottlenecks-in-openelis-global-2-after-two-week-analysis/2157 "2026-03-18T19:11:44Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![priyanshu56](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/priyanshu56/32/1148_2.png) [@priyanshu56](https://talk.openelis-global.org/u/priyanshu56)\
**Post date:** [March 18, 2026, 7:11pm UTC](https://talk.openelis-global.org/t/addressing-frontend-performance-bottlenecks-in-openelis-global-2-after-two-week-analysis/2157/1 "2026-03-18T19:11:44Z")

</div>

After a deep dive into the `frontend` architecture, I have identified several critical performance bottlenecks that impact initial load times and UI responsiveness.

**Core Issues Identified:**

- **Monolithic Initial Bundle** :

- **“God” Components** : Key files like

- **Unoptimized Deployment** : The default Nginx configuration lacks **Gzip compression** and **Caching Headers** , resulting in slow asset delivery and redundant data usage for returning users.

- **Legacy Sync Patterns** : The presence of synchronous fetch helpers in

- **Utils.js** poses a risk of freezing the browser UI during network requests.

---

<div class="post-metadata">

**Author:** ![priyanshu56](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/priyanshu56/32/1148_2.png) [@priyanshu56](https://talk.openelis-global.org/u/priyanshu56)\
**Post date:** [March 18, 2026, 7:17pm UTC](https://talk.openelis-global.org/t/addressing-frontend-performance-bottlenecks-in-openelis-global-2-after-two-week-analysis/2157/2 "2026-03-18T19:17:12Z")

</div>

@Moses_Mutesasira@Agaba_Derrick_Junior sir can you please check and review my understanding over frontend.  
and suggest me more about the flow of frontend so i can effectivly handle everything I have learn all the major performance startergy from our lead engineer which can help in this project

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/openelisci/original/1X/1e5d1a910deb131d254116e7e3f97df90eb92614.png) [@system](https://talk.openelis-global.org/u/system)\
**Post date:** [March 19, 2026, 9:44am UTC](https://talk.openelis-global.org/t/addressing-frontend-performance-bottlenecks-in-openelis-global-2-after-two-week-analysis/2157/3 "2026-03-19T09:44:10Z")

</div>



---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/openelisci/original/1X/1e5d1a910deb131d254116e7e3f97df90eb92614.png) [@system](https://talk.openelis-global.org/u/system)\
**Post date:** [April 16, 2026, 6:32pm UTC](https://talk.openelis-global.org/t/addressing-frontend-performance-bottlenecks-in-openelis-global-2-after-two-week-analysis/2157/4 "2026-04-16T18:32:41Z")

</div>


