Yeah, that was pretty bad. No, the Android browser is not typically like that. Maybe when the device is already heavily loaded, which is uncommon (generally speaking, there's not that much running in the background) or while it's still loading a complex page, but that seemed to last longer than that. Having Flash turned on might explain it.

That said, there's an option to have Flash installed, but not run anything in the browser until you click on it, like Flashblock. Except that once you start Flash on that page, all Flash applets on that page start.