Revisiting browser and connectivity defaults

[pmeenan]

(03-17-2013 06:24 AM)mle_ii Wrote:  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.

This TERRIBLE page here:
http://www.webpagetest.org/result/130315_8W_M0R/
Normally takes around 13 seconds to completely load the page with 2.* mb of data.

With this morning's run it was less than 4 seconds.
http://www.webpagetest.org/result/130316_Y0_FAV/

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.

Thank you,
Mike

Looks like your query parameters are fine. I'm checking to see if I had a tester that didn't traffic shape correctly (the latency numbers look like there was no traffic shaping whatsoever). I re-ran the test it it came out as expected: http://www.webpagetest.org/result/130316_M0_KW2/ so I'm hoping it's just a specific tester with an issue.