Tim Kadlec - Akamai
Performance is a cultural issue
Lack of performance = lack of planning
Post-optimization is the root of all evil, because it never happens.
Performance impacts all business and technical KPIs.
-
a clearly defined performance goal
-
4 types
- Quantity-based: (# of requests, total bytes)
- Rule-based: (PageSpeed Insights, ySlow, Grades)
- Milestone Timing: (time to first byte, start render, DOM content loaded)
- We can create our own: Custom Timeline Marks
- We probably have our own milestone metrics, like Twitter does with time to first tweet
- An obvious one would be displaying first and last name on dialer connections
- Speed Index (Percent visually complete) - lower is better. < 1000 is great
NO LINK TO UX <========================> CLOSEST UX
1............2....................................3.........................................4................
A combination of metrics is best to communicate total performance.
Improvements to performance are best made in 20% increments. That's the threshold at which most people will notice change. It's also less daunting to improve incrementally.
You can work backwards too. Use an approximate kb/s connection speed to calculate page weight for a target load time.
Enforcing performance budgets can be automated.