Describe the difference between DOMContentLoaded and window.load
This tests critical rendering path knowledge. DOMContentLoaded fires after HTML parsing and deferred scripts, while load waits for all subresources; use the former to bind UI early. RED FLAG: Defaulting to load, which stalls interactivity until images finish.
This tests your understanding of the browser critical rendering path and exact lifecycle timing. A strong answer distinguishes DOMContentLoaded, which fires once HTML is parsed and deferred scripts execute, from window load, which blocks until images, iframes, and async subresources finish. For performance, attach UI listeners and run non-visual setup inside DOMContentLoaded so users can interact while heavy media downloads.
Read the original → developer.mozilla.org
- #web apis
- #performance
- #browser
- #dom
- #interview
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.