We consume 33MB for a single page in GLPI about glpi HOT 4 OPEN

A lot of unneeded scripts are loaded because there is no sector > item > option menu difference between the search and form pages. Unless in debug mode though, the impact isn't that big because they will be cached by the browser.

For me, the computer search page loads 14.2MB of resources and only 422kb actually get transferred when in production env and with an updated DB. The worst offender is the locale JSON data which Chrome isn't using from the cache for some reason (not expired and the same URL is requested each time) at 371kb.

from glpi.

Is it really worth it to split libs loading as it is cached after the first load ?
This behavior lead to bugs many time because we forgot to load a library for a given page.

from glpi.

I think keeping it split is a good idea. Maybe not the way we are doing it now with the menu layout determining what gets loaded and not with as many script imports for a single feature.
Maybe something better can be done using webpack.
We really need to modernize our JS code in general.

from glpi.

I already have in mind a solution to be able to load modules only when it is necessary, and to also be compatible with CSP (= no inline JS code). I already implemented it on some projects, and it worked well. Anyway, changing this part is too late for GLPI 11.0, it can only be done later.

For GLPI 11.0, we should focus only on what could be considered as a regression, i.e. libs that were not loaded in the same context in GLPI 10.0 and that are really heavy.

from glpi.