Network for Frontend Performances
Network performance is about getting bytes to the browser sooner and in fewer round trips. It covers HTTP/2 and HTTP/3, compression with gzip or Brotli, CDN caching with Cache-Control headers, and resource hints such as preload, preconnect and dns-prefetch that start critical work early.
Stage: Loading · Part of the Frontend Performance roadmap · Last reviewed 19 November 2026
What to learn in Network
- Set Cache-Control and ETag headers for static and dynamic responses
- Compare Brotli and gzip compression for text assets
- Use preconnect for an origin you will definitely need
- Preload the LCP image or a critical font without overusing hints
- Explain what HTTP/2 multiplexing and HTTP/3 over QUIC change
Network interview questions
What is the difference between preload and prefetch?
Preload tells the browser to fetch a resource needed for the current page at high priority. Prefetch fetches a resource likely needed for a future navigation at low priority during idle time. Misusing preload competes with other critical requests.
What does Cache-Control immutable with a long max-age do?
It tells the browser the file will never change at this URL, so it can reuse its cached copy without revalidating until max-age expires. This suits fingerprinted assets whose filenames change when content changes.
Where Network fits in the Frontend Performance roadmap
Network belongs to the Loading stage (intermediate level), which takes about 13 hours. Get bytes to the user.
Other units in this stage
Back to the full Frontend Performance roadmap