Happy to help.
I suspect the Page.Wait() method falls foul of Chrome always reporting it's state as "complete". It's an annoying bug in the browser. That one little bug makes a simple task like waiting for a page to load very awkward.
Mind you, with all the sub-page level stuff going on in sites these days, which are detached from the page load status, it's hardly surprising.
I also do performance testing and we now have an in-house solution for timing sub-page stuff like Ajax events.
As browsers and sites get more complex, I guess it gets harder and harder for automated solutions to keep up ....
