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

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:

    App.js imports all major features (Storage, Admin, Reports) synchronously. This forces users to download the entire application logic before seeing the login page, significantly slowing down the “time to interactive.”

  • “God” Components: Key files like

    StorageDashboard.jsx have grown to over 4,900 lines (~182 KB). These bloated components increase browser parsing time and cause expensive re-renders.

  • 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.

@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