A: 

Lorna,

maybe your security team is going crazy. What is the difference between serving a dynamic HTML generated by the server and a dynamic JS generated by the server?

It does not make any sense. You should try talking them out of it.

tucaz
Many thanks for your answer. However it's not related to security at all, we have a requirement to reduce up-front load time for the application as much as possible. There is policy in place that the desktop machines do not cache Browser content. We've done some tests and by deploying the scripts in Release mode, and with IIS compression enabled we can get them down to about 40kb. However each site has a contended, very low bandwidth line. Quite literally every byte counts. I realise the irony since we're using UpdatePanels but despite Bernhard's misgivings this is a temporary solution.
Lorna
Why you can´t cache stuff in the client? Maybe this policy can be removed "temporarly" while you develop a new version with jQuery or other JS frameworks. Still, this policy looks very odd and makes no sense. Update Panel != Performance. Tell us a little bit more about the environment where every byte counts. I´m very curious.
tucaz
The organisation has disabled browser caching as a company-wide policy and will not re-enable it for this application. The application itself is (clearly) not designed for this environment, so the intention is to try and get something in place with local JS content whilst in the meantime we rewrite the front-end using jQuery or the MS AJAX Framework without the use of update panels. I completely understand that UpdatePanel != Performance, they're not going to change their caching policy unfortunately.The environment is a distributed network of branches on very low speed, contended lines.
Lorna
Apologies Tucaz, I've edited the question to more accurately reflect the situation. We don't have "complete control over the client machine configuration". I've amended it to reflect the fact that we have control over the local filesystem only.
Lorna
A: 

what is the average size of pages and viewstate data. you might need to store viewstate in sqlserver rather than sending it to client browser every time.

Cem
Many thanks for you response. ViewState is disabled and the average page size is very small, circa 5kb - 8kb or thereabouts. The real issue is the up-front load time for resources such as CSS and JS since they're not being cached.
Lorna