Supported way of eliminating (large) JS files for SharePoint 2010
During an onsite visit at a customer who were very busy at creating an Internet facing website using SharePoint 2010, I was asked if the technique that was described by my buddy Chris O’Brien to prevent the loading of unnecessary .js files was supported yes or not. And if not, if Microsoft had an alternative. Needless to say that the approach that Chris took was not really that supported by Microsoft (modifying the HttpContext and using Reflection are not really that great to be supporting right ;)
If you are really wondering what this post is about, I strongly recommend reading Chris’s post “Eliminating large JS files to optimize SharePoint 2010 internet sites“ on why you don’t want to load the all .js that are used by SharePoint 2010 files for anonymous facing websites.
How this stuff works within Microsoft?
However, it took some challenges to figure this one out. I would like to give you an insight how stuff works within Microsoft on how to get something like this be officially supported yes/no.
First of all, the only team responsible for saying that something is supported or not, is the Product Group (PG).
To get such a statement the following happens:
- PFE (that’s me) researches if there is a related (kb) article to support the question of the answer, if nothing found, he escalates this to the Account Manager of the customer who then raises a ticket for a Request for Collaboration.
- Technical Lead will craft a Request for Collaboration with the PG
- RFC goes to an Escalation Engineer that maintains this communication with the PG
- PG responds with an answer, while they are extremely busy with developing the next version of SharePoint
- RFC goes back to the Escalation Engineer and he/she communicates this with the Technical Lead and the involved on-site engineer (that’s me) to see if the answer is the desired one
As you may have noticed, I (as a Premier Field Engineer) don’t have a direct line with the PG. It’s not that I can call the developer lead of the WCM piece of the platform to give me an answer to something like this or why something is implemented as it is, this is of course for good reason ;)
I just wanted to point out how many steps are involved and that such a process can take up quite the time to be finished.
Sorry to have keep you waiting, however, below is the code by utilizing Chris’s solution, to prevent the registration and downloading of the .js files.
protected override void OnPreRender(EventArgs e)
There you have it, by just calling a (yet) undocumented SharePoint JSOM call, will result in SharePoint not loading and registering the .js files. This method is however a public API which you can use for this particular reason.
The only you need to make sure is that this control is near the bottom of the page and not on top of the page like Chris explains in his post.
Yes, really, this is the solution. The question is, what does it actually do?
Well, it just stops the prefetching from happening. The only time the .js files are loaded is when a control is asking for it, meaning that you really should test if everything still works on your page when implementing this and you use a control that is dependent on a SharePoint .js file. Furthermore there is maybe a performance penalty you need to pay when you are 'synchronously’ downloading that particular .js file.
Also, please make note, like Chris is also explaining in his post, it’s not just the downloading of the .js files that is the issue, it’s also the manipulating of the DOM that is being prevented which results in a page that is loaded quicker and feels ‘snappier’ as well.