openskills.info
Course Preview

Web Performance

Web performance is the discipline of making a site load, respond, and remain visually stable for real users. It combines delivery, browser rendering, JavaScript work, and measurement so the page feels fast on the devices and networks people actually use.

itWeb development

Don't Panic: Web Performance

Web performance is the work of making a page useful, responsive, and steady for the person on the other side of the connection. It is not the small green number you receive from a browser tool, though the number may be trying its best. It is the whole route from request to visible content, then from input to an updated screen.

A page is a relay race with a strong preference for tripping over its own shoelaces. The request reaches an origin or cache. HTML arrives. The browser finds resources, transfers them, runs code, lays out pixels, and eventually agrees that a button may be pressed. A delay at any point can become the delay the reader remembers.

Three Core Web Vitals keep the conversation tied to what people notice. Largest Contentful Paint, or LCP, asks when the largest useful element becomes visible. Interaction to Next Paint, or INP, asks how long an interaction waits before its visual result appears. Cumulative Layout Shift, or CLS, catches content that moves after somebody has already aimed at it. They are loading, responsiveness, and stability wearing sensible name badges.

The surprising part is that one test run cannot settle the matter. Field data comes from real page loads and reveals the outcome across actual devices and connections. Lab data comes from a controlled run and gives you a trace, waterfall, and a repeatable scene of the crime. If they disagree, neither has betrayed you. The disagreement tells you that a route, cache state, device, or network condition still needs a name.

For loading, inspect the gaps from Time to First Byte to First Contentful Paint and then to LCP. For interaction, inspect the main thread and its long tasks. For stability, reserve space for images, video, fonts, and late-arriving widgets before they begin rearranging the furniture. The browser does not regard the button you meant to press as a sentimental object.

Start with the Intro for the full path and the vocabulary. Use the Slides when you need the relationships in one view. Keep the Cheatsheet nearby while reading a trace or waterfall. The Practice tab turns the evidence loop into a repeatable investigation, and the Exercise asks you to prove one improvement without changing the weather, the network, and three unrelated files at once.

Where this skill leads

Relevant careers

See how this topic contributes to broader role-level skill maps.

Sources

  • https://web.dev/articles/vitals
  • https://web.dev/articles/optimize-lcp
  • https://web.dev/articles/optimize-inp
  • https://web.dev/articles/cls
  • https://developer.mozilla.org/en-US/docs/Web/API/Performance_API
  • https://www.w3.org/TR/navigation-timing-2/
  • https://www.w3.org/TR/resource-timing/
  • https://www.w3.org/TR/longtasks/
  • https://github.com/davidsonfellipe/awesome-wpo
  • https://www.w3.org/2018/09/webperf/
  • https://www.w3.org/standards/history/navigation-timing/
  • https://www.w3.org/TR/user-timing-1/
  • https://www.w3.org/TR/2013/REC-performance-timeline-20131212/
  • https://www.w3.org/2014/07/mobile-web-app-state/Overview.pdf
  • https://www.rfc-editor.org/rfc/rfc7540
  • https://www.w3.org/TR/hr-time-2/
  • https://web.dev/blog/inp-cwv-march-12
  • https://www.etsy.com/codeascraft/q1-2015-site-performance-report
  • https://www.etsy.com/uk/codeascraft/q1-2016-site-performance-report
  • https://medium.com/pinterest-engineering/driving-user-growth-with-performance-improvements-cfc50dafadd7
  • https://www.debugbear.com/features
  • https://www.cloudflare.com/
  • https://www.fastly.com/
  • https://www.akamai.com/
  • https://www.speedcurve.com/
  • https://calibreapp.com/