3 ms·

The same happens for me in Chrome. Twitter is the issue, not your browser.

• mistermann 10y ago
  Chrome tabs each have their own process though, so then wouldn't your problem be your PC?
  • cyphar 10y ago
    Sure. But if three instances of a website can bring a fairly new machine to its knees, then there's nothing any browser could reasonably do to fix Twitter's massive JS bloat.
    • mistermann 10y ago
      In my case, FF uses well less than 10% of CPU, yet the browser is extremely unresponsive. So no, it's not the machine, it is FF.