Well I have did more testing, and digging on this, the last couple days. I noticed a couple things, and I'm gonna share my findings below.
1. Oddly at times I noticed my result's were not the best while using google chrome. I used firefox, and things seemed more steady. I have been able to get some good result's with chrome as well though. So I wouldn't say not use it. I tried using windows 10 built in IE browser, however I tried a couple test's, all failed when trying to do the upload side of the test. So I say stay away from IE for testing.
2. When running this test, I strongly suggest cutting all bandwidth usage on the device you're testing on. So if you're on your pc, which you shouldn't be testing over a wifi device anyways. So testing while on a PC/Laptop. Close any apps/browser tabs that are using active bandwidth till testing is over. Also I highly recommend when testing on dslreports.com, try to only have it open within the browser you're using. I feel that will minimize any other tabs within the browser somehow causing the test an issue.
3. Do yourselves a favor, and create an account on dslreports.com, will only take a short time to do so. Reason being, you can configure your "Preferences" settings for the speedtest, once saved, they will stay linked to your account. I feel configuring the preference settings is VERY important with this speedtest. I will explain more below.
4. Reason to setup preference settings. First you can select the servers you want to use, for the test. At the top you have a option to let it pick some servers for you based off of either Latency, or Bandwidth. I suggest using the "Latency" option. After that's done running, it will have the servers it picked with a check on them. After that, you can look at the one's it picked, and unselect some of them if you want. I did a couple for myself, pick the ones closest to me. After this, make sure to hit the save button at the bottom.
However I'm not done with the preference settings yet... After getting a small number of servers picked based off latency by it's own testing, and also checking over them yourself. I wouldn't have no more then 8-10 servers selected.
Now scroll down a little, and you will see "No. download streams" with a box beside it. You can pick between 1-32. I honestly think for most of us "4" will be enough. That will be the amount of servers it will use while testing. Do the same for the upload side, which is right below it.
For awhile I was using 16+ for each test I done, and I now don't recommend using that high of a number of servers for each test. Reason being, your overall result's will depend on all the servers used during that test. For me, I'm on the east coast of the US, and when I'm doing one of these test using 16+ servers. I'm likely using several servers on the west coast of the US. With a mixature of servers all over, there's so many things that can affect your routing from one minute to the next.
So my final opinion on this, keep the number of servers used for the test low, and use servers close to you. Because this to me will give you more accurate result's, when it comes to the bufferbloat part of this test. Finally make sure after any preference setting changes, you make sure to click the "save" button at the bottom.
5. After doing the stuff above, I have been seeing more steady result's with the dslreports.com speedtest, in terms of bufferbloat, and my overall results. I don't feel the current default settings used for their speedtest, is optimized very well for testing, and getting the most accurate results. Ultimately I think by default they're running the test using to many servers, which can be from far away. With that, comes a lot of possible routing issue's. Some of them you have no control over, and isn't an issue with your connection. However whatever each server is reporting back, ultimately is included at the end of the test, and will factor into your final result.