VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 2
30 Jun 2010
Yesterday, Network World posted part 1 of our whiteboard session where I talked about the performance problems faced by today’s websites: browser differentiation, web page complexity and size, and user expectations.
In part 2, I talk about the solution landscape, including CDNs and ADCs, and I explain why these don’t address all the opportunities for site optimization:
I also talk about how the Strangeloop Site Optimizer takes advantage of some unique optimization opportunities. I don’t normally use this blog to flog product, but I get a lot of requests to explain how exactly Site Optimizer works. If you’re wondering, this is the chance to find out.
Tweets that mention VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 2 — Web Performance Today -- Topsy.com
Jun 30, 2010 @ 13:55:01
[...] This post was mentioned on Twitter by Melissa Chadwick. Melissa Chadwick said: RT @strangeloopnet VIDEO: Everything you wanted to know about web performance, part 2 http://bit.ly/bLPCt6 /@NetworkWorld [...]
VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 1 — Web Performance Today
Jul 07, 2010 @ 13:15:04
[...] VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 2 → [...]
Cheat Sheet: Everything you wanted to know about web performance but were afraid to ask — Web Performance Today
Jul 07, 2010 @ 13:16:58
[...] Everything you wanted to know about web performance but were afraid to ask, part 1 VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 2 The 16 Best Graphs of Velocity: A snapshot of the current web performance [...]
Defining the Web Performance Problem: Payload, page complexity and the browser wars — Web Performance Today
Jul 07, 2010 @ 22:15:21
[...] VIDEO: Everything you wanted to know about web performance but were afraid to ask, part 2 [...]
Oct 01, 2010 @ 03:00:59
When you talk about delivering different content to different browsers, that sounds a lot like browser sniffing. How do you avoid the adverse effects that browser sniffing has?