Kevin,

My user has expressed a concern that the web page I have developed takes about 15 to 20 seconds to open the main web page everytime it is called. I don't know if this is reasonable. There are large amounts of static data, and the web page has many data elements.

1 - WebMenu
1 - WebTab - 7 tabs
7 - User Controls for the tabs
1 - User Control for a footer (static Info)
1 - Parent Table (1 Row) (56 fields, some varchar(500) and a single varchar(2000))
2 - Child tables (say 4 records each, average row size 100) (5 fields each)
14 - Static tables (pulling from a cache object when available, total of 193 records, average row size 60)

Approx 5 WebDateChoosers
Approx 20 mmDropDownLists
2 mmDataGrids (child tables)
1 Radio Button list
1 Check box
2 buttons
1 WebNumericEdit
Approx 5 WebMaskEdit
the remainder are WebTextEdit objects

On my machine it takes less than 5 seconds. When I tested the web application on the clients server, it was also less than 5 seconds. The user is accessing the system in a place called Westlock, Alberta (rural), where the system resides in Edmonton, Alberta (urban). Westlock is about 50 minute drive NW of Edmonton. The system will eventually reside in Westlock, but will be accessed across Northern Alberta. How can I make that web page perform faster or persist it's state on the client's machine and only have the data behind it refresh? Or does the page always have to come from the server? I see other applications, such as Universal Thread, performing very fast in comparison. I must be over looking something.



>Gordon,
>
>I don't know if you've seen this link in the MM .NET Dev Guide, but it can help you make your decision:
>
>http://msdn.microsoft.com/msdnmag/issues/03/04/ASPNETUserState/default.aspx
>
>Regards,