Tools like Page Speed Insights and Google Lighthouse are great for providing advice for front end performance issues. But what these tools can’t do, is evaluate performance across your entire stack of distributed services and applications. This is why you need tracing.

Frontend issues that affect your users are often triggered by backend problems. Join us in this workshop so you can learn how to identify the issues causing your poor Core Web Vitals. Then, discover how to trace issues to slow database queries or the dreaded server-side request waterfall. In this session you’ll learn how to: Discover common sources for poor web vitals Setup tracing with Sentry Trace issues through your stack to the code-level with Sentry.

React 19 isn’t GA yet, but Sentry already supports it. The Sentry React SDK now supports React 19 and it’s new error handling hooks. This means that Sentry will automatically attach your component stack to every new error, making it easy to know where to look in your component tree for debugging.

See your source code in your JavaScript project’s stack trace by uploading source maps to Sentry. Learn how to use the Sentry source map wizard to unminify the code displayed in a Sentry issue’s stack trace.

Sentry’s User Feedback gives your users an easy way to provide direct input on problems they encounter on your site – whether that be a frontend error, broken link, or misleading label – to help get context into a known error or catch an issue that can only be spotted in the UX. This simple widget can be customized to match your site’s look and feel and embedded non-intrusively. Learn how to set it up with this step-by-step demo.