Announcing availability of the Page Diagnostics Tool for SharePoint

Published Jun 28 2018 11:56 AM 23.9K Views

Today we’re pleased to announce availability of the Page Diagnostics Tool for SharePoint.  The Page Diagnostics Tool for SharePoint is a Chrome Browser Extension designed to help you identify potentially problematic Classic pages in SharePoint Online that may not be delivering optimal performance based on characteristics discovered about the page by the Page Diagnostics Tool. 


The Page Diagnostics Tool works by comparing discovered characteristics of one or more Classic pages in SharePoint Online to known best practices and provides guidance to remediating those issues to ensure you are delivering the best possible experience across these pages.  In addition to addressing performance of existing pages, the Page Diagnostics Tool can also be used to evaluate existing pages before they are published in your environment.


The Page Diagnostics Tool is currently available as a Chrome Browser Extension that can be downloaded directly or installed through the Chrome web store.


For additional information on installing and using the Page Diagnostics Tool, refer to the getting started guide  


The Page Diagnostic Tool also provides detailed information on a variety of characteristics useful for support and troubleshooting purposes to include the current CorrelationID, SPRequestDuration, SPIISLatency, page load time, and the current Url evaluated.  For information on how to use this information, refer to support documentation for the Page Diagnostics Tool at



The baseline rules currently evaluated by the Page Diagnostics Tool are detailed below.  Each rule has an associated “more info” link which will take you to the supporting page providing more insights on the rule.





  1. Check Running as Standard User
  2. Check Requests to SharePoint
  3. Check using CDNs
  4. Check for Large Image Sizes
  5. Check for Structural Navigation
  6. Check for CBQ WebPart (CBQ - Content by Query WebPart)


For additional information on using the Page Diagnostics Tool and in-product help, you can also use the About link in the tool to get links to the “How to use this tool”, “Tune SharePoint Online Performance”, “Third Party Notice” in addition to a link to “give feedback” which links to the tools and extensions section in User Voice.






We look forward to your feedback as we continue to consider scenarios for future versions of the Page Diagnostics Tool for SharePoint.

Frequent Contributor

Great to see this tool is released. I have done some debugging in the past on classic pages that were not performing as aspected, having a dedicated tool for this sounds good!


Thanks @Harold van de Kamp!  Let us know if this solutions helps in future debugging efforts.

Regular Visitor

Thanks Bill - just what our team needs right this moment. Thanks @harbars for passing on. 

Occasional Contributor

@Bill Baer Can this plugin be used for modern experience pages?



Regular Visitor

A version for Firefox would be nice.

Frequent Contributor

What happened to Edge? I thought MS wanted everyone to use it as the primary browser.


@RAJU GOLLA On Modern Pages you will receive basic diagnostic details and trace information.

Regular Visitor

Hi @Bill Baer,

Thanks for delivering this tool, we as a SharePoint solution editor company will probably rely on it to increase performance and user feedback on custom SharePoint portals we develop. 

A quick technical feedback though, we experience conflicts when the plugin is installed because it double loads some SharePoint standard JS libraries (SP.js, SP.runtime.js and SP.publishing.js) which sometimes already are on the page/masterpage and I found two drawbacks :

- they are loaded from [the current SharePoint site]/_layouts/15/*.js rather than the CDN

- they break something when custom code is executing a SP.clientcontext query and gathering fields with some SP.Taxonomy.TaxonomyField among them. The taxonomy fields are then badly initialized and all their properties are null. 

I can confirm that if I prevent the plugin from loading SP.js and SP.runtime.js and directly use the ones previously loaded from CDN it works seamlessly. My advice would be to check the availability of both the namespaces registered by these JS files and call $.getscript() only if needed. 

Regular Visitor

@Wojciech Wróblewski could you check with this extension converter ? I already used it in the past and it gives often good results. I don't think the plugin uses specific Chrome APIs and seems to be mainly based on vanilla JS.


It's great to see a tool like this available to the community.  Thanks, Bill for making this happen.   However, I noticed that the values for SPRequestDuration & SPIISLatency are reporting as "N/A" and the page load time is a negative value.  Am I using it incorrectly?  (BTW - This was from home.aspx on a modern team site.)





Is this only applicable for SharePoint online or on Premise versions as well?


Thanks for the feedback. The N/A is as a result of not receiving the SPRequestDuration and SPIISLatency from the page. This is an issue on pages in team sites currently and is not an issue with the Tool.

The issue is already logged and is being investigated by the SharePoint Engineering team. It does not affect the rules processed by the tool.

The current version of the tool is designed for classic pages. 

The page load time was originally provided for informational purposes. It does not affect the rules processing but the issue regarding a negative load time is currently being investigated. 


@Rishi Gupta Works on-premises as well on classic pages served over HTTPS.

Frequent Visitor

Hi ,


I have tried this tool for Classic pages but still it shows N/A for  SPIISlatency , SPrequestduration.  Any suggestions?




Hey @Pavan reddy, as per my previous comment it has nothing to do with the tool.
It is a known issue on classic pages on team sites which is being investigated by the SharePoint Online team as the SPIISLatency and SPRequestDuration is not being returned in the page header so the tool cannot access it. If you tried to get the same data via F12 Dev Tools or in Fiddler you will see it doesn't exist there either.
The numbers are not really helpful to you in SharePoint Online as the items that impact those numbers are related to the server calls you make from your pages which is why we highlight the items to optimize and provide an overall page load time so you can work towards optimizing your pages.

Occasional Contributor


I'm wondering when the tool says "Not using CDN" but it then also shows the "Found 1 URL" notification is that URL using the CDN?





@Alexander Broere, you may have used CDN for some items but there are items that are not in CDN which is why the message is highlighted. Only when all items that could be in CDN are complete would this change to green.

Occasional Contributor

Hi @Scott Stewart,


Ok, so the Found URL are the ones that need to be added to the CDN to make the red message go green? Is there also a reason why sometimes it says "found 1 URL" but then it says " found 2 URL (1,2)" then it switches back to "Found 1 URL" etc..?


Thanks for the help




Hey @Alexander Broere, yes it will highlight those not in CDN. If it is different on the same page I would like to understand what you are seeing so please DM me so we can sync.

Version history
Last update:
‎Jun 28 2018 11:59 AM
Updated by: