I'm not sure whether the problem is in the firefox runtime or in the way google optimizes for Chrome (and maybe even "accidentally" slows things down on firefox)