Jump to content

NotHereToPlayGames

Member
  • Posts

    6,745
  • Joined

  • Last visited

  • Days Won

    83
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by NotHereToPlayGames

  1. I can hit "infinity" if I keep my Proxomitron enabled. But I generally run tests like these wtihout Proxomitron and without NoScript or uMatrix.
  2. My hunch is that you've only been able to trick the RESULT. But the amount of TIME that the test takes should still tell you something for one browser versus another.
  3. Fair enough. Do find it odd that the same exact computer, same exact browser, scores 140 here at home but breaks 300 at work. At any rate, even the 140 is the HIGHEST that I've ever seen ANY browser score here at home.
  4. The tests I've used in the past are Speedometer 1.0, Speedometer 2.0, Basemark Web 3.0, Kraken 1.1, and SunSpider 1.0.2. I know they all correlate to each other as far as scores go. A browser that "wins" in one will also "win" in another. A browser that "loses" in one will also "lose" in another.
  5. I know there used to be (or still is?) something called a "Just In Time Debugger" that could be enabled/disabled.
  6. Sweet! Please let us know if you can track down the browser settings.
  7. My Win10 laptop scores 140 both on direct-connect and on wireless.
  8. I max the needle at 140 with the same exact laptop here at home. But it does break 300 at work. Perhaps the scale is different on different types of networks?
  9. I use Ungoogled Chromium v97 on my Win10 and it scores 300 plus. It's the only browser I've ever seen break 300! Newer Chrome/Chromium's score lower so I've stayed with v97. My spreadsheets reference Speedometer 2.0, I did not know there was a 2.1 until just this week.
  10. lol, was given to me for free when a neighbor installed WIN10 on it and then complained how slow it was. Works fine for XP, relatively speaking.
  11. I'm over 12 minutes in (separate computer) and the test is still running on NM28. Yikes!
  12. My oldest (without running to the garage and putting old parts together) is only 14 years old. eMachines T3656.
  13. 2.66 !!!??? Holy cow, Batman! It should be noted that the "Speedometer" test takes several things into account. I will get one result when running "fast" wi-fi, another result when connected directly to LAN.
  14. This needs corrected to include a missing QUOTE (") at the very end of the user-agent line. Should read -- Parameters=--user-data-dir="%Profile%" --disable-logging --no-default-browser-check --disable-component-update --disable-background-networking --allow-outdated-plugins --kiosk-printing --disable-print-preview --cipher-suite-blacklist=0xe013 --disable-webgl --js-flags=--noexpose_wasm --user-agent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.5304.88 Safari/537.36"
  15. Spoofing the useragent is old school. Some "modern" websites do not use your useragent but still know that you are using an "older" web browser. Etsy is using a "simple" user agent test - see next post for fix.
  16. How well does Serpent 52, Serpent 55, BNavigator, New Moon 27, and New Moon 28 compare on your computer?
  17. Chrome variants cannot set the backspace via about:config. I am not familar enough with Serpent 52 and offered the solution I use in 360Chrome. Good do know there's an about:config solution for Mozilla variants.
  18. Aside from THIS is how this "argument" started in the first place. I obviously "failed", but the ONLY thing I was TRYING to do is to demonstrate that DcBrowser uses more RAM than 360Chrome. Nobody else seems interested in "that" for some reason. We all know that Chrome variants use a lot of RAM, no new "news" there.
  19. I'm more interested in 360Chrome being compared to DcBrowser. Every comparison I've done has thrown DcBrowser right to the Recycle Bin shortly thereafter.
  20. I currently use Chrome v97 on my systems with 32GB RAM. I have a couple PCs still on XP but I now run Win10 by default on most of my PCs.
×
×
  • Create New...