Resource Loading at the Cutting Edge
summary
Browsers disagree about real priority behavior (fonts are highest in Chrome but low in Firefox), HTTP/2 uses a complex prioritization tree while HTTP/3 carries an urgency 0–7 plus an incremental flag, Chrome recently flips incremental defaults, and backend deployments frequently ignore browser signals — testing finds only two of these companies do this correctly; tooling matters: netlog and wireshark reveal packet-level truth, WebPageTest and DevTools can mislead because they hide chunk timing and priority changes.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:22The state of performance
- 2:50Resource priority basics
- 5:16HTTP/2 vs HTTP/3
- 8:59Sword fighting analogy
- 11:56Browser inconsistency
- 16:14Protocol issues
- 19:07Server behavior testing
- 25:16Mitigating factors
- 28:45Two-phase loading
- 34:32Tooling limitations
- 40:38Debug challenges
- 44:07Industry call to action
- 46:56Conclusion and demo
related talks
42mResource loading, prioritization, HTTP/2 - oh my!
51mHTTP/2 priorities
37mThe Critical Request: An investigation into what blocks render
39mWhat’s new in performance?
19mHTTP/2 is here, now let's make it easy
21mState of Performance
38mCSS and the first meaningful paint
30mHigh Performance in the Critical Rendering Path