Note: I'm not a dev for SPE, but I've dealt with Drupal (the framework they use on the back-end) quite a bit.
1) Why am I downloading a 200K .png of "Jared Dipane" that doesn't even show on the home page?
2) Why isn't that picture reduced in size, both dimensions and bytes?
That image is used on Jared's "Meet the team" tab in the superfooter. As for why it's not been resized: good question. Probably an oversight.
3) Is there no way for the 2755 line, 10651 word, 134738 character js_a1de670e01c8b6b453184a8f1c504662.js javascript file to be reduced in size and resource demands? How about the 195K www-embed_core_module-vflXhboHY.js or the 135K www-embed-vflIi8lfi.css? Bloody hell, seriously? Just the various .js files are 625K.
Drupal's extendable through the use of modules, and each one has it's own Javascript and CSS. Luckily, the framework allows you to compress all their individual files into one aggregate file; this reduces the number of small GETs that need to be done, but results in one massive file to pull. The idea is, once the user's loaded the page once, this is cached and doesn't need to be pulled again.
4) Can't the image in the article "Sony Tablet S slated for Sept. 16 US launch, priced at $499.99" be reduced in size, both dimensions and bytes? Or at least in bytes? Just making it a jpeg reduces it to a little over half its current size. As a 70% jpeg, it's 100% readable and is 16K. This is just one example. so don't fixate on it-- most other images could very easily be optimized.
This goes back to points 1 and 2, which I am in agreement with. Drupal does have several modules available that allow for image compression on upload; I'm surprised SPE doesn't take advantage of these. Granted, it could be because some of them are a real pain to integrate with some WYSIWYG editors, and don't catch all image files uploaded.
5) Just the html for the home page is almost a quarter of a megabyte.
This goes back to the earlier point of Drupal being a framework. It's massive, complex, and a little on the heavy side, but it's extremely flexible and powerful. I'm not really sure if they can get rid of it without losing some functionality.
6) There are too many calls to external sites. I've waited for loads from:
youtube.com
cdn.androidcentral.com
cdn.smartphoneexperts.com
i2.ytimg.com
i4.ytimg.com
a2.twimg.com
api.twitter.com
platform.facebook.com
By removing these calls, they'd remove Facebook and Twitter buttons, images stored on CDNs (including two of their own), and Youtube videos. Not exactly something that you can just throw out; it's a reality of the modern web.
7) Is it really necessary to have direct links for 20 different phones on the sidebar?
Consequence of a fast-moving Android ecosystem.

I'm sure they could cut this down, but I imagine the links help get people where they need to go.
8) Must everything that's on the home page really be there? You can easily get rid of "Meet the team" (no offence, but *no one* cares), the pictures of people following AC on Facebook (the same number of people care about this as do "the team"), the "where did it all go" image, and either the "join our community" or the "the forums and you" bits. Seriously-- its Too. Much. Crap.
I'll agree that the superfooter needs to be trimmed; you're right, a lot of it is unnecessary to be loaded on every page load. Meet the team should be reduced to a text link on the sidebar and put on another page; a tag cloud moved to the bottom of a page is pretty useless; and there are plenty of redundant links in the section that no one sees that are already available at the top of the page. The superfooter should be reduced to just a 'footer'.
Even when I disable everything except images, CSS and HTML, it's still horrendous. They threw together the largest, most jam-packed page they possibly could, threw in a few images that aren't even used, said "eh, our users have broadband", placed pinkies to the corners of their mouths and cackled into the night sky. I know... for every element on that page, someone, somewhere in the AC or SPE management decided that traffic would be increased by cross-posting. For any element I mention, someone can respond, "but it drives traffic (and ad revenue) to XYZ!" I'm sure there's a great reason for every last element. It's too much.
As far as I can tell, everything that is downloaded by the site is used; some of it's just not readily visible at first glance.
Honestly, I don't think the overall site is that bad; it almost seems like the site's static content isn't being cached, though. I refreshed the site several times while looking at Chrome's Network monitor, and hardly anything is being pulled from cache. I would expect things like the staff pictures, pictures of the phones, etc. to be static, so it's odd that the site's making the browser request for that data over and over again.