Anatoly Mironov
This list focuses on how you can improve the load times and the performance on a SharePoint page. This list does not take Infrastructure, Servers and Data Storage into account. See it only as tips for you, as Developer, how you can boost your SharePoint users' perception about the responsiveness and performance.
Reflow means rearranging of elements, changing their appearance. Every time you update the look of an element, the web browser recalculates all surrounding elements. It eats the memory and time. A suggestion is to hide an element, update it as many times you want, then show it again. This way there are only two times the page gets reflowed.
Please prefer using css classes instead of updating inline css.
Bundle and minimize. Every request costs you.
jpg is better at compressing, but it does not support transparency.
Override asp:Content placehoders with empty ones in pages that do not use it. A good example is a quick launch. If your start page does not show the quick launch (left navigation), why render it code behind. Just override it, to save processor time.
Do not have to many static levels. It takes time to render them:
<SharePoint:AspMenu
ID="TopNavigationMenu"
StaticDisplayLevels="1"
AdjustForShowStartingNode="true"
MaximumDynamicDisplayLevels="0"
SkipLinkText="" />
Infinite scroll, search autocomlete: Do not throw elements away. Keep the reference and reuse them. It will improve the memory usage in the web browser.
Do you want to load content async. Do not overdo it. It slows down the web browser. Do it in following situations:
- On demand (when the user wants it, show details, show more)
- On slow content. If your content takes time to get, then it is okay to use it. But if it does not take so much time, and it is shown on page, include it in the main page load. Let a user wait for the page 0.5 sec instead of showing an ugly spinner.
Do not use 3rd-party-frameworks jQuery unless you are very sure about what you are doing. Browsers are becoming better and better on implementing html5
Create a place (site collection or a web application, can be outside of SharePoint) The resources should be available for all users of the intranet. Please use it as an entry point, even for the hive resources.... This CDN can be even extended to be cached in different regions.
