> I'm not joking, but the real problem here is all the hot steaming dogshite that they choose to load, not really the number of requests, IMO. Neither making r

> I'm not joking, but the real problem here is all the hot steaming dogshite that they choose to load, not really the number of requests, IMO. Neither making requests not transferring data around are CPU-bound activities. > Many of those requests are also running GPU code to fingerprint clients. Canvas and WebGL. To "prevent clearing cookies to bypass paywall" fraud and ban scrapers. Even taking these statements at face value, considering that javascript is single-threaded by default it still sounds like a perceptual performance problem (not real performance problem) resulting from a poor software architecture. Expensive tasks are expected to be offloaded out of the main thread to avoid getting it blocked.