Related to the discipline of improving the performance of web pages. Performance may be measuring page load time, memory usage, UI jankiness, Rendering time, etc.

- Wiki
6 articles, 0 books.

When web browsers need to draw updates to a page, like for scrolling or animations, they typically draw up to 60 times a second. Each drawing pass is called a frame. To have completely smooth animations and scrolling behavior, the browser can spend no more than 1000ms/60 (or 16.67ms) on each frame.

In this post we’ll be discussing lots of ways to tune web servers and proxies. Please do not cargo-cult them. For the sake of the scientific method, apply them one-by-one, measure their effect, and decide whether they are indeed useful in your environment.

Byte-for-byte, JavaScript is still the most expensive resource we send to mobile phones, because it can delay interactivity in large ways.

There are no silver bullets to web performance. Simple static pages benefit from being server-rendered with minimal JavaScript. Libraries can provide great value for complex pages when used with care.

Let’s make 2019… fast! An annual front-end performance checklist, with everything you need to know to create fast experiences today. Updated since 2016.

Climate change may not seem like an issue that should concern web developers, but the truth is that our work does have a carbon footprint, and it’s about time we started to think about that.