Closed Bug 1383234 Opened 3 years ago Closed 3 years ago
Don't throttle Leader and Unblocked resources
When we throttle load of <head> referenced script, yes, trackers can be even there (see cnn.com), we prolong time to window.onload. That's undesirable.
Summary: Don't throttle Blocking and LoadUnblocked resources → Don't throttle Leader and Unblocked resources
self explanatory. reason: some trackers can be referenced in <head>. when we slow them down we postpone onload event. That handler may easily trigger load of a vital display content dynamically, hence, it makes sense to never throttle leaders. https://treeherder.mozilla.org/#/jobs?repo=try&revision=6917d3d6063a5e93f878de977edf6d54737d12b8
Attachment #8889518 - Flags: review?(mcmanus)
Attachment #8889518 - Flags: review?(mcmanus) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/8af1672af38d Don't throttle Blocking/Unblocked marked HTTP responses. r=mcmanus
You need to log in before you can comment on or make changes to this bug.