Lighthouse's "Reduce unused JavaScript" audit reports 22.7 KiB of the 29.7 KiB in main.js (76%) as unused on our homepage. Looking at the file, it appears to bundle a wide range of platform features into one script regardless of which ones a given store actually uses — shopping cart, address book, product variations, search, store locator with Google Maps, postcode/suburb selection, back-in-stock notifications, AJAX templating, vehicle/product compatibility matching, endless scroll, popup utilities, and currency formatting.
I'd like to request that Neto/Maropost consider a mechanism to customize which modules are included in main.js on a per-store basis — for example, tied to which features are actually enabled in a store's control panel configuration, rather than shipping the full bundle to every store regardless of what's turned on.
To be clear, I'm not asking for main.js to be trimmed globally or for any specific feature to be removed platform-wide — I understand other Neto stores will use different combinations of these features than we do. The ask is specifically for per-site configurability, so each store can run as lean as possible for its own actual feature usage — including ours, as the features we rely on may change over time — without affecting what's available to other stores.
Why this matters: I'm actively working to hit best-in-class Core Web Vitals and PageSpeed scores, and a leaner, store-specific main.js would be a meaningful contributor to that goal — particularly on mobile/slower connections, where every KB of unused JavaScript adds real cost to both transfer time and parse time.
