10 KiB
| title | chunk | source | category | tags | date_saved | instance |
|---|---|---|---|---|---|---|
| RAIL - Glossary | MDN | 1/3 | https://developer.mozilla.org/en-US/docs/Glossary/RAIL | reference | web, html, css, javascript, documentation | 2026-05-05T05:41:43.686010+00:00 | kb-cron |
MDN HTML HTML: Markup language
HTML reference
HTML guides
Markup languages
CSS reference
CSS guides
Layout cookbook
JavaScriptJS JavaScript: Scripting language
JS reference
JS guides
Web APIs Web APIs: Programming interfaces
Web API reference
Web API guides
- Using the Web animation API
- Using the Fetch API
- Working with the History API
- Using the Web speech API
- Using web workers
Technologies
Topics
Learn Learn web development
Frontend developer course
- Getting started modules
- Core modules
- MDN Curriculum
- Check out the video course from Scrimba, our partner
Learn HTML
Learn CSS
Learn JavaScript
Tools Discover our tools
About Get to know MDN better
RAIL
RAIL , an acronym for Response, Animation, Idle, and Load , is a performance model originated by the Google Chrome team in 2015, focused on user experience and performance within the browser. The performance mantra of RAIL is "Focus on the user; the end goal isn't to make your site perform fast on any specific device, it's to make users happy." There are 4 stages of interaction: page load, idle, response to input, and scrolling and animation. In acronym order, the main tenets are:
Respond to users immediately, acknowledging any user input in 100ms or less.
When animating, render each frame in under 16ms , aiming for consistency and avoiding jank.
When using the main JavaScript thread, work in chunks for less than 50ms to free up the thread for user interactions.
Deliver interactive content in less than 5 second.