velocityconf

If you're at #velocityconf and want to chat about Tasseo, track down @obfuscurity. Big guy wearing a green shirt and khaki shorts.

— Tasseo (@tasseo_dev)2012-06-25 13:11:35

Follow @estellevw slides about Mobile Web App Performance on your own computer at http://t.co/A9igtlBO #VelocityConf #reallyclever

— Pingdom (@pingdom)2012-06-25 13:10:44

Bryan McQuade says, "focus on user-perceived latency." Awesome, can we get some guidance on the relevant metrics? #velocityconf

— Elizabeth Ayer (@ElizAyer)2012-06-25 13:10:12

Avoid document.write, CSS import #velocityconf

— sideroad (@side_road)2012-06-25 13:09:25

"Every performance problem at Typekit is something we don't yet measure, all scaling pain points were unexpected" -@ph #velocityconf

— Joel Barciauskas (@jbarciauskas)2012-06-25 13:09:24

@cscotta I haven't done a complete survey, that was mostly a quote from #velocityconf by @ph

— Joel Barciauskas (@jbarciauskas)2012-06-25 13:08:39

.@bryanmcquade (Google) does nice demo of Critical path explorer to show waterfalls in a new way. Coming soon. #VelocityConf

— Pingdom (@pingdom)2012-06-25 13:08:34

RT @amrithkumar: looking fwd to a gr8 #velocityconf. Monday at 0845 ppl are asking "vere is gin?" (see pic) http://t.co/BXhZpWKY

— Greg Arnette (@gregarnette)2012-06-25 13:07:52

When building the "minimum viable product", use "minimum viable infrastructure" - you're not facebook or etsy, yet. #velocityconf

— Joel Barciauskas (@jbarciauskas)2012-06-25 13:06:58

"Important to understand what you are measuring and optimizing for" #webperf #velocityconf

— Dits kenny (@kenny_dee)2012-06-25 13:06:33