A new diagnostic component for Office 365 and SharePoint Online administrators is now available.
The Page Diagnostics Tool is going to help you potential issues with ‘classic’ SharePoint Online pages, like latency, page load time… You can also run a network trace from there
NOTE you need to have Publishing enabled if you need to troubleshoot CDN.
When you hit Start your page is reloaded to start logging
The following is being checked:
- Check Running as Standard User
Checking page performance should not be performed when logged in as a Service Account, Administrator or Site Collection Administrator. If you run the extension as an administrator/site collection administration this will be reported as ‘error’, even if this is not really one.
- Check Requests to SharePoint
The amount of data and requests made to the server should be limited as an overloaded page will experience poor performance. This check verifies the number of requests being made to SharePoint and will advise when the requests exceed 6 requests. Most requests should be cached and therefore not called for every page load.
- Check using CDNs
Content Delivery networks have been provided by Microsoft and the ones referred to here are the SharePoint Online Content Delivery Networks.
- Check for Large Image Sizes
Images should be optimized for web by utilizing better web types like PNG. Image renditions should also be utilized and is available in SharePoint directly.
- Check for Structural Navigation
Structural Navigation was originally designed for use in SharePoint On-Premises where object cache could be utilized. Structural Navigation is not recommended for use in SharePoint Online and should be changed to Managed Navigation or a Custom Provider.
- Check for CBQ WebPart (CBQ – Content by Query WebPart)
The Content by Query WebPart generates a high SQL load as it traverses all items in the query for each and every page load, for each User. Unlike an On-Premises installation, there is no cache available to limit the number of queries needed to populate this WebPart. As such CBQ performs slowly and impacts overall page performance which is why it should not be utilized. Please use the Content Search WebPart (CSWP) as the replacement for the Content Query WebPart.
Then you have the result of the analysis with the potential issue(s) found.
When you click on one of the issue found you will get a link to a More info page
Once completed, you will have to hit the Stop button as the tracing is not stopping automatically
If you want to take a network trace, just hit the Network Trace button and Start
You will be able to export the network trace result as a JSON file