So if Moose's computer is accessing websites he's not actually visiting, then if it's just because he's visiting webpages that access those other sites then blocking them in some way is the best approach, but if we're going to assume Moose lives a clean lifestyle then isn't that unlikely?
Like I said, they're ads. Google-analytics is Google's advertising-tracking outfit; when you load a page being tracked by Google Analytics it sends a request to their servers.
It's not malware; it's the banner ads and "sponsored links" that appear on everybody's blog, news sites, basically everywhere. Are you not aware how all that works? Bloggers and website managers sign up with AdSense or a similar outfit to sell advertising space, and when you load that webpage, a line of code in the HTML ("ads go here") tells your browser to head over to AdSense and grab an ad (their choice, based on who links to your website.)
That's why he's waiting on requests to Google Analytics and the like - embedded ads in the webpages he's loading. But there's some kind of network routing issue, probably nowhere near his end, that means that packets from AdSense take a lot longer to receive than packets from the webpage he's visiting. That's not surprising - the ads are dynamically generated every time they're requested by browsers, based on information from your cookies, your IP, your location (derived from IP), and how you got to that website in the first place. That processing takes some overhead as I'm sure you're aware. And the network latency between Moose and Google Analytics is apparently much higher than the latency between Moose and the website itself.
Blocking them at his router means his browser spends a lot less time waiting for AdSense to get packets back to him - the router returns the error message immediately. The "downside" is that he doesn't see the ad, but who gives a shit? Win-win if you ask me.
I've never heard of regional Internet bottlenecks, hope I never get one.
One of the disadvantages to the internet moving from government networks (NSFnet, the university system backbones) to commercial networks (MCI, etc) is that the internet became much less redundant. It no longer "routs around damage" to the same extent.
It's likely that every residential ISP in your neighborhood leases their bandwidth from a single source, who itself leases bandwidth from a major commercial backbone. That's a considerably smaller amount of redundancy that means a lot more people can be affected by a loss of a single node.
There was a case several years ago where residential internet access was interrupted
for the entire state of Minnesota because a homeless man lit a fire under a highway overpass and burned through an internet trunk line. The internet no longer routs around damage.