Google Cloud Core Web Vitals
How real Chrome users experience cloud.google.com, from Google's Chrome UX Report: the 75th percentile of visits on every device.
Google Cloud fails Core Web Vitals
Sep 26 – Oct 23, all devices
INP
331 ms
Needs improvement
LCP
2.9 s
Needs improvement
CLS
0.01
Good
FCP
2.6 s
Needs improvement
TTFB
1.4 s
Needs improvement
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- Google Cloud fails Core Web Vitals on Largest Contentful Paint (2.9 s, good is 2.5 s or less) and Interaction to Next Paint (331 ms, good is 200 ms or less).
- The server answers slowly: time to first byte is 1.4 s, 49% of the LCP time, so a faster backend or cache would help most.
- Among 16 hosting and cloud sites we track, Google Cloud has the 11th fastest LCP.
- INP has improved by 47 ms over the last 25 weeks, from 390 ms to 343 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 ≤ 2.9 s, CLS ≤ 0.10, FCP ≤ 2.6 s.
Other hosting and cloud sites
| Site | Core Web Vitals | LCP | INP | CLS |
|---|---|---|---|---|
| Vercel | Fails | 4.4 s | 194 ms | 0.02 |
| Netlify | Passes | 1.6 s | 166 ms | 0.01 |
| Cloudflare | Passes | 1.6 s | 158 ms | 0.00 |
| Render | Passes | 1.8 s | 124 ms | 0.00 |
| Railway | Fails | 3.7 s | 309 ms | 0.03 |
| Fly.io | Passes | 2.3 s | 61 ms | 0.01 |
| Heroku | Passes | 1.4 s | 78 ms | 0.01 |
| DigitalOcean | Passes | 1.6 s | 82 ms | 0.00 |
| AWS | Fails | 3.2 s | 133 ms | 0.02 |
| Supabase | Fails | 3.8 s | 190 ms | 0.03 |
| Neon | Passes | 1.4 s | 44 ms | 0.00 |
| PlanetScale | Passes | 1.1 s | 46 ms | 0.00 |
| Firebase | Fails | 2.6 s | 111 ms | 0.05 |
| MongoDB | Fails | 4.1 s | 124 ms | 0.06 |
| Upstash | Passes | 1.3 s | 44 ms | 0.00 |