Why is my eSpace so large?
Our experience tells us that whenever a module has a large size, one of three things is usually involved:
You use a single module approach which is against the 4 Layer recommend architecture.
You have large images. Sometimes people include MB large jpg or png files with high resolution even if then they are re-sizing the images to smaller sizes in screens. This can also have a large impact when running the application because the browsers will fetch the entire image thus using more bandwidth.
You have large resources. Sometimes when using the Excel bootstrap approach people include it in the module by dragging and dropping the Excel to have everything together. Our recommendation in these cases is to change the bootstrap action to receive the binary instead of going to the resources and have a screen with a file upload field that calls the bootstrap action with the uploaded file.
While the first one is slightly harder to correct because it involves re-factoring of the code, the latest two are quite easy to spot and fix and will prevent such errors.