Skip to content

Add mobile performance score section #14923

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 16, 2025
Merged

Add mobile performance score section #14923

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions docs/product/insights/mobile/mobile-vitals/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -32,6 +32,15 @@ In the example below, the detail view of a transaction displays the warm start m

While the SDKs differentiate between cold and warm starts, they don't track hot starts or resumes. To get more insight into your cold and warm start metrics, you can use the [App Starts](/product/insights/mobile/mobile-vitals/app-starts/) feature.

## Performance Score

Sentry categorizes average app start durations as follows:

| Metric | Good | Meh | Poor |
| --- | --- | --- | --- |
| Average Cold App Start | less than 3s | between 3s and 5s | greater than 5s |
| Average Warm App Start | less than 1s | between 1s and 2s | greater than 2s |

## Slow and Frozen Frames

To track the responsiveness of the user interface, Sentry measures _slow frames_ and _frozen frames_. Both indicate if the rendering of a frame is taking too long, causing the UI to appear laggy or frozen.
Expand Down
Loading