If the user is watching YouTube, the system is spending most of its non-idle time downloading chunks of video, shoveling them into the decoder, and piping the output to the screen. This is a heavily hardware-accelerated workflow, and is quite efficient. The structure of the YouTube web app helps, too; it's a (well disguised) single-page app, so the browser doesn't even have to reload/reparse scripts when navigating from one video to another.
Browsing web pages is much more chaotic. As the user scrolls through the page, the system is having to render parts of the page (on the CPU), evaluate CSS rules, run scripts... the works. When the user navigates to a new page, that's a whole bunch of new HTML, CSS, and scripts that have to be parsed. And so on.
duskwuff|3 years ago
Browsing web pages is much more chaotic. As the user scrolls through the page, the system is having to render parts of the page (on the CPU), evaluate CSS rules, run scripts... the works. When the user navigates to a new page, that's a whole bunch of new HTML, CSS, and scripts that have to be parsed. And so on.
Scoundreller|3 years ago
I remember having to disable smooth scrolling when I had a computer barely capable of playing mp3s.