A tour of the internals of Chrome's rendering architecture, tracing the steps in the pipeline from web content to display pixels. Concretizes high-level concepts with pointers to important classes and data structures in the codebase.
I tested 26 Chrome extensions to measure their impact on CPU consumption, page download size, and user experience.
Grammarly and Honey are super slow!
The performance impact of individual extensions is usually outweighed by the site being loaded, but they increase power consumption and having many extensions installed adds up
Extension developers can score easy wins by following best practices
"With the DNS prefetching flag in Google Chrome on Android enabled, Chrome scans the page for clickable links and resolves the URLs to IP addresses. By the time you head to any of the pages, their addresses will have been returned to your device, mitigating any DNS speed issues — the only bottleneck will be your own connection. (Optionally, it will use your device’s own DNS servers and won’t touch Google’s unless you want it to.)"
"Le navigateur de Google ne repose pas seulement sur WebKit, également la base de Safari d'Apple, ou des composants issus de Firefox. Il intègre du code Microsoft, comme le souligne sur son blog Scott Hanselman, un développeur indépendant de l'éditeur de