Edit: Tried it in Chrome with the network tab open. 267 requests, 2.43 mb transfered, loaded in 23 seconds. Something like 40 of those are javascript files. Then 8 font files.
For a news story! What madman wrote this?
Completely off-topic and irrelevant but say what? 2GB coupled with the beast that is i7 makes the nerd in me cry a little.
The page works really well in Links, though - loads far more quickly than in the other browsers I tried, no scrolling lag or unusual CPU use.
Not meaning to be offensive at all, maybe it is because of my location (Japan)?
Pingdom just measures /response time/, not browser-side parse/render time.
That's insane, users don't like to wait.
It uses ipv6; if your host is ipv6 enabled, there are probably tunnels involved and it'll be slower.
It tries to load dozens of json files from api.sharedcount.com. Try turning on pipelining if it's not already (still off by default in FF), and set max pipeline requests to something a lot more than the default of 4.