You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of our clients reported performance issues on the home page of their intranet, which includes several of our custom web parts as well as out-of-the-box web parts. The client created a support ticket with Microsoft, and the response indicated that the Page Diagnostics for SharePoint tool shows the page is exceeding the limits of requests to SharePoint APIs and Search APIs. The support team suggested that our web parts might be the cause of this issue.
However, we have developed these web parts following the SPFx best practices recommended by the Product Team and the community. To further investigate, we tested the Page Diagnostics tool on multiple scenarios and found that it shows failures even on pages with only nine out-of-the-box web parts.
Given this context, we would like to ask if the Product Team has considered the output of this tool in relation to the principles and modularity of SharePoint web parts and SPFx solutions. It seems that the tool's output might not align with the intended benefits of using SPFx web parts.
The screenshot shows the output of the tool on an out-of-the-box page with only 9 out-of-the-box web parts.
The web parts we used on this page are:
1x Image web part
1x News web part
1x quick links web part
3x Highlighted content web part
1x List web part
1x Sites web part
1x Events web part
The text was updated successfully, but these errors were encountered:
What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested
Additional environment details
Issue description
One of our clients reported performance issues on the home page of their intranet, which includes several of our custom web parts as well as out-of-the-box web parts. The client created a support ticket with Microsoft, and the response indicated that the Page Diagnostics for SharePoint tool shows the page is exceeding the limits of requests to SharePoint APIs and Search APIs. The support team suggested that our web parts might be the cause of this issue.
However, we have developed these web parts following the SPFx best practices recommended by the Product Team and the community. To further investigate, we tested the Page Diagnostics tool on multiple scenarios and found that it shows failures even on pages with only nine out-of-the-box web parts.
Given this context, we would like to ask if the Product Team has considered the output of this tool in relation to the principles and modularity of SharePoint web parts and SPFx solutions. It seems that the tool's output might not align with the intended benefits of using SPFx web parts.
The screenshot shows the output of the tool on an out-of-the-box page with only 9 out-of-the-box web parts.
The web parts we used on this page are:
The text was updated successfully, but these errors were encountered: