Thank you! As said, your best choice is to run a plugin profile and try to figure out what happens. I have just tried it on my own blog, which happens to have quite a lot of complex plugins — none, however, which were consuming so many resources as about-me.
I suspect — but cannot confirm! — that the trouble might be from opening a remote call to get all the data from About.me before returning that data properly formatted to WordPress. When doing that, there might be huge timeouts, which force the user to wait on the page — and the profilers will catch that delay.
This is just a wild guess, mind you. I might be utterly wrong :)
And maybe this discussion should be forked outside this thread for feature requests?