Behance Core Web Vitals
How real Chrome users experience www.behance.net, from Google's Chrome UX Report: the 75th percentile of visits on every device.
Behance fails Core Web Vitals
Sep 25 – Oct 22, all devices
INP
144 ms
Good
LCP
3.0 s
Needs improvement
CLS
0.03
Good
FCP
2.1 s
Needs improvement
TTFB
1.5 s
Needs improvement
INP over time
Weekly p75. The dashed line is the 200 ms "good" threshold.
What the numbers say
- Behance fails Core Web Vitals on Largest Contentful Paint (3.0 s, good is 2.5 s or less).
- The server answers slowly: time to first byte is 1.5 s, 52% of the LCP time, so a faster backend or cache would help most.
- Among 9 design sites we track, Behance has the 6th fastest LCP.
- INP has held steady around 145 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 ≤ 3.0 s, CLS ≤ 0.10, FCP ≤ 2.2 s.