Miro Core Web Vitals
How real Chrome users experience miro.com, from Google's Chrome UX Report: the 75th percentile of visits on every device.
Miro fails Core Web Vitals
Sep 27 – Oct 24, all devices
INP
224 ms
Needs improvement
LCP
4.9 s
Poor
CLS
0.07
Good
FCP
1.2 s
Good
TTFB
785 ms
Good
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- Miro fails Core Web Vitals on Largest Contentful Paint (4.9 s, good is 2.5 s or less) and Interaction to Next Paint (224 ms, good is 200 ms or less).
- Time to first byte is 785 ms, so most of the LCP time is spent after the first byte: loading the main image, fonts or scripts.
- Among 16 productivity and collaboration sites we track, Miro has the 13th fastest LCP.
- INP has worsened by 24 ms over the last 25 weeks, from 200 ms to 224 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 ≤ 5.0 s, CLS ≤ 0.10, FCP ≤ 1.8 s.
Other productivity and collaboration sites
| Site | Core Web Vitals | LCP | INP | CLS |
|---|---|---|---|---|
| Notion | Fails | 4.9 s | 153 ms | 0.01 |
| Slack | Passes | 1.9 s | 83 ms | 0.07 |
| Asana | Fails | 2.0 s | 216 ms | 0.15 |
| Trello | Fails | 3.9 s | 161 ms | 0.24 |
| Monday.com | Passes | 2.4 s | 177 ms | 0.02 |
| ClickUp | Passes | 2.4 s | 169 ms | 0.03 |
| Airtable | Passes | 1.9 s | 103 ms | 0.01 |
| Loom | Fails | 4.2 s | 146 ms | 0.08 |
| Calendly | Fails | 5.3 s | 170 ms | 0.02 |
| Zoom | Fails | 5.5 s | 113 ms | 0.07 |
| Dropbox | Fails | 3.8 s | 245 ms | 0.09 |
| Todoist | Passes | 1.4 s | 96 ms | 0.04 |
| Obsidian | Passes | 1.1 s | 45 ms | 0.00 |
| Discord | Fails | 6.3 s | 299 ms | 0.10 |
| Zapier | Passes | 2.2 s | 126 ms | 0.06 |