The 16.6ms Frame Budget: Why Fast Loads Still Feel Slow

Related: Why CSS Never Matches Figma which is another place where the browser's rendering pipeline creates unexpected gaps. At 60Hz , the browser has ~16.67ms per frame for all JavaScript execution, style calculation, layout, paint, and compositing — combined. This is not a soft guideline. It is a hard physical constraint set by the display's refresh schedule. Miss the deadline and the display repeats the previous frame. Miss it consistently and users perceive jank regardless of what Lighthouse reports. What this covers: Where the 16.6ms number comes from, what work must fit inside one frame, why good Lighthouse scores coexist with bad runtime performance, and why high-frequency data UIs are the most unforgiving stress test for this budget. Where 16.6 ms comes from A 60 Hz panel asks for 60 frames per second . One second divided by 60 is ≈16.67 ms per frameoften rounded to 16.6 ms in conversation. That number is not a browser setting; it is physics of the refresh schedule . If the main