In reply to a post by ajseeds:

Second link previously had a missing "s"

Corrected link works fine, as you say.

Ah, must of been corrected the time I checked it

Paul

Not the OP, but here are mine run from an iMac with Eset Cyber Security Pro running using Safari:

The http version really impacts the uploaf speed.

Https result:
https://www.thinkbroadband.com/speedtest/15982240044...

Http: result:
https://www.thinkbroadband.com/speedtest/15982239684...

Happy to run results on Firefox if required. Chrome always produces poorer results.

Sync. speeds: 1,008 kb/s upstream; 8,095kb/s downstream.

Rather odd that some results have upstream peaking above sync speed- presumably that is loading the buffer?

All goes to show that choice of browser can affect results significantly.

AV may be doing more checking on http data than SSL i.e. it will see the SSL and trust the certificate and do less checking possibly

Which speed test of ours has reported an upload speed above the sync speed?

If other testers are doing that I don't care, as not my job to fix their services for them.

This is the TBB result where peak speed exceeds Sync. speed:

https://www.thinkbroadband.com/speedtest/15982174938...

1.1Mb/s with a Sync. speed of 1.08Mb/s

I think the issue of buffering may be important. Perhaps a longer upload test is needed at these low bit rates to get a reliable result?

That was burst - so buffering is an issue and longer test would not fix that.