Why Is Twitter So Slow - Causes and Solutions
Slow loading is usually your connection, the app cache or a rate limit rather than X being down. How to work out which, on desktop and mobile.
Platform-wide degradations
Slow X is normally either the platform, your connection, your hardware assuming that enormous enough a record that individual screens have real work to do. Go through them in that order. A platform outage is not for you to solve. Check status first. You open a status site or launch five other apps. Stop if those hang the same. Since 2023, X has suffered from repeated degradations following overhauls of its infrastructure. One of those inbetween times is a complete waiting game. Refreshing the feed that has stopped working won´t do anything.
During such a site degradation, the web app, iOS app and Android app often fail differently. One client can display an empty home > timeline while another still gets replies. And that split places the issue on X's side. Avoid reinstalling the app during a known incident or resetting network settings. Those steps use up time and do not fix a backend that is overloaded. You have to wait a little, then check recovery itself by loading URL for one tweet in your private window. The incident ends if that single page renders.
Network path problems
Change to Wi-Fi or switch to mobile data and see if the slowness follows you. If the app survives while using Wi-Fi but snaps back on cellular, that means there's a problem with the Wi-Fi path. If they're both slow, use an entirely different network like a hotspot from another phone. If it is a DNS problem, you get a hung spinner but no error. This issue is often resolved by changing the device (or router) DNS to a public resolver. A VPN can hang X when the rest of the sites seem fine. Temporarily disable it to run a single remote test
In images that never finish loading; in videos that buffer indefinitely. Perform speed test on the same network. Throughput of several megabits is suitable for the time scale; latency above 200 milliseconds or packet loss higher than one percent are not. If the test looks bad, restart the router. Filtering, frequently throttling or blocking X media hosts on a work or school network. There is no client configuration that circumvent that. Use another network. The media will remain a slog until that filter switches.
Device and app state
Kill the X app and restart it. Swipe that out of the app switcher on iPhone. Android — Use Force stop from the system app info screen and run it freshly. If the timeline is still sluggish, restart the phone afterwards. Install the app via the store. Old builds keep trying to call old endpoints but moved, it seems like never ending loading. With only a few hundred megabytes of free storage, every one app on the phone will clog up with X. Remove unused apps and big videos, then relaunch X.
The app is also throttled in background refresh and battery saver modes. If you want notifications and a faster first paint on iOS, go into Settings, X, and allow Background App Refresh. Fetching will be delayed in Low Power Mode. Android: Remove X from all battery optimization list and allow unrestricted data if on wifi An ancient phone with a failing battery will throttle thermal on the media-heavy timeline. There is no setting that rectifies than hardware limitation As a temporary light stopgap, use the mobile site in a browser.
Cached media and data saver
Cached media is the usual offender on a phone that has had the app installed for a year. Settings, and privacy, then Accessibility, display and languages, then Data usage. That dump can be multiple gigabyte. Once it has finished, quit and relaunch the app, allowing for a timeline rebuild. Enable up Data saver from the same Data utilization section. That stops auto-play videos and downloads lower resolution images which are needed on slow connections and warm phones. Keep Data saver turned ON until the data connection gets better.
If after a cache clear, the app still feels heavy — uninstall it and reinstall. You have to to log in again You can lose bookmarks and drafts saved only on the device, so first copy all that you need. For Android, one can clear cache easily in the system app info screen — quicker than a full uninstall. The Apple approach goes a little deeper than that as there is no separate cache button on iOS outside of the in-app Data usage screen. Leave Data saver enabled for a day after reinstall and monitor the home timeline.
Browser extensions and tabs
Launch X in a private window with whatever extensions you use turned off. A loaded extension is the reason why if that timeline loada at full sped there. Then, in a normal window, switch them off one after the other until the stall returns. Now that the site desperately needs scripts to be stripped, ad blockers and privacy extensions sometimes break X's loading. It can mooch on certain GPUs too for hardware acceleration. This can be disabled in the browser settings and needs a reload. If one profile a slow, its cookies or service workers stale. Clear x.com site data and sign in.
Tab groups with pinned tabs that have remained open for days build up a large DOM and lots of media blobs on your system. Instead, make sure to close the X tab completely and open a separate one! Zoom above 100 percent requires additional layout work for the dense timeline. Reset zoom to default. X tabs can contend over the same session and block each other. Keep a single tab. If tab X has a lot of other heavy sites open then it will also be starved of memory by the busy site. Remove all unutilised tabs and click reload X one time The fair test is the first paint after cleanup.
Large account archives
Indeed, those profiles with tens of thousands of posts are just slower to load and scroll through. Because pages in your profile, media tab and likes actually have to load some real work, opening them can take more than a few seconds. And searching your own history across 10 years worth of posts does not happen in real-time. There is nothing wrong with the app — that delay. The price of a telephone book. Trimming old posts cuts down what those screens need to retrieve. Years old will disappear from your own profile, search and media grid.
TweetSweep arranges your posting history in a calendar format, which makes it easier to delete entire years of tweets without scrolling through them. Select a date range and look through the posts in that time period, then delete them all at once rather than hitting delete on each one. That's the real solution when it is your own archive that is slow, not the network or app. Force-close the app after a large delete, and reopen so that your client is forced to refetch the smaller profile. So, after few mins you can go to your profile and media tab.