System Design bank Browser System Design / 20 questions Your progress 0 / 20 done Saved in this browser. Reset All 20 Easy 10 Hard 10 Hide done No questions match those filters. 01 Walk through the full browser rendering pipeline from HTML parsing to pixels on screen. Easy 02 Design a page-load sequence that minimizes blocking during the rendering pipeline. Hard 03 Explain the Critical Rendering Path and how render-blocking resources affect it. Easy 04 Optimize a page with render-blocking CSS and synchronous scripts in the head - what's your plan? Hard 05 Explain the DOM tree structure and how the browser constructs it from HTML. Easy 06 Debug a memory leak caused by detached DOM nodes still referenced in JavaScript. Hard 07 Explain the CSSOM and why CSS is considered render-blocking. Easy 08 Explain how the browser combines the DOM and CSSOM into the render tree. Hard 09 Explain the difference between the style, layout, and paint stages. Easy 10 Debug a page with unexpectedly high style recalculation cost. Hard 11 Explain what triggers a reflow and why reflows are expensive. Easy 12 Debug a script that reads offsetHeight in a loop and causes layout thrashing - how do you fix it? Hard 13 Explain the difference between reflow and repaint, and which CSS properties trigger which. Easy 14 Design an animation that avoids triggering repaint or reflow using only compositor-friendly properties. Hard 15 Explain how the browser's compositor thread works independently of the main thread. Easy 16 Explain why transform and opacity animations are cheaper than animating top/left. Hard 17 Explain how the browser decides to promote an element to its own compositor layer. Easy 18 Debug a page with excessive layer count causing memory bloat (layer explosion). Hard 19 Explain how GPU acceleration works for compositing and when it can hurt performance. Easy 20 Design a smooth 60fps drag-and-drop interaction leveraging GPU-accelerated properties. Hard ← Previous JavaScript Next → Performance