X's Rebuilt Web App Cuts Profile Load Time from 22 Seconds to 2.7 on Slow Connections

X is rolling out an updated version of its web app one country at a time, starting with signed-in users, according to The Verge.

X principal engineer Yagiz Nizipli described the rebuilt application in a company blog post. The post frames the work as a rebuild of the web client rather than an incremental redesign, meaning the front end was largely written anew instead of being adjusted in place.

The most concrete performance figure concerns cold profile loads on a slow connection. A cold load means the browser has nothing cached from earlier visits, so every piece of the page must be fetched from the server. According to The Verge, opening a profile on the old X web app took more than 22 seconds before the first post appeared. On the new app, the same action took 2.7 seconds.

Architecturally, the updated app replaces three servers that had handled traffic from people, search crawlers and link previews with a single server. Search crawlers are the automated bots that read pages so search engines can index them. Link previews are the summary cards generated when a URL is shared. The consolidation is described in the engineering post.

The new app is already live for logged-out visitors to X.com and for pages that search engines crawl. The Verge reports that signed-in users are receiving it on a country-by-country basis.

Security researcher Jane Manchun Wong said she had access to the updated app. She described it as snappy, fast to load, and polished in many of its parts.

In my view, the server consolidation is the detail that will matter most to engineers reading this. Merging three workloads with different latency expectations, caching behavior and traffic patterns onto one service simplifies operations, but it also concentrates load and failure modes in one place. How that service holds up at peak traffic, and how it handles crawler and link-preview requests alongside interactive sessions, is something that will only become clear with time in production.

The broader context here is the user base. A profile that takes 22 seconds to show its first post on a slow connection is effectively unusable for many people, while a 2.7-second response falls within the range where a reader can start engaging. Faster first render on constrained networks widens the set of people for whom the service works well, which appears to be the outcome the rebuild was designed to produce. Whether the gains hold once the rollout reaches every market, and under the full range of real-world conditions, is a question the coming months will answer.