Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Summary
Implementing customizations in SharePoint places an even greater emphasis on effective design and development for web applications in general, and client-side web applications in particular, especially when it comes to the concept of application performance. Performance is one of the important factors that influence user-experience and how efficient users can work with the portal.
High-level guideline/general rules
- When testing performance, take into account both server-side performance of your code, as well as the performance of your code running in end-users' browsers.
- Whenever possible cache data to minimize the number of requests to SharePoint.
- When referencing scripts and other assets, allow users to cache them for as long as possible to minimize the number of requests to the server and the amount of data to load.
- Avoid excessive DOM manipulation that would trigger re-rendering of the page and delay its loading.
Handling SharePoint Online throttling
Applies to: Office 365
SharePoint Online uses throttling to prevent users from over-consuming resources. When a user runs CSOM or REST code that exceeds usage limits, SharePoint Online throttles any further request from the user for a period of time.
Articles
- Handle SharePoint Online throttling by using exponential back off
- Avoid getting throttled or blocked in SharePoint Online
Samples
SharePoint Framework
Applies to: Office 365 | SharePoint Server
Articles
- Optimize builds for production
- JavaScript Patterns and Performance
- Make batch requests with the REST APIs
- SharePoint Framework (SPFx) enterprise guidance
- Use existing JavaScript libraries in SharePoint Framework client-side web parts
- Use the Office 365 content delivery network (CDN)
SharePoint Add-ins
Applies to: Office 365 | SharePoint Server
The approaches you take to ensure optimal performance with SharePoint is different in the new SharePoint Add-in model than it was with Full Trust Code. In a typical Full Trust Code (FTC) / Farm Solution scenario most code operations took place in the SharePoint Server-side Object Model code.
Articles
- JavaScript Patterns and Performance
- Performance considerations in the SharePoint Add-in model
- Improve performance in SharePoint provider-hosted add-ins
- Make batch requests with the REST APIs
Videos
Samples
Portals
Applies to: Office 365 | SharePoint Server
Articles
- Proven Practices for SharePoint Online Portals - Performance
- Proven Practices for SharePoint Online Portals - Navigation Solutions
- JavaScript Patterns and Performance
- Optimize page performance in SharePoint