Close Mode: Why Browsers show different performance results

Зображення до статті Close Mode: Why Browsers show different performance results
Зображення до статті Close Mode: Why Browsers show different performance results

The article considers as browsers, including Chrome and Safari, not only download resources such as images and scripts, but also how they priority these resources. Chrome and Safari have introduced a "close mode" that limits which resources are loaded and in what order, but they choose quite different approaches to this.

🚀 "Close Mode" is a way in which browsers load resources from the server. In this mode, browsers limit the loading of low priority resources to the time when the body of the document is connected to the document (after execution of all blocking scripts in the title).

🧠 Understanding "close mode" can be difficult because it includes a number of nuances. For example, in Chrome and Safari, the "tight" mode is performed differently. In Chrome it is activated only in the presence of a locking javascript inwhile in Safari it is activated in the presence of a blocking JavaScript or CSS anywhere in the document.

  • 📌 Browsers use "close mode" to prioritize resource loading.
  • 📌 Chrome and Safari implement "close mode" differently.
  • 📌 Firefox does not use "close mode".
🧩 The result: "close mode" is a method by which browsers priority loading resources. Chrome and Safari use this mode, but adjust it differently. Firefox does not use "close mode".
🧠 Own considerations: understanding of "close mode" and its impact on the performance of the browser can be useful when optimizing websites. Considering the differences in the implementation of this mode in Chrome and Safari, developers can use this information to adjust the resource -shaking of resources in such a way as to improve the performance of the site in both browsers.