Chrome and thinkbroadband.com speed test

Bump...

I can recreate this.  I'll pass the thread over to our development team for comment.

Thanks ruckus.

Looking at the data generated by thinkbroadband.com's site, they've rolled their own protocol which unfortunately includes very short handshake components.  This is something which tripped up our identification of non-http content.  This has already been improved, and the next update should fix this issue with thinkbroadband.com's speed test tool.

Web filtering components will always have some impact on performance testing, though once we can identify content as non-http and bypass it this interference should be minimal.

Both Safari and Firefox run their flash browser plugins as a separate process, which means our Web Protection feature doesn't filter it.  The performance issues are unlikely to be related to our product; as Thinkbroadband acknowledge:

 > Users of Firefox and Safari in OS X may see slow speeds on the 'TBB' download figures. This is due to an issue with Flash in these browsers. We suggest Apple users try the Google Chrome browser as this is unaffected.

Ookla's speedtest.net site measures performance using the HTTP protocol, so is not affected by this HTTP identification issues, but with Chrome the results wil include time taken to scan the content.  Are you able to use their speed testing services instead?

I already use Ookla and/or thinkbroadband.com for speed tests, the choice depending on where I am and what I want the speed tests for.

The good news is that you know the cause of the issue and, hopefully, have a fix for it in the next update. Any idea of the timeframe?

Thanks for your input.