I think you might miss the css and javascript binding points. If you are going to add css or js files on each view in combination with the files on the main page, then you create a ton of small packages that your user must download every time.
If you don't have a ton (and I mean TON) of Javascript and Css, then you better combine ALL of your css and javascript into the same kit. Thus, the user gets hit by loading it for the first time, and then it is cached.
If you have TON css and javascript, use the named bundle function and create packages for different sections of your site. But the thing is that you want to minimize the number of packages created so that the user does not have to download files.
The only exception is for mobile browsers where they have certain size caching restrictions.
source share