I live in Rwanda and like a sizeable portion of Twitter's userbase, have very slow internet. When Twitter switched to their new design it got a lot harder to open their site... I kept using the old version until they removed it. I don't understand why - it's not pulling down a lot of data, it's not even making that many requests (~50), but this site and other AJAX rich sites just don't seem to work as well as the old…
A single tweet page is 2.0 MB
21–30 of 115 posts
Re: A single tweet page is 2.0 MB
#22Re: A single tweet page is 2.0 MB
#23Earlier quoted context omitted.
A more accurate title might be "The Twitter web client is 2.0 MB."
The problem is that Twitter broke links to tweet pages by using the #! URL structure. Now you can't load a tweet page without loading the entire app. That's bad.
Re: A single tweet page is 2.0 MB
#24Re: A single tweet page is 2.0 MB
#25Earlier quoted context omitted.
Exactly - just set your phone to EDGE and pull up a tweet page in your mobile browser and you'll see how long it takes. And not only for the 1st page load but for all others too. I can pull up a Facebook page (while being logged in) and have that served to me in a fraction of the time it takes for Twitter. Compare that to the feature-set and your opinion will change quickly. Just try it, no stats & graphs needed, you…
Honestly, Facebook's load time is quite phenomenal. It is one of the most feature-laden and complex consumer web applications out there and they still manage to set the bar with regards to speed and multi-platform usability.
Scrolling on TechCrunch with your mouse over the post area is a hilariously pitiful experience.
Re: A single tweet page is 2.0 MB
#26His rant doesn't seem too informed: "aggressive anti-performance and apparent contempt for the web by Twitter’s designers" According to his charts most of Twitter's page is JS/CSS and presumably set to heavily cache. Very little is data. Once you've done the first page load Twitter's pages will load quite fast and efficiently. While quite a lot of JS, this is good design, not bad.
This means that to get the requested information on first load, the user has to wait for a 2MB download, followed by another roundtrip Ajax request to twitters tweet retrieval API. This results in the perception of a slow page load, even though the tweet itself comes down the pipe in only 100ms.
In my view, Twitter is an excellent case study in some of the pitfalls of thick-client application design. Mainly that ignoring the first-time-use case will result in widespread perception among users that your app is slow, even when every page view after the first is lightning fast.
Re: A single tweet page is 2.0 MB
#27His rant doesn't seem too informed: "aggressive anti-performance and apparent contempt for the web by Twitter’s designers" According to his charts most of Twitter's page is JS/CSS and presumably set to heavily cache. Very little is data. Once you've done the first page load Twitter's pages will load quite fast and efficiently. While quite a lot of JS, this is good design, not bad.
Re: A single tweet page is 2.0 MB
#28I live in Rwanda and like a sizeable portion of Twitter's userbase, have very slow internet. When Twitter switched to their new design it got a lot harder to open their site... I kept using the old version until they removed it. I don't understand why - it's not pulling down a lot of data, it's not even making that many requests (~50), but this site and other AJAX rich sites just don't seem to work as well as the old…
And it is funny - AJAX-related technologies were promoted exactly to make sites more lightweight and more responsive..
Re: A single tweet page is 2.0 MB
#29Earlier quoted context omitted.
Wirth’s Law: Software is getting slower more rapidly than hardware becomes faster.
Web data usage != slow software
Re: A single tweet page is 2.0 MB
#30I live in Rwanda and like a sizeable portion of Twitter's userbase, have very slow internet. When Twitter switched to their new design it got a lot harder to open their site... I kept using the old version until they removed it. I don't understand why - it's not pulling down a lot of data, it's not even making that many requests (~50), but this site and other AJAX rich sites just don't seem to work as well as the old…