I'm trying to speed up my Twitter application, and one of the
recommendations I ran across was to increase the download
parallelization of the numerous Twitter profile images on my webpage.
Just out of curiosity, I tried:
and noticed they all resolve. Perhaps Twitter is using this same
Can we rely on spreading our profile image requests from a1.twimg.com
to a5.twimg.com for our applications?