Web Performance in Action Building Faster Web Pages (Jeremy Wagner)（Z-Library）

【One-Line Pitch】 A practical field guide to making websites load and render faster for real-world users on constrained devices and networks, covering asset delivery, rendering, footprint reduction, and automated optimization workflows. Best for web developers and front-end engineers who want concrete speed techniques rather than theory. 【Book Arc】 - **Opening (~0%–10%)**: Frames the core problem — web content is growing more complex while infrastructure and devices vary wildly, so slow loads cost you visitors before they see your content. - **Early (~10%–30%)**: Establishes the performance mindset and the levers available: speeding asset delivery, improving rendering, and shrinking overall page footprint. - **Middle (~30%–60%)**: Works through optimization techniques across the asset pipeline — how resources are delivered to the user and how the browser turns them into pixels. - **Late (~60%–85%)**: Moves from one-off fixes to a repeatable workflow that automates common optimization steps so gains persist as the site evolves. - **Ending (~85%–100%)**: Looks ahead to newer protocols and technologies such as HTTP/2, positioning them as the step from "adequate" to "seriously fast." 【Key Takeaways】 - **Performance is a user-retention problem, not a vanity metric** (Opening): Visitors on slow connections or restricted data plans may abandon a site before seeing it, so load speed directly gates whether your content ever gets a chance. (Opening) - **Optimization spans three fronts** (Early): Asset delivery speed, rendering speed, and overall site footprint are treated as distinct but connected targets rather than one vague "make it faster" goal. (Early) - **Delivery and rendering are separate battles** (Middle): Getting bytes to the user quickly and getting the browser to paint quickly are different problems requiring different techniques. (Middle) - **Footprint reduction is a first-class strategy** (Middle): Shrinking what the site ships is presented as a core lever alongside delivery and rendering improvements. (Middle) - **Automation turns optimization into a workflow** (Late): The book treats common optimization techniques as things to be scripted and repeated, not manually reapplied each release. (Late) - **HTTP/2 changes the performance playbook** (Ending): Newer protocols are framed as the difference between merely adequate and genuinely fast sites, meaning older assumptions may need revisiting. (Ending) 【Reading Tips】 - Read the opening framing carefully — it justifies why performance work matters and sets the vocabulary used throughout. - Treat the middle chapters as the hands-on core: expect to apply delivery, rendering, and footprint techniques to your own site as you go. - Pay special attention to the workflow/automation material if you maintain a build pipeline; that's where gains become durable. - Don't skip the HTTP/2 discussion even if you're not migrating yet — it reframes earlier advice and is worth understanding before you commit to legacy optimizations. 【Coverage Limits】 The available excerpts cover only the book's framing and high-level promises; specific techniques, code examples, chapter structure, and measured results are not covered here.