I'm working on a big (200 pages) dotnetnuke site. The load time of a page is extremely slow (+ 30 sec). How can I find out the bottlenecks that make this site so slow ?

The server we use can't be the problem (Dedicated server, Xeon 1.60 GHz Quad Core, 2 GB memory, 2 x 146 GB 15k rpm SAS disks raid 1).

The site we're talking about can be acessed on : http://citanew.weborigin.be

Thanks a lot for your input.

I've set the caching of the modules on the homepage to 3600 sec. The menu however cannot be cached. My guess is that the menu is the biggest boottleneck. I used the CISS.SideMenu module. This module uses XSL to create the html output. I've created my own XSL because the samples included in the CISS.SideMenu did not what I needed. The entire website structure is everytime loaded, because with javascript I open/collapse the submenus, that's the reason also that the pages are around 500K each.

On my portable (Core 2 Duo 2Ghz, 2Gb, Vista), I have the same site running, but is a lot faster. I tried restarting the application pool (dedicated for this dotnetnuke instance) on our server, and now the site is already remarkable faster.

The current settings of the Application pool are :

• Recycle worker process : 1740 min
• Shutdown worker process after being idle for 480 min
• Number of requests : 1000

Can I tune these application pool settings. Is it advisable to run a script for restarting the application pool every xx hours ?

Software on our server is Windows Server 2003 SP 2 + MS SQL Server 2005 Workgroup Edition

I've installed and configured the module Open-Viewstate (http://www.opendnn.net/DNNModules/OpenViewState/tabid/110/Default.aspx) which greatly reduces the size of the viewstate. The page size is now a lot smaller, but the site is still slow.

For now the only thing that helps is restarting the Application Pool, but after 15 minutes the site is again remarkably slower.