&gt; why would you want to render a webpage at several hundred FPS?<p>You wouldn&#x27;t (and the demo shows 60 fps), the point&#x27;s rendering absolutely definitely most certainly isn&#x27;t a bottleneck anymore, which gives more time for<p>&gt; other background tasks<p>or other <i>foreground</i> tasks like the page itself (and the ability to increase its complexity since you don&#x27;t need to budget for rendering anymore), or just letting the CPU go to sleep (could help whatever browser ends up with servo tech finally compete with Safari when it comes to energy consumption).<p>It also gets you in a good place for VR (2 displays and 90Hz minimum IIRC from a Carmack note?) or for ever-larger displays (though that ties into the complexity thing, displays also get finer and denser on mobiles)<p>&gt;  Unless FPS is a multiple of your monitor&#x27;s refresh rate, (i.e. vsync) it won&#x27;t look good.<p>Well you could do that with several hundred FPS anyway, 300FPS is a multiple of 60Hz, so&#x27;s 1540FPS for 140Hz.