Jira (Atlassian) Core Web Vitals
How real Chrome users experience www.atlassian.com, from Google's Chrome UX Report: the 75th percentile of visits on every device.
Jira (Atlassian) fails Core Web Vitals
Sep 27 – Oct 24, all devices
INP
360 ms
Needs improvement
LCP
4.7 s
Poor
CLS
0.11
Needs improvement
FCP
2.9 s
Needs improvement
TTFB
1.7 s
Needs improvement
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- Jira (Atlassian) fails Core Web Vitals on Largest Contentful Paint (4.7 s, good is 2.5 s or less) and Cumulative Layout Shift (0.11, good is 0.10 or less) and Interaction to Next Paint (360 ms, good is 200 ms or less).
- Time to first byte is 1.7 s, so most of the LCP time is spent after the first byte: loading the main image, fonts or scripts.
- Among 17 developer tools sites we track, Jira (Atlassian) has the 16th fastest LCP.
- INP has worsened by 171 ms over the last 25 weeks, from 189 ms to 360 ms.
Keep a site like this from getting slower
Real-user data shows a regression weeks after it ships. Vitalgate runs Lighthouse on every pull request and fails the check when a change breaks budgets like these: LCP ≤ 4.8 s, CLS ≤ 0.11, FCP ≤ 2.9 s.
Other developer tools sites
| Site | Core Web Vitals | LCP | INP | CLS |
|---|---|---|---|---|
| GitHub | Passes | 1.9 s | 87 ms | 0.05 |
| Bitbucket | Fails | 4.0 s | 133 ms | 0.12 |
| Linear | Fails | 3.0 s | 95 ms | 0.10 |
| Sentry | Fails | 2.8 s | 62 ms | 0.00 |
| Postman | Fails | 4.4 s | 116 ms | 0.07 |
| Stack Overflow | Passes | 1.6 s | 61 ms | 0.08 |
| npm | Passes | 1.9 s | 45 ms | 0.01 |
| Docker | Passes | 1.8 s | 110 ms | 0.03 |
| Datadog | Passes | 1.4 s | 78 ms | 0.01 |
| PostHog | Fails | 2.1 s | 384 ms | 0.05 |
| Retool | Passes | 1.5 s | 121 ms | 0.00 |
| Replit | Fails | 6.1 s | 415 ms | 0.10 |
| CodeSandbox | Fails | 4.0 s | 172 ms | 0.04 |
| Cursor | Fails | 3.1 s | 83 ms | 0.00 |
| JetBrains | Fails | 2.2 s | 111 ms | 0.12 |
| Raycast | Passes | 1.8 s | 87 ms | 0.00 |