Performance for Frontend Developers
Frontend performance is how quickly a page loads, responds and stays smooth. Core Web Vitals measure it with Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift. Improving it involves smaller bundles, optimised images, caching, code splitting and avoiding long main-thread tasks.
Stage: Quality and Performance · Part of the Frontend Developer roadmap · Last reviewed 19 November 2026
What to learn in Performance
- Read a Lighthouse report and find the largest bottleneck
- Fix layout shift by reserving space for images and embeds
- Split a bundle with dynamic imports and lazy routes
- Serve responsive images in modern formats with correct sizes
- Find a long task in the Performance panel and break it up
Performance interview questions
What do the three Core Web Vitals measure?
Largest Contentful Paint measures how fast the main content appears, Interaction to Next Paint measures how quickly the page responds to input, and Cumulative Layout Shift measures unexpected movement of content while loading. Together they approximate the loading, interactivity and stability a user feels.
How do you reduce a slow Largest Contentful Paint?
Find the LCP element, often a hero image, and shorten each delay: speed up the server response, preload the image, compress and size it properly, avoid lazy-loading it, and remove render-blocking CSS and JavaScript ahead of it.
Where Performance fits in the Frontend Developer roadmap
Performance belongs to the Quality and Performance stage (beginner level), which takes about 4 hours. Make it fast, accessible, secure and tested.
Other units in this stage
Back to the full Frontend Developer roadmap