asked on

Sharepoint 2010 home page performance

I am running a Sharepoint 2010 farm. I have a few thumbnail pics and a slide show on the home page. Internal performance is ok but external is slow which I believe is related to the size of the home page.
I am using ie developer tools network capture to view load time and pic size. The Sharepoint developers are not strict on pic size and I want to provide them with guidelines for pic size and overall home page size. Is there a max size a pics should be on a home page and also what is the recommended max size of a home page for Sharepoint 2010. Thanks

QPR

If the true culprit is image and page size (as opposed to code related sluggishness) then this is probably a general web design best practise rather than sharepoint specific question and answer.
Listed here are some great tips and best practises for reducing page load time.
http://developer.yahoo.com/performance/rules.html

Also, use the developer dashboard to view webpart load times
http://msdn.microsoft.com/en-us/library/office/ff512745(v=office.14).aspx

Ted Bouskill

Further to QPR's comment there is a plug-in for FireFox called YSlow that does a great job of breaking down the page performance.

Sid_F

ASKER

I am using fiddler to look at page performance however it is really what the min and max page size should be for a corporate environment that requires internal and external access that I am looking for. To some degree looking at performance tools is pointless unless you know what the benchmark size should be.

QPR

The benchmark is before it gets to the point you find yourself at, you'll have to reduce the number of page elements or use the developer dashboard to find an offending webpart

Sid_F

ASKER

I'm guessing from the responses that there is no metric for the ideal size. It's down to the admin to decide what is slow.

QPR

Correct (or user feedback).
In these days of fat internet pipes you'd need to out of your way with front end stuff to impact the end user beyond just a bit slow. Look to back end calls, buggy webparts or elements relying on other resources for your speed issues.
Did you look at the developer dashboard yet?

Sid_F

ASKER

Yes I looked at the f12 developer tools and even MS deep dive on the tool but I cannot get any real life scenarios as in ... this is a test page and here are the slow elements and here is how the slow elements are identified on a capture...

The deep dive talks about getting wait, start, request, response and gap timings but doesn't go much further in actually putting them to work in a real scenarios.

SOLUTION

QPR

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

Ted Bouskill

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial