MyBB Internal: One or more warnings occured. Please contact your administrator for assistance.
WebPagetest Forums - Speed Index Distribution

WebPagetest Forums

Full Version: Speed Index Distribution
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
In https://sites.google.com/a/webpagetest.o...peed-index (https://8d4a14bf-a-42404934-s-sites.goog...irects=0), there is speed index distribution figure.

I get the csv data for pages from httparchive. But I find the figure I plotted out is somewhat quite different to it for May 15,2013, [Image: cdf2013.png]

But in 2014,2015, the data is also different to it. [Image: cdf2015_all.png]The value varies significantly
(in 2013, the max value is 1800, but in 2015, max value becomes 80000).

Can you explain to me anything I did wrong?
1800 sounds suspiciously (and impossibly) low for a max. The 2013 data can't possibly be right if that is what you are seeing. It might be worthwhile to spot-check a few of the individual tests to see if it was a reporting issue or a measurement problem.
Thanks for your reply, I'm a bit confused about it as I used same date data from your document figure.

One more thing is what's the reasonable range for maximum of speed index, as 2014 and 2015 data are around 80,000, which is 4 times larger than the figure in the document

(06-10-2015 11:43 PM)pmeenan Wrote: [ -> ]1800 sounds suspiciously (and impossibly) low for a max. The 2013 data can't possibly be right if that is what you are seeing. It might be worthwhile to spot-check a few of the individual tests to see if it was a reporting issue or a measurement problem.
I don't know that I'd ever use an absolute maximum for anything interesting. A single outlier could easily skew things. The SpeedIndex is effectively reported in milliseconds and is the average point in time when the viewport pixels are displayed.

80,000 Would imply an 80 second max in the data set which is plausible if some site was sufficiently slow (or just timing out/failing to respond.

1.8 seconds (the 2013) number is WAY too fast and I'd be surprised if the average was even close to that.
Reference URL's