Kitz Forum
Broadband Related => FTTC and FTTP Issues => Topic started by: tiffy on October 05, 2017, 10:29:24 AM
-
Anyone noticed a recent change in results from the BT Performance Tester ?
I have been away from home for 6 weeks so not run the tester for some time, I now find that I am getting consistantly very low DS speed figures which I don't believe are correct, ie., less than 20 Mbps. when my actual DS speed is close to 35 Mbps. as it always has been since migration to VDSL in June this year.
How do I know my DS speed is still 35 Mbps ?
TBB live data speed indicator which I always run on my desktop indicates close to 35 Mbps. for the full duration of the DS BT performance test.
Sam Knows white box monitor DS data speed indicates close to 35 Mbps. as per normal expectations.
Other speed testers such as TBB indicate close to 35 Mbps. DS data rate as per previous tests.
My DS synch. rate is unchanged as can be seen on MDWS (ID tiffy)
My line is very stable and rarely re-synch's as again can be observed on MDWS.
The only change I have noticed is when activating the BT speed test I am advised that Adobe Flash is required and activating this may slow down Firefox browser, I have to accept this to run the test.
I am running Win. 8.1 64b. on a desktop PC and Firefox is my default browser.
-
Anyone noticed a recent change in results from the BT Performance Tester ?
Do you mean the BT Wholesale Broadband Performance Tester (http://speedtest.btwholesale.com/)?
If yes, I've just tried it on my own circuit and it has returned the expected result.
-
Had problems running it here.
- It wouldn't return any results in Chrome
- It kept crashing in Firefox
- Yet I successfully ran it in Pale Moon and got the expected result.
-
I use Google Chrome yesterday. Once missing Flash had been installed it worked for me.
-
burakkucat:
Yes, that's the one to give it it's full name.
kitz:
The only difference apparent since the issue I have described started is that I get the "window" as per your snapshot but in by case it advises that Adobe Flash must be run and it may effect the performance of Firefox browser, I can't snapshot this now as I chose the option to "accept always" and it is no longer displayed.
The tester appears to run normally in Firefox but I believe the DS speed results to be incorrect as already explained.
I have not tried the tester in any other browser to date.
renluop:
I did not have to install "flash" as such with Firefox, just accept the warning.
-
Update:
Ran the BT WS Performance Tester on IE11, results obtained:
DS/US 35.52/1.67Mbps. (believed to be correct for my line, PN 40/2 package)
No warning given ref. Adobe Flash usage before test run.
Re-run tester using Firefox, latest revision, results obtained:
DS/US 17.77/1.57Mbps. (TBB desktop speed indicator showed approx. 35Mbps. DS during the test as per normal expectation)
Also noted recently that BT WS Tester "further diagnostics" process frequently failed to complete with Firefox, appears to proceed normally using IE..
Would appear that my issue is with Firefox browser and is associated with the appearance of the "Adobe Flash" message.
-
Re-run tester using Firefox, latest revision, results obtained:
DS/US 17.77/1.57Mbps. (TBB desktop speed indicator showed approx. 35Mbps. DS during the test as per normal expectation)
Also noted recently that BT WS Tester "further diagnostics" process frequently failed to complete with Firefox, appears to proceed normally using IE..
Would appear that my issue is with Firefox browser and is associated with the appearance of the "Adobe Flash" message.
A very vague memory tells me that I had problems on Firefox when I first had FTTC fitted back in 2011.
It turned out to be not firefox itself, but one of the extension I had added. I no longer recall the name of the extension (no longer use firefox much), but IIRC it was one that allowed you to trace the intimate behaviour of firefox when it was loading a page.
-
I just ran it on ff, and the ds result was sub 20mbps something is borked with it
-
Noted quite a few posts on the PN forum reporting the same issue, looks like the common factor in all is Firefox.