webperf

Just realized that posting a #webperf blog post not related to #velocityconf was probably a bad idea this week. #facepalm

— Stephen Pierzchala (@spierzchala)2012-10-03 09:34:59

Beautiful visualisations of webpage dependencies being shown by Rajiv Vijayakumar of Qualcomm #webperf #velocityconf

— Andy Davies (@andydavies)2012-10-03 09:30:25

RT @jeroentjepkema: Nice,the @lognormal guys introduce a new #webperf metric: LD50.. When does the page speed increases the bouncerate ...

— Andrew Custard (@AndrewCustard)2012-10-03 09:23:04

RT @cliffcrocker: who knew that latency measurement began in the late 1700s? @bluesmoon @bbrewer #velocityconf #boomerang #webperf

— Tom Taylor (@tom_taylor)2012-10-03 06:47:28

RT @cliffcrocker: @bbrewer introduces the LD50 for #webperf after 3.5s load time is lethal dose where 50% of users bounce! #velocityconf

— Tom Taylor (@tom_taylor)2012-10-03 06:47:01

RT @jeroentjepkema: Nice,the @lognormal guys introduce a new #webperf metric: LD50.. When does the page speed increases the bouncerate ...

— Chris Addis (@chrisaddis)2012-10-03 06:44:19

RT @cliffcrocker: @bbrewer introduces the LD50 for #webperf after 3.5s load time is lethal dose where 50% of users bounce! #velocityconf

— Perry Dyball (@iamnmtd)2012-10-03 06:43:43

Nice,the @lognormal guys introduce a new #webperf metric: LD50.. When does the page speed increases the bouncerate above 50%? #velocityconf

— Jeroen Tjepkema (@jeroentjepkema)2012-10-03 06:41:55

RT @cliffcrocker: @bbrewer introduces the LD50 for #webperf after 3.5s load time is lethal dose where 50% of users bounce! #velocityconf

— Fred Beringer (@fredberinger)2012-10-03 06:41:09

@bbrewer introduces the LD50 for #webperf after 3.5s load time is lethal dose where 50% of users bounce! #velocityconf

— Cliff Crocker (@cliffcrocker)2012-10-03 06:38:27