it's probably does to an older fetch arriving after the updated one.
http fetches are not done in order: some can take a while.
one second is way too little: the old ones can stack up, and twitter is going to turn you off after a few hours of war-hammering like your doing.
plus, i would be pissed if i realized your page sucks 500mb per day from my data plan; that's ridiculousness!
BROWSER STATS [% share]
(2013/12/12) IE7:0.3, IE8:7.5, IE11:4.3, IE9:4.6, IE10:7.8, FF:18, CH:43, SF:5.5, MOBILE:21.5
Last edited by rnd me; 01-17-2013 at 01:39 AM..