4 ms·
Google lately "optimized" Chrome "time for the first page to load" by no longer waiting for extensions to initialize properly. First website you load bypasses a
by rasz 6y ago
Google lately "optimized" Chrome "time for the first page to load" by no longer waiting for extensions to initialize properly. First website you load bypasses all privacy/ad blocking extensions.
- raf42 6y agoThank you for confirming this, I thought I was going crazy seeing it happen a bunch recently. I assumed my system was just on the fritz.
- Cthulhu_ 6y agoYeah I think that's the kind of odd behaviour that those KPI's end up causing; they 'cheat' the benchmark by avoiding certain behaviour, like loading extensions later. I mean I can understand it, a lot of extensions don't need to be on the critical path. But at the same time, I feel like Chrome could do things a lot better with extensions, such as better review policy and compiling them to wasm from the extensions store.
- saruken 6y agoWow, had no idea about this! Can you link me to a writeup or something?
- rasz 6y agohttps://github.com/Tampermonkey/tampermonkey/issues/1083 https://github.com/Tampermonkey/tampermonkey/issues/1083 confirmed by Tampermonkey dev.
- sundvor 6y agoI hope the Edge team never merges this in.
- rasz 6y agoIts been in Chrome since 81, Id wager a guess its in Edge and nobody noticed.