This article reviews Google’s pioneering SPDY protocol, its key features and impact on HTTP/2, then explores the disruptive QUIC protocol built on UDP, detailing its connection setup, Diffie‑Hellman encryption, multiplexing, connection migration, and other enhancements that boost web performance.
This article reviews the pioneering SPDY protocol that inspired HTTP/2, then delves into Google's disruptive QUIC protocol—explaining its UDP foundation, Diffie‑Hellman encryption, connection migration, and advanced features that overcome TCP limitations, while comparing their roles in modern web communication.
This article reviews the evolution of web communication protocols, detailing SPDY's pioneering features that influenced HTTP/2 and exploring QUIC's disruptive UDP‑based design, security mechanisms, multiplexing, connection migration, and other enhancements that reshape modern internet performance.
This article explains how HTTP/2 server push works, why it improves page load performance, and provides practical Node‑SPDY code examples for pushing assets, redirects, cache‑validation messages, and integrating Server‑Sent Events to notify clients of pushed resources.
This article details how Qzone’s front‑end and operations teams tackled the 50% slowdown after switching to HTTPS on mobile, using SPDY, TCP and SSL session reuse, domain consolidation, and TLS tuning to shave more than 1000 ms off page load times.
This article translates and expands a performance study that pits HTTPS, SPDY/3.1, and HTTP/2 against each other using Firefox and HttpWatch on Google UK's homepage, revealing trade‑offs in header compression, response size, connection multiplexing, and page‑load speed.
This article details how Alibaba's mobile Taobao app tackled severe H5 performance problems in 2015 by introducing the 521 rule, extensive system analysis, and a series of front‑end, network, and native optimizations—including HTTPDNS, SPDY, image compression, and pre‑loading—that collectively reduced load times dramatically and boosted user metrics.
Ctrip's wireless development team shares a comprehensive overview of their app's network architecture, common performance pitfalls such as DNS and TCP issues, and a series of practical optimizations—including DNS caching, quality detection, priority handling, retransmission, payload reduction, and protocol upgrades—that dramatically improved service success rates and reduced latency.
This article explains the concept of HTTP/2 server push, demonstrates how to implement it using the node‑spdy module with code samples for pushing assets, redirects, and SSE notifications, and discusses practical considerations and future possibilities for optimizing web performance.
