Perhaps I am not using the REST Api correctly, but it appears that the speed variation that we had it coded to (in case the defaults changed) has been overwritten. It looks like all of our pages load MUCH faster than previous runs with this morning runs.

While we will likely revisit the params we're using down the road, the unexpected change in speeds will throw off our data. Which is why we used the hard coded values on the API rather than depend on defaults.

I'll look into this more tonight when I get a chance to see if something is not set right for our calls to your service.

FWIW I agree with the settings you are defaulting to, though I might put Chrome ahead of IE9 just because of the number of webkit related versions. Well, at least for our customers.