Well yeah, it's definitely the site; one of the replies to my original comment managed to identify the piece of JS that's doing it. Using a JS-blocker (or inserting a bit of JS into your developer tools to blank-out the offending function) would do the trick.