(In reply to Emilio Cobos Álvarez (:emilio) from comment #3) > This page also takes forever to load on Chrome desktop fwiw. Hmm, it loads pretty quickly in Chrome-on-Desktop for me. (in normal mode and in their RDM mode) It also loads quickly in Firefox-Nightly-on-Destop (even with content blocking disabled). The key place where I'm seeing a difference is: - Firefox on Android (with no content blocking), which takes 4-5 seconds for our blue loading bar to stop animating on load & reload. ...vs: - Chrome on Android, which takes 1-3 seconds for its blue loading bar to stop animating on load & reload. > I can dig into what the tracker script is trying to do if you think it'd be > helpful Aside from getting content blocking enabled, I think most actionable thing we can do here would be to discover if there's a particular operation (whether in querySelector runtime, or something else) where Chrome is beating us perf-wise, and then see what we can do about closing that gap.
Bug 1503119 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Emilio Cobos Álvarez (:emilio) from comment #3) > This page also takes forever to load on Chrome desktop fwiw. Hmm, it loads pretty quickly in Chrome-on-Desktop for me. (in normal mode and in their RDM mode) It also loads quickly in Firefox-Nightly-on-Destop (even with content blocking disabled). The key place where I'm seeing a difference is: - Firefox on Android (with no content blocking), which takes 4-5 seconds for our blue loading bar to stop animating on load & reload. ...vs: - Chrome on Android, which takes 1-3 seconds for its blue loading bar to stop animating on load & reload. > I can dig into what the tracker script is trying to do if you think it'd be > helpful Aside from getting content blocking enabled, I think most actionable thing we can do here would be to discover if there's a particular operation during the pageload here (whether in querySelector runtime, or something else) where Chrome is beating us perf-wise, and then see what we can do about closing that gap.