Difference between revisions of "Performance"
Jump to navigation
Jump to search
(Created page with "==Performance guidelines== * Ideally, every page loads in '''200ms'''. (Why half of the Doherty threshold? Because if it’s 200ms in the US on a high-speed connection and rel...") |
|||
| Line 3: | Line 3: | ||
* There is no top-level loading number recommendation from UX, because it's a very context-specific decision. | * There is no top-level loading number recommendation from UX, because it's a very context-specific decision. | ||
* Worst case scenario is that the connection consistently times out or the volume of data crashes the user’s browser – we consider both of these cases total user experience failure and they should be avoided. | * Worst case scenario is that the connection consistently times out or the volume of data crashes the user’s browser – we consider both of these cases total user experience failure and they should be avoided. | ||
==Additional Resources== | |||
* [https://uxdesign.cc/what-you-should-know-about-skeleton-screens-a820c45a571a Everything you need to know about skeleton screens] | |||
* [https://medium.com/@juneuprising/designing-for-the-appearance-of-speed-aaabc7f568c2 Designing for the appearance of speed] | |||
* [https://medium.com/uxd-talks/engaging-users-with-progressive-loading-in-skeleton-screen-335a4e287a55 Engaging users with progressive loading in skeleton screen] | |||
* [https://www.lukew.com/ff/entry.asp?1797] | |||
* [https://www.youtube.com/watch?v=EbbjEY-TyhU&feature=youtu.be&t=4136] | |||
* [https://infrequently.org/2021/03/the-performance-inequality-gap/ The Mobile Performance Inequality Gap] (2021) | |||
* [https://jlelliotton.blogspot.com/p/the-economic-value-of-rapid-response.html The Economic Value of Rapid Response Time] by [[Jim Elliot]] | |||
* [https://www.researchgate.net/publication/234791131_The_importance_of_percent-done_progress_indicators_for_computer-human_interfaces The importance of percent-done progress indicators for computer-human interfaces] by [[Brad A. Myers]] (1985) | |||
* [http://yusufarslan.net/sites/yusufarslan.net/files/upload/content/Miller1968.pdf Response time in man-computer conversational transactions] by [[Robert B. Miller]] (1968) | |||
[[Category:Development]] | [[Category:Development]] | ||
Latest revision as of 05:41, 18 June 2021
Performance guidelines
- Ideally, every page loads in 200ms. (Why half of the Doherty threshold? Because if it’s 200ms in the US on a high-speed connection and relatively new hardware, it’s going to be slower for anyone not-US, not-high-speed or not-new-hardware, and we want to do our best to stay under the Doherty threshold in those situations.)
- There is no top-level loading number recommendation from UX, because it's a very context-specific decision.
- Worst case scenario is that the connection consistently times out or the volume of data crashes the user’s browser – we consider both of these cases total user experience failure and they should be avoided.
Additional Resources
- Everything you need to know about skeleton screens
- Designing for the appearance of speed
- Engaging users with progressive loading in skeleton screen
- [1]
- [2]
- The Mobile Performance Inequality Gap (2021)
- The Economic Value of Rapid Response Time by Jim Elliot
- The importance of percent-done progress indicators for computer-human interfaces by Brad A. Myers (1985)
- Response time in man-computer conversational transactions by Robert B. Miller (1968)