That’s my thought as well. It sounds like lackluster support passing the blame on.
I just tried in Firefox on the same machine and it’s fast and smooth. It’s still unusable in Chrome.
I think this is a strong indication that the problem lies with 3DVista’s implementation on Chrome. Since Chrome has a ~65% market share, they should address this.