RAIL performance model for web apps

The 4 parts of the RAIL performance model: Response, Animation, Idle, and Load.

User Perception Of Performance Delays
0 to 16ms Users are exceptionally good at tracking motion, and they dislike it when animations aren’t smooth. They perceive animations as smooth so long as 60 new frames are rendered every second. That’s 16ms per frame, including the time it takes for the browser to paint the new frame to the screen, leaving an app about 10ms to produce a frame.
0 to 100ms Respond to user actions within this time window and users feel like the result is immediate. Any longer, and the connection between action and reaction is broken.
100 to 300ms Users experience a slight perceptible delay.
300 to 1000ms Within this window, things feel part of a natural and continuous progression of tasks. For most users on the web, loading pages or changing views represents a task.
1000ms or more Beyond 1000 milliseconds (1 second), users lose focus on the task they are performing.
10000ms or more Beyond 10000 milliseconds (10 seconds), users are frustrated and are likely to abandon tasks. They may or may not come back later.

Test your webpage

 

Leave a comment

Design a site like this with WordPress.com
Get started