Hi Andrew
Just testing that, and indeed it's changed now and reporting lower, however it's gone a bit too low. I've not got time to look at the code to see what it is doing, but currently my speed test shows as 64.98 with the factor at 1 (i.e. no change), I was expecting something around 69. If we take 64.98 * 1.06 it equals 68.88 which is what I would expect from that change. I'm guessing perhaps a bug in the test code is applying that correction factor twice and perhaps that is the bug, not the actual factor itself, therefore a factor of ~1.03 would correct that more or less. I'm guessing at the moment so I don't suggest changing it unless you want to, perhaps you would prefer to revert back to how it was?
All other speedtests are currently coming in around 68-69Mbps very consistently, the only exceptions are those based on the fdossena open source tester, I've tried Uno, yours, and even their own test page one at
http://speedtest.fdossena.com/, they all report higher where dividing by 1.06 matches other testers.
Edit: Had a quick look at the Javascript and can't see this being applied twice, however the help documentation has:
overheadCompensationFactor: compensation for HTTP and network overhead. Default value assumes typical MTUs used over the Internet. You might want to change this if you're using this in your internal network with different MTUs, or if you're using IPv6 instead of IPv4.
Default: 1.06 probably a decent estimate for all overhead. This was measured empirically by comparing the measured speed and the speed reported by my the network adapter.
1048576/925000: old default value. This is probably too high.
1.0513: HTTP+TCP+IPv6+ETH, over the Internet (empirically tested, not calculated)
1.0369: Alternative value for HTTP+TCP+IPv4+ETH, over the Internet (empirically tested, not calculated)
1.081: Yet another alternative value for over the Internet (empirically tested, not calculated)
1514 / 1460: TCP+IPv4+ETH, ignoring HTTP overhead
1514 / 1440: TCP+IPv6+ETH, ignoring HTTP overhead
1: ignore overheads. This measures the speed at which you actually download and upload files rather than the raw connection speed
So 1 seems to be the true download speed, all the others are trying to estimate the overheads, and it can be seen from the notes that most aren't calculated, but arrived at by some guess work and observations. Interesting 1.0369 is listed as an alternative, which is what I suggested above would seem to give rise to something in the ball park of other testers.
Seems like this isn't a precise science where this tester is concerned, I wonder what adjustments are made by other speed testers?
There is a newer version of this tester code which has various bug fixes as well.
Regards
Phil