infragistics.js combined all controls js, it's too huge, over 2M even minified.
infragistics.loader.js is lightweight, it will raise more http request. Look the grid control which is the most commonly used in out application.
Almost 20 request raised.
Code:
Hi,
My advise is to stick with the loader, because the files will be initially cached in the browser cache and for the subsequent page visits the files will be loaded from the browser cache so there will be no http requests.
As an alternative you can examine the files requested by the loader and then combine them in one file(one for JavaScript code and one for the Style sheets), but you have to be careful to order them correctly in the file because there are dependencies between features. Then use your custom generated file in the production page. The drawback is that you have to create such file on each Volume release/Service release from Infragistics, so it will be best to incorporate this in your build procedure.
Best regards,
Martin Pavlov
Infragistics, Inc.
I don't think that's a good idea to combine the css or js manually, since each control loading different resource group.
And the browser will load the infragistics.js from the cache once user downloaded it, that same to the action of infragistics.loader.js.
I have a idea to reduce the css request. I'll refer to the both files infragistics.theme.css and infragistics.css in advance, then when I use infragistics.loader.js to load control's resource, can I avoid the css part files to be downloaded via some settings?