Earlier quoted context omitted.
But it wins in every case where performance truly matters: multi-threaded calculations, archiving, encoding. You know, the things that actually do take up time. Do you really care if your webpage renders for half a second longer?
Yes, I do care. A lot. Actually if it's just 50ms I care. Slow main thread is a huge annoyance, and that's 99% of my computer use. On the other hand, I don't care if asynchronous tasks (encoding etc.) take 30 or 40 seconds or whatever; I can get a cup of coffee or check my email. Also, major parallel workloads are done on the GPU anyway.
You're also missing that even on chrome the js and layout engines run different threads. Same with audio and video rendering. Same with downloads. The average page is probably running things on 10-20 random threads. And the average user has multiple tabs open.
Multicore CPU is so common these days that any performance critical code that can be parallelized, is. This includes GZIP and HTTP which are used heavily by web browsers. The network stacks underneath those in the OS are also multi core capable.
Single thread performance is not all that important anymore. It's better to have 2x the number of fast cores than half the number of slightly faster cores in almost every situation these days.