OpenAI Core Web Vitals
How real Chrome users experience openai.com, from Google's Chrome UX Report: the 75th percentile of visits on every device.
OpenAI fails Core Web Vitals
Sep 26 – Oct 23, all devices
INP
219 ms
Needs improvement
LCP
2.9 s
Needs improvement
CLS
0.00
Good
FCP
2.6 s
Needs improvement
TTFB
1.3 s
Needs improvement
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- OpenAI fails Core Web Vitals on Largest Contentful Paint (2.9 s, good is 2.5 s or less) and Interaction to Next Paint (219 ms, good is 200 ms or less).
- The server answers slowly: time to first byte is 1.3 s, 46% of the LCP time, so a faster backend or cache would help most.
- Among 10 ai sites we track, OpenAI has the 7th fastest LCP.
- INP has held steady around 223 ms over the last 25 weeks.
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 ai sites
| Site | Core Web Vitals | LCP | INP | CLS |
|---|---|---|---|---|
| ChatGPT | Fails | 4.2 s | 669 ms | 0.17 |
| Anthropic | Passes | 1.4 s | 67 ms | 0.00 |
| Claude | Fails | 2.7 s | 157 ms | 0.01 |
| Hugging Face | Passes | 1.1 s | 51 ms | 0.00 |
| Perplexity | Fails | 4.6 s | 353 ms | 0.03 |
| Midjourney | Fails | 2.7 s | 223 ms | 0.00 |
| Mistral AI | Fails | 2.9 s | 101 ms | 0.08 |
| Replicate | Passes | 2.4 s | 73 ms | 0.08 |
| Groq | Passes | 1.1 s | 95 ms | 0.00 |