The RAIL Performance Model: Difference between revisions
Jump to navigation
Jump to search
(Created page with " * https://developers.google.com/web/tools/chrome-devtools/profile/evaluate-performance/?hl=en * Free Course : [https://www.udacity.com/course/browser-rendering-optimization--...") |
No edit summary |
||
| Line 1: | Line 1: | ||
RAIL is a user-centric performance model. Every web app has these four distinct aspects to its life cycle, and performance fits into them in very different ways: Response, Animation, Idle, Load. |
|||
* https://developers.google.com/web/tools/chrome-devtools/profile/evaluate-performance/rail?hl=en |
|||
* https://developers.google.com/web/tools/chrome-devtools/profile/evaluate-performance/?hl=en |
* https://developers.google.com/web/tools/chrome-devtools/profile/evaluate-performance/?hl=en |
||
* Free Course : [https://www.udacity.com/course/browser-rendering-optimization--ud860 Browser Rendering Optimization : Building 60 FPS Web Apps] |
* Free Course : [https://www.udacity.com/course/browser-rendering-optimization--ud860 Browser Rendering Optimization : Building 60 FPS Web Apps] |
||
Latest revision as of 02:02, 1 August 2016
RAIL is a user-centric performance model. Every web app has these four distinct aspects to its life cycle, and performance fits into them in very different ways: Response, Animation, Idle, Load.