Leaderboard

Since you were good enough to set an auto test, it's very helpful in showing network data on and off peak as you say. Which gives the appearance of throttling to protect all users from a deficiency in total bandwidth. You might do well setting these tests over longer periods of time, or each day I should say, allowing the tests to run for as long as you can configure them. Do this for several days during the weekday, and then again on weekends. It will show a consistent drop off at specific times if throughput is set to be capped at a specific time during the day.

At first glance the latency 'dip' appears as network congestion during the test, some type of QOS, or if this is happening on all tests, could be power fluctuations within the first line node. Or any number of other issues actually. As far as speedtest, it's not showing the latency because it discards such findings. Why is anyone's best guess. But great for ISP's since it will not show issues such as you have pointed out in testmy.net results.

On the same topic it appears that the auto test stops if the connection is lost. That leads to big gaps in graphing if I'm not awake and aware to start a new test. Since my primary use at present is to document my provider's performance problems I'd rather have a test that keeps trying for the number of runs I had specified. (Someone once told me that nothing is too difficult for the person who doesn't have to do the work...)

That's on your smart TV, right? Typically when we see results like that on a computer we suggest TCP Optimizer. Optimizing the TCP and MTU settings will often bring the single thread score up to the multithread result level. You may not be able to change these settings on your TV, I would almost bet that you wouldn't be able to. Sometimes if the drive performance is lacking single thread tests here will suffer. Here's results from a Macbook. The first 9 results were taken with a failing mechanical HDD. The last 4 stable results were taken after the HDD was swapped for a SSD. In hindsight I should have done some multithread tests to show you that multithread is usually unaffected in this scenario. But I didn't know I'd be sharing the results at the time... I just wanted to quickly fix my friends laptop. I could tell just by how the first few tests felt while they ran that it was the hard drive holding it back, plus I had already diagnosed it with multithread test comparison a month prior. Did a swap for SSD, rebooted and instantly 90 Mbps ... over and over again. Everything ran better by the way... I just tested it through the Internet and TMN. ... Note: if I only had 15 Mbps Internet I wouldn't have been able to see the issue. It's only at extreme speed that you can start using TMN for purposes beyond what I originally intended it to be used for. It's not always the Internet connection and ISPs fault. Hardware can hold you back too. TestMy.net is not just a bandwidth test... it started as a bandwidth test but at higher speeds we've found it does much more. Those results (from a TV on your connection type) look good to me. That's a comfortable speed to surf at. It would be better if both types tested at 35+ but I wouldn't get too hung up on it either. That's not a bad performance. It may be held back by the speed of the TV's memory... why things like that only affect my classic test, I don't know.. they just do. But now, when you get your next tv... you'll know how to benchmark the difference.