2013 articles with this tag
A lab metric that adds up how long the main thread was blocked by long tasks between the first paint and the page becoming reliably interactive. Why does it mat...
The difference between performance measured in a controlled test, such as Lighthouse, and performance measured from real visitors' devices and connections. At a...
A public dataset of real-user performance measurements collected from Chrome users who have opted in, reported for origins and popular URLs. What is at stake Cr...
Google's free tool that reports real-user Core Web Vitals from the Chrome UX Report alongside a Lighthouse lab test for a given URL. The key figures Field secti...
The browser's main thread handles layout, painting and most JavaScript, and any single task that runs for more than 50 milliseconds blocks it from responding to...
Background threads that run JavaScript separately from the page's main thread, used for heavy computation such as parsing data, image processing or search index...
Removing unused code from JavaScript bundles during the build, so visitors only download the functions a page actually uses. At a glance Tree shaking dead-code...
Compressing HTML, CSS, JavaScript and other text responses on the server so they transfer in far fewer bytes, then decompressing them in the browser. What is at...
Delivering the styles needed to render the visible part of the page immediately, often inline in the HTML, and loading the rest of the CSS without blocking rend...
Deferring the download of images until they are about to scroll into view, using the loading="lazy" attribute or a script. Where most projects go wrong The usua...
Using the CSS content-visibility property so the browser skips layout and painting for sections of a long page that are off screen until they are needed. Why do...
A browser API that reports rendering frames that took longer than 50 milliseconds, with details of the scripts responsible, used to diagnose slow interactions....
Showing 1,932 of 2,013
