4 ms·
This website fully pegs one CPU core on my laptop (Firefox 57.0.4 on Ubuntu 17.10, with uBlock and Ghostery enabled). Apparently these lessons haven't reached t
by photon-torpedo 9y ago
This website fully pegs one CPU core on my laptop (Firefox 57.0.4 on Ubuntu 17.10, with uBlock and Ghostery enabled). Apparently these lessons haven't reached their web design team.
Edit: investigating closer, this even happens with JS disabled, and also in Chrome (with less load though).
- shakna 9y agoI'm not seeing anything like that, but you got my interest. The page is only using 14mb of memory, which is a bit higher than some pages, but it's about 4mb of JS source, and another 4mb of objects held in memory. It isn't desirable, but shouldn't be causing any issues. And though the page does load fairly quickly for me, a glance over what it does during that load makes me suspect I know your issue: Styles were recalculated more than 75 times, with the repaint happening more than 35 times. There's also a huge peak in the middle of the JS being executed. The culprit [0] has a tightly packed for-each loop. Three nested for-each, with each one contained a lambda, which contains two or three more lambdas. It's not performant code. That particular script is also 500kb of more of the same kind of code. (Might also point out that the form-handler on that page is an even bigger script.) So: I'd think it's the repaint from too many styles coming in overriding each other, but it might just be a reliance on a large library, which doesn't seem to be well thought out. [0] https://www.hpe.com/etc/clientlibs/hpeweb/js/hpe.dll.libs.js https://www.hpe.com/etc/clientlibs/hpeweb/js/hpe.dll.libs.js
- walshemj 9y agoDoesnt seem to do that on my 5 year old plus lap top with a i5-4200U I get 5-9% cpu usage with just this site open on edge.