Twitter Catches the ‘SPDY’ Train
Twitter has embraced Google's vision of a faster web and is now serving webpages over the SPDY protocol to browsers that support it. — SPDY, pronounced “speedy,” is a replacement for the HTTP protocol — the language currently used when your browser talks to a web server.
Context & Ripple Effects
Twitter's move to serve twitter.com over SPDY extends a performance push Google has been running since its Speed Tracer tool for diagnosing slow web apps launched in December 2009. SPDY replaces the HTTP request model between browser and server, and Twitter is enabling it selectively — only browsers that speak the protocol get it.
The significance is who is adopting, not what the technology is: SPDY until now has been closely identified with Google's own properties, and a top-tier consumer site like Twitter switching it on is the first broad signal that the protocol could travel beyond its creator. The story drew no syndicated pickup or public discussion in the corpus, so the ripple effects below rest mainly on the confirmed deployment itself.
First-order effects
- Visitors to twitter.com using SPDY-capable browsers — Chrome foremost among them — get faster page loads, while everyone else sees no change, making browser support a visible performance differentiator.
- Google gains a marquee third-party validation for SPDY outside its own fleet, strengthening its case when lobbying other sites and server vendors.
Second-order effects
- Other high-traffic consumer sites face pressure to evaluate SPDY support so they don't lag Chrome-optimized rivals on perceived speed; web server and CDN vendors gain a customer-driven reason to implement the protocol.
- Browser makers without SPDY support see a widening real-world gap on major sites, raising the cost of staying out of Google's faster-web camp.
Third-order effects
- If more large sites follow Twitter, a Google-designed protocol becomes de facto web infrastructure, forcing the question of whether SPDY should be standardized under neutral stewardship rather than remain one company's experiment.
- Site-by-site protocol adoption splits the web into fast lanes for modern browsers and legacy behavior elsewhere, making client upgrade cycles a bottleneck for web-wide performance gains.
The trend: Web delivery is drifting from the universal HTTP baseline toward faster transport protocols incubated inside single vendors, with big consumer sites' adoption decisions determining whether they stay proprietary experiments or harden into standards.