Once I've started typing the lag from keypress to display drops to around 0.2 seconds, which is tolerable, but I don't prefer it.
Each time I alt-tab back to Chrome, it would take almost 5 seconds to give me a cursor so I know where I'm typing again. SUMMARY: I did a few of these tests while typing this here response, and the most painful part with Chrome was getting my cursor back so I could enter the results. Wikipedia page for United States:Firefox: 3.6 seconds to load ( Firefox doesn't have a "spinning" indicator )Chrome: 11 seconds to load, 24.8 seconds to stop "spinning"Edge: 6.8 seconds to load, 19.9 seconds to stop "spinning"
Random eBay listing:Chrome: loads in 0:27, finishes "spinning" by 0:40Edge: loads in 0:15, finishes "spinning" by 0:42Firefox: loads in 0:15 ( Firefox doesn't have a "spinning" indicator ) "realworld" time to launch browser, go to reddit, pull up my profile, click on this post, find your response and start typing this reply:Firefox: 0:37 (first try) - 0:28 (second try)Edge: 0:36 (first try) - 0:25 (second try)Chrome - 0:54 (third try)
CHROME FOR WINDOWS INSTALL
TLDR summary: Chrome loses ( I have the 32 bit install ) because of a 0.5 to 3.0 second delay between typing and seeing what you typed show up on the screen, but I am using it to write this response so it does work. Alright, more benchmarks! I just spent the last 2 hours of my 4th of July testing this on my Book2 for, let's be honest, my own curiosity.
0 kommentar(er)
