Speed Matters at In Control 2014

A9a379f2e92c7ded4564190c5b286b78?s=47 Tim Kadlec
February 18, 2014

Speed Matters at In Control 2014

No one wants to create a slow site. Yet that's exactly what happens. Not only do fat sites exist, they're actually becoming more and more common. It would be one thing if performance was merely another feature, but the reality is that performance is a fundamental component of the user experience.

If we want to start providing people with the fast experiences they so desperately want, performance needs to be engrained throughout the entire process. In this session, we'll discuss how to make sure that our sites are as fast as they are beautiful by incorporating performance into our workflows from start to finish.

Presented at In Control, in Orlando, Florida on February 18th, 2014.

A9a379f2e92c7ded4564190c5b286b78?s=128

Tim Kadlec

February 18, 2014
Tweet

Transcript

  1. 5.
  2. 9.
  3. 14.
  4. 15.
  5. 16.
  6. 17.
  7. 18.

    Minimize JS & CSS Optimize images GZip JS at bottom

    Async scripts Browser caching Avoid redirects
  8. 21.

    I doubt anyone really wants to release a site that

    doesn't perform well, it's just a product of not being afforded the luxury of time and top-down pressure. — a friend.
  9. 28.
  10. 29.
  11. 38.
  12. 39.
  13. 40.
  14. 46.
  15. 53.

    vs

  16. 54.
  17. 55.
  18. 62.

    Speed is the most important feature. If your application is

    slow, people won’t use it....If something is slow, they’re just gone. — Fred Wilson http://bit.ly/csL5ck
  19. 63.

    There is real empirical evidence that substantiates the fact that

    speed is more than a feature. ! It’s a requirement. — Fred Wilson http://bit.ly/csL5ck
  20. 64.

    There is real empirical evidence that substantiates the fact that

    speed is more than a feature. ! It’s a requirement. — Fred Wilson http://bit.ly/csL5ck It’s a requirement.
  21. 82.
  22. 87.
  23. 89.

    Being a Web designer & not considering speed/ performance is

    like being a print designer & not considering how your colors will print. — Luke Wroblewski http://bit.ly/yRvfu8
  24. 93.
  25. 94.
  26. 95.
  27. 96.
  28. 97.
  29. 102.
  30. 103.
  31. 104.
  32. 107.
  33. 109.

    Now more than ever, we’re designing work meant to be

    viewed along a gradient of different experiences. — Ethan Marcotte http://bit.ly/Wi0xvw
  34. 110.

    Now more than ever, we’re designing work meant to be

    viewed along a gradient of different experiences. — Ethan Marcotte http://bit.ly/Wi0xvw Now more than ever, we’re designing work meant to be viewed along a gradient of different experiences. gradient of different experiences
  35. 111.

    Now more than ever, we’re designing work meant to be

    viewed along a gradient of different experiences. — Ethan Marcotte http://bit.ly/Wi0xvw Now more than ever, we’re designing work meant to be viewed along a gradient of different experiences. gradient of different experiences
  36. 113.
  37. 114.
  38. 115.
  39. 116.

    By keeping your client side code small and lightweight, you

    can literally open your product up to new markets. — Chris Zacharias http://bit.ly/Vl1sqy
  40. 118.
  41. 121.
  42. 123.
  43. 124.
  44. 125.
  45. 126.
  46. 127.
  47. 131.

    That was a pretty harsh experience for us. We’d been

    building an app for users like us. But we were the exception, not the rule. — Ragavan Srinivasan
  48. 132.

    That was a pretty harsh experience for us. We’d been

    building an app for users like us. But we were the exception, not the rule. — Ragavan Srinivasan
  49. 134.
  50. 135.
  51. 138.
  52. 139.
  53. 140.
  54. 141.
  55. 150.