Hi,
As I said before, I spent at least a week trying to implement combining and minifying of scripts and I read a lot of articles and they all sound easy but in fact when you have a cms with composable pages where each page may need different scripts it is very problematic.
Anyone who feels they can really solve this problem I say go for it and give it a try, if you succeed I will salute you. But before you declare success be sure you test every feature (in every major browser) and also consider the impact on custom features that others may have developed for their own needs. I worked very hard to try and do this but I found it to not be feasible. It is quite easy if you know exactly what scripts will be needed in a page but in a cms with composable pages including content of unknown features you don't. Also many of the script references come from the asp.net runtime and have urls like ScriptResource.axd?... because the script comes from embedded resources in an assembly instead of static script files.
So even if you figure out a way to combine all the scripts needed for a given cms page, you end up needing to do it different for each page since there may be variations in the needed scripts so you lose the benefit of caching in the browser because you would need a different combined script for each page. You might think you could figure out all the possible scripts needed in the whole site and combine that into one script, but that will not solve it if additional scripts are needed in custom features (nor will it solve the embedded resource scripts) and it would result in one large script file that includes many things not needed on many pages. Then there is always the consideration of how expensive is the processing to do the combining and minifying and does that create a performance hit that offsets and benefit. So one needs to do both measuring of page load speeds before and after applying any such techniques as well as load testing to make sure it does not degrade the number of requests per second that the server can handle by adding this extra processing.
The specific article you pointed to only handles scripts that are loaded in the <head section which is basically none of the scripts in mojoPortal. So there is nothing helpful or new in that article.
So it is a huge challenge (translate as very expensive) that can result in some micro optimizations for page loading if you succeed (little bang lots of bucks). It may be possible for Yahoo and Google to do this kind of thing because they have a lot of expensive developers at their disposal and in their cases it is justified to spend that kind of money micro optimizing page speed due to the sheer amount of traffic they receive and the money they make.
Best,
Joe