Sentry tracing and profiling preventing PageSpeed Insights to compute scores

[rodolfoBee]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

8.54.0

Framework Version

No response

Link to Sentry event

No response

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Create a NextJS project
2. Build and deploy it
3. Check PageSpeed Insights for the deployment
4. Add Sentry SDK with performance and profiling enabled.
5. Check PageSpeed Insights again.

Expected Result

Sentry to not conflict with Google's data and get results from PageSpeed Insights on both cases

Actual Result

See screenshots before and after adding Sentry, disabling tracing and profiling resolves the issue.
Before:

After:

The domain and page were redacted due to PII, the original can be found in this internal ticket.

[lforst]

I looked into this and cannot reproduce with any configuration (replay, browser-profiling). It would be cool to get some sort of reproduction here.

Suspicion is that maybe turning on replay or profiling is simply the straw that breaks the camel's back with regard to PSI timing out.

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀