Not sure if this should be in this or the content management forum so please reroute if necessaryI have been asked to look at a server which is running MOSS 2007.Single Web application - single site collectionTop Level Site is a publishing site with one sub site1700 pages in the top level site pages library300 or so pages in the sub site pages LibraryOpening a page in the top level site takes about 8 seconds in the sub site 1-2 secondsI added a simple web part page with the default master page in each site and the speed is about the same as the modified content pages i.e still 8 secs in top level and 1-2 seconds in sub site.I am fairly new to publishing sites and am hoping to get some advice as to how to get the top level pages opening a bit faster.1. is 1700 pages excessive in a single library 2. is it OK to switch on a column index in this pages library (title column?) - is this likely to help or should the pages be in subfolders3. I am currently reading a page http://msdn.microsoft.com/en-us/library/bb727371.aspx - and will start working through this but any other suggestions are most welcome or an indication that this article is the right approachMany thanks in advanceDavid

Is there anything on those top level pages that aggregates data or shows a list of other pages dynamically? If so, it may be grabbing the entire collection before filtering it down to the first 10-20 items. Here are some other recommendations I blogged about a little while back: http://nextconnect.blogspot.com/2010/01/troubleshooting-page-loading-issues.htmlSharePoint MVP | Developer | Administrator | Speaker-- Twitter -- Blog - http://nextconnect.blogspot.com

I agree with Mike that you should check for web parts or custom code / RSS feed readers on the main page. If there are none I would check your SQL performance. The static content should be cached after your first visit to the site.Andrew Milsark, MCTS Fpweb.net - The SharePoint Hosting Pioneer Blog : http://blog.fpweb.net Twitter : http://www.twitter.com/sharkmu25

Hi, I would suggest the following: 1. Check if there are few webparts on your top level sites that are just "closed" and not "deleted". "Closed" webparts consume resources. 2. Enable caching of not so frequently changed items on those pages: like Images, Scripts, CSS etc. 3. Main reason of slow performance is the time taken by client browser to download the content of the page. apart from using caching, optimize all the scripts, CSS and most importantly the images and flash content if used any. 4. Check for external feeds and data aggregation from other sites as pointed out in previous posts. 5. You have to check how many connections are being used to connect with the SQL server. If there are many, esp in case of unghosted pages, try to improve performance of SQL server and network between index server and DB. 6. Check which version of IE are you using. IE 6 is slow in comparison to its successors and surely avoid any tool bars. I can go on and on but I would suggest that you check all above points and if performance is still not improved, get back to me.Cheers, Sanjiv Kumar

Firstly thanks for all the suggestionsI have installed fiddler and observed that the payload is the same (roughly) between sub site and top site pagesI then copied a subsite page to the top site and see the performance decrease - i.e same page slower in top level faster in sub siteI added a brand new page - same effect - no custom code, no web parts closed or otherwise, no customised page or master page.This to me suggests that in the top level site something like navigation is including the sub site so we are hitting a threshold (magic no 2000 maybe) however - switching off show pages in the navigation settings made no difference. There were many there and set to hidden.As soon as I can get back to the server I will investigate some more Thanks again

The main problem turned out to be a sharepoint:aspmenu, using the standard site map provider, in the master page which was only showing 6 items as a set of tabs - there are 1700 pages in the library (similar to what Mike said in the first reply)- removing this changed the speed of the page dramatically. Now I can replace it with a different approach.There are client side routines which call back to the server to get information from lists but the amount of data is small and they run very quickly.Thanks again for all suggestions - having these made a real difference

David,did you try to turn off "Show pages" option in Site Actions > Site Settings > Modify All Site Settings > Navigation? May be with this option unchecked you will be able to solve your problem without removing of AspMenu control. For more details you can see http://sadomovalex.blogspot.com/2010/02/basics-of-navigation-in-sharepoint.html http://sadomovalex.blogspot.com

Hi ,I did try this but it was still slow .It wasn't until I removed the sitemap datasource and menu that the page started to respond in reasonable time.thanks