Performance
Jump to navigation
Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
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)