![]() ![]() Why 50ms? The RAIL model suggests you process user input events in 50ms to ensure a visible response within 100ms. Clicks and taps often don't work because event listeners, click handlers etc have not yet been attached.ĬPU-heavy Long Tasks occur due to complex work that takes longer than 50ms. While a web page is loading, Long Tasks can tie up the main thread and make the page unresponsive to user input even if it looks ready. But did you know Long (JavaScript) Tasks can contribute heavily to a poor TTI? What are Long Tasks? #Ī Long Task is JavaScript code that monopolizes the main thread for extended periods of time, causing the UI to "freeze". If you use Lighthouse to audit your pages, you may be familiar with Time to Interactive, a metric representing when users can interact with your page and get a response. Chrome DevTools can now visualize Long Tasks, making it easier to see tasks to optimize. Tl dr: Long Tasks can keep the main thread busy, delaying user interaction. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |