Metrics for Frontend Performances
Performance metrics are the numbers that describe how a page feels to users. Core Web Vitals, namely Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift, are the main ones. Lab tools like Lighthouse give controlled results, while field data from real users shows what actually happens.
Stage: Measure · Part of the Frontend Performance roadmap · Last reviewed 19 November 2026
What to learn in Metrics
- Define LCP, INP and CLS and state the good threshold for each
- Run Lighthouse and WebPageTest and read the results correctly
- Explain why lab and field data can disagree
- Pull field data from the Chrome UX Report or PageSpeed Insights
- Use the DevTools Performance panel to attribute a slow interaction
Metrics interview questions
Why can Lighthouse and real user data give different scores?
Lighthouse runs one simulated load on a fixed device and network, while field data aggregates many real visits across devices, networks, caches and interactions. Lab runs also cannot measure INP properly without scripted input, so differences are normal.
What replaced First Input Delay as a Core Web Vital?
Interaction to Next Paint replaced First Input Delay. FID only measured the delay before the first interaction was handled, while INP observes all interactions during a visit and reports a high percentile of their full latency, including processing and the next paint.
Where Metrics fits in the Frontend Performance roadmap
Metrics belongs to the Measure stage (beginner level), which takes about 10 hours. Know your numbers.
Other units in this stage
Back to the full Frontend Performance roadmap