Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarification on Page Diagnostics for SharePoint Tool and SPFx web parts #10038

Open
2 of 9 tasks
DariuS231 opened this issue Dec 2, 2024 · 0 comments
Open
2 of 9 tasks
Labels
Needs: Triage 🔍 Awaiting categorization and initial review.

Comments

@DariuS231
Copy link

DariuS231 commented Dec 2, 2024

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

  • 💥 Internet Explorer
  • 💥 Microsoft Edge
  • 💥 Google Chrome
  • 💥 FireFox
  • 💥 Safari
  • mobile (iOS/iPadOS)
  • mobile (Android)
  • not applicable
  • other (enter in the "Additional environment details" area below)

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.
image

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
@VesaJuvonen VesaJuvonen added the Needs: Triage 🔍 Awaiting categorization and initial review. label Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 Awaiting categorization and initial review.
Projects
None yet
Development

No branches or pull requests

2 participants