Web Vitals
Learn more about Web Vitals issues and how to diagnose and fix them.
Web Vitals issues are created for the highest opportunity pages in a project when their vitals scores fall into the Meh or Poor threshold for an extended period of time.
This issue is currently only available for browser SDKs.
The detector for this performance issue runs on a schedule and checks the 7 day average Web Vitals scores for the top 5 highest opportunity pages on your website (the pages that are both high traffic, and have issues worth fixing).
The following additional criteria must hold true:
- You must have Seer enabled on your Sentry account.
- You must have a Github code mapping configured for your project.
- There must be at least
10sample spans for the given vital (this value is configurable). - There must be no issues currently open for the same Web Vitals metrics on the page being evaluated.
You can view the Web Vitals Insights dashboard to get an understanding of what pages will trigger the Web Vitals performance issue:
- A loading / render performance issue will be opened, if Time to First Byte (TTFB), Largest Contentful Paint (LCP), or First Contentful Paint (FCP) falls into or below the
Mehthreshold. - A page stability issue will be opened, if Cumulative Layout Shift (CLS) falls below the
Mehthreshold. - An interaction performance issue will be opened, if Interaction to Next Paint (INP) falls below the
Mehthreshold.
We highly recommend using Seer's Issue Fix functionality to diagnose and fix the Web Vitals Issues we've opened. Alternatively, there is lots of great documentation online about how to improve specific web vitals metrics, see:
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").