Could be something going on with the route or even the particular Macupdate server you're hitting. (Not sure if they're dispersing the load among multiple machines or not.) I assume you do not see this in Safari if you try Flushing the cache and stuff?