[Due for payment 2025-09-12] [Due for payment 2025-08-19] [Due for payment 2025-08-01] Investigate options to reduce the DOM size for performance imrovements

[mountiny]

Coming from here.

The size of the DOM of the app has an influence on its performance. Every added extra layer means more load for the browser/ device. Lets investigate:

• What is the impact of each DOM layer on performance? Should we try to address it ASAP, or is the impact rather small, though not insignificant, so we should fix this over time?
• Can you identify common patterns which lead to unnecessary DOM layers that we could remove with an easy refactor?
  • Can we prevent these from happening in future? Can we add some eslint rule to prevent the bad
• At what point do we reach diminishing returns?
• What best practices we can put in place to avoid bloating the DOM in future?

Issue Owner

Current Issue Owner: @abekkala

[melvin-bot]

Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.