Skip to the content ForoHackers
Log inJoin

Web performance: start here

Web performance
#925 · Ophuscado · · Report

Web performance is how quickly a page loads, responds and stays smooth, on real devices and real networks. It shapes whether people stay, and it is limited by latency, bandwidth, the work the browser must do and the work the server must do. The rule is to measure first, then change the biggest cost.

Key concepts

  • The critical path: the resources and steps that must finish before the user sees something useful.
  • Latency over bandwidth: round trips, not raw speed, often decide load time; fewer, smaller, earlier requests help.
  • Caching: the fastest request is the one never sent; use cache headers and a content delivery network.
  • Payload size: compress text, size images properly and ship only the code a page needs.
  • Runtime cost: heavy scripts, layout work and long tasks block the single main thread.

Vocabulary

  • Time to first byte: how long until the first part of the response arrives.
  • Render-blocking: a resource that stops the page from being drawn until it loads.
  • CDN: content delivery network, servers near users that cache your files.
  • Lazy loading: delaying resources until they are about to be needed.

What to study, in order

  1. Record a page load in the browser's network and performance panels and find the longest chain.
  2. Throttle the network and the CPU to mimic a modest phone, and test again.
  3. Fix the biggest cost first: compress, cache, resize images or defer a script; measure the change.
  4. Learn the standard user-centred metrics for loading, interactivity and visual stability.
  5. Set a performance budget and check it automatically on every change.

Related tags

#http #browsers #frontend #performance

Log in or join to reply.