Icons on web should be optimised
The icons for "add to favorites", "reply to this tweet" and "updates protected" on web are far too big for their content: 13, 46 and 13 kilobytes, respectively. They make pages load very slowly, and even more so for dial-up users.
For their dimensions, they should be under 1 kilobyte.
Optimising the images would reduce the bandwidth usage on Twitter a lot as well.
Another suggestion would be to put all icons on the same assets* server (maybe static.twitter.com?) to take advantage of HTTP 1.1 keep-alive.
For their dimensions, they should be under 1 kilobyte.
Optimising the images would reduce the bandwidth usage on Twitter a lot as well.
Another suggestion would be to put all icons on the same assets* server (maybe static.twitter.com?) to take advantage of HTTP 1.1 keep-alive.
6
people like this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
The best point from everyone
-
Based on some rough research, I'm going to ballpark that twitter is having to load those icons about 500 million times a day.
At 87kb combined total for the icons, that equates to 43,500,000,000,000 bytes per day. (43,500Gb, 43.5Tb).
If the images were optimized, the combined total would be 1,144 bytes. At 500m/day, the total bandwidth usage would be 572,000,000,000 bytes/day. (572Gb).
The total daily savings would be 42,928gb/day.
In a 30 day month, that would equate to 1,287,840Gb of saved bandwidth (1,287Tb).
Based on bandwidth costs of $0.10/Gb, that would save twitter an astounding $128,784 PER MONTH on bandwidth.
These figures are estimates at best, just to show why optimization is needed. Even if the pageviews are much lower and the cost of bandwidth is cheaper, there is still money to be saved!
I’m astounded
3 people think
this is one of the best points
-
Inappropriate?YES YES YES! Please change this. Also, the images are loaded with the epoch time as a parameter at the end, forcing the browser to reload the image EVERY TIME! Is this some kind've crazy load tracking? This must be fixed!
I’m thankful
-
Inappropriate?Addendum: The title "twitter" image (at the top-left on all Twitter pages on web) is also on an assets* server, with some ?1203138248 parameter as spling describes. That's not as bad, though I'd also like to see it on static.twitter.com.
The "favorited tweet" icon, if I may call it like that, is *also* upwards of 10 kilobytes. -
Inappropriate?Based on some rough research, I'm going to ballpark that twitter is having to load those icons about 500 million times a day.
At 87kb combined total for the icons, that equates to 43,500,000,000,000 bytes per day. (43,500Gb, 43.5Tb).
If the images were optimized, the combined total would be 1,144 bytes. At 500m/day, the total bandwidth usage would be 572,000,000,000 bytes/day. (572Gb).
The total daily savings would be 42,928gb/day.
In a 30 day month, that would equate to 1,287,840Gb of saved bandwidth (1,287Tb).
Based on bandwidth costs of $0.10/Gb, that would save twitter an astounding $128,784 PER MONTH on bandwidth.
These figures are estimates at best, just to show why optimization is needed. Even if the pageviews are much lower and the cost of bandwidth is cheaper, there is still money to be saved!
I’m astounded
3 people think
this is one of the best points
-
Inappropriate?Thanks for the heads-up. Taking care of it...
Loading Profile...








