To be fair, I think the performance of that page has something to do with the embed API, and the face that it was trying to load multiple copies of wave.

The actual wave client performs pretty well now.