You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2021. It is now read-only.
Hope this is worth looking into;
I experience pretty intense lag on both my desktop (powerful gaming pc) and my laptop (macbook air) after having the site open for a couple of minutes (with & without this extension installed) it slowly becomes unusable due to the sheer amount of lag between actions, specifically scrolling, liking tweets, videos lagging, etc. Taking a look into Chrome's Task Manager i've found, whilst having multiple tabs open, Twitter has both the highest CPU usage and most memory usage of all of my tabs open.
I'd greatly appreciate if this could be looked into, as it would certainly make the site alot more usable to people who experience the same issue as I. Thanks a bunch!
The text was updated successfully, but these errors were encountered:
For anyone wanting to look into this, try using the "Performance" tab in Dev Tools.
sindresorhus
changed the title
Investigate & Eliminate Lag with Default Twitter Site
Investigate and eliminate lag with default Twitter site
Dec 8, 2017
I haven't looked deeply enough to see why these are slow, but I thought I'd at least log my findings here. These were the top two function calls in terms of total execution time.
Hope this is worth looking into;
I experience pretty intense lag on both my desktop (powerful gaming pc) and my laptop (macbook air) after having the site open for a couple of minutes (with & without this extension installed) it slowly becomes unusable due to the sheer amount of lag between actions, specifically scrolling, liking tweets, videos lagging, etc. Taking a look into Chrome's Task Manager i've found, whilst having multiple tabs open, Twitter has both the highest CPU usage and most memory usage of all of my tabs open.
I'd greatly appreciate if this could be looked into, as it would certainly make the site alot more usable to people who experience the same issue as I. Thanks a bunch!
The text was updated successfully, but these errors were encountered: