11 ms·

I think web browsers could get framerates on typical webpages to 180 fps if it were a priority. I have found some sites that should be renderable at super high

I think web browsers could get framerates on typical webpages to 180 fps if it were a priority. I have found some sites that should be renderable at super high framerates that struggled to keep an average of 60 fps. One reason that browsers aren't super fast is that it will always be possible to make a super slow site. Speeding up sites like HN is really not very important to battery life or user experience. Also the necessary complexities of the browser make it much harder to get 100% out of your hardware. I would guess that browsers are 3x slower than they could be on most CPU/GPU bound tasks.

jdaxe 4y ago
If there was an incentive for web devs to develop faster-loading and more responsive web pages then they would, e.g if Google search weighted those pages higher in search ranking. (they won't, because then Google would have to rank their own web apps lower)
KronisLV 4y ago
> I think web browsers could get framerates on typical webpages to 180 fps if it were a priority. I have found some sites that should be renderable at super high framerates that struggled to keep an average of 60 fps. Wouldn't it be better if most sites were only redrawn upon user interaction, remaining static most of the time apart from that? Think of the battery life savings!