Testing with a a Dell Win7 Celeron netbook doing 120 sprites and checking Task manager. Note that the JavaScript code is unoptimized (e.g. we repeat the sin/cos calculations every cycle, when we could store them), but I'm guessing/hoping that the CSS transitions are the main CPU hog. The 'flipping' code takes between 2-6 milliseconds (*depending on browser), once per second - that's less than a frame at 60hz, so it shouldn't have any noticeable impact
Testing with no background image:
Testing with a scaled JPEG background