Railway Core Web Vitals
How real Chrome users experience railway.com, from Google's Chrome UX Report: the 75th percentile of visits on every device.
Railway fails Core Web Vitals
Sep 27 – Oct 24, all devices
INP
309 ms
Needs improvement
LCP
3.7 s
Needs improvement
CLS
0.03
Good
FCP
2.2 s
Needs improvement
TTFB
758 ms
Good
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- Railway fails Core Web Vitals on Largest Contentful Paint (3.7 s, good is 2.5 s or less) and Interaction to Next Paint (309 ms, good is 200 ms or less).
- Time to first byte is 758 ms, so most of the LCP time is spent after the first byte: loading the main image, fonts or scripts.
- Among 16 hosting and cloud sites we track, Railway has the 13th fastest LCP.
- INP has improved by 22 ms over the last 25 weeks, from 331 ms to 309 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 ≤ 3.8 s, CLS ≤ 0.10, FCP ≤ 2.3 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 |
| 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 |
| Google Cloud | Fails | 2.9 s | 331 ms | 0.01 |
| 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.2 s | 123 ms | 0.05 |
| Upstash | Passes | 1.4 s | 44 ms | 0.00 |