Re:Why loading third party scripts async is not good enough
by wladimir on Thursday November 24, 2011 @04:54AM
(#3273834)
Agreed. -214%, the way I interpret it intuitively, would mean the new value flips sign. -XXX% where XXX is bigger than 100 therefore looks strange.
Re:Why loading third party scripts async is not good enough
by dredmorbius on Wednesday November 23, 2011 @03:27PM
(#3271584)
The pedant uses the delta over the mean of the old/new values.
So: 100 * (1.14 )/((1.14 + 3.63)/2) or -104%
Re:Why loading third party scripts async is not good enough
by Rexxar on Wednesday November 23, 2011 @05:44PM
(#3272114)
May be I'm missing something, but this way of computing a percentage seems completely meaningless to me.
Re:Why loading third party scripts async is not good enough
by dredmorbius on Wednesday November 23, 2011 @07:17PM
(#3272416)
It's unbiased toward either the beginning or ending value.
If you want to overstate a change, you'll use the smaller value as the denominator. If you want to understate a change, you'll use the larger. If you use the mean of the two, you're giving a value that's not biased by either of the two extremes.
There are arguments for using other methods. As usual, Wikipedia has a good discussion of alternatives: http://en.wikipedia.org/wiki/Relative_change_and_difference
Re:Why loading third party scripts async is not good enough
by recursive on Wednesday November 23, 2011 @11:47PM
(#3273111)
When talking about a starting value and a new value, I find the percentage change formula on the page you referenced to be the most logical. When considering a change, your frame of reference is usually the original value.
http://en.wikipedia.org/wiki/Relative_change_and_difference#...
This is a pet peeve of mine. Percentage changes should be measured using the original value as the denominator, not the new value.