1 UI thread !== only 1 thread

Firefox and chrome use a half-dozen or so threads parsing and compiling JS code so it loads quickly. Firefox's Quantum work adds a lot of threads for rendering as well. In addition, service workers, web workers, and Wasm all spawn additional processes which serve the same purpose if you aren't sharing memory directly.

That said, the Phoronix Selenium tests show AMD ahead by quite a bit. (source)[https://www.phoronix.com/scan.php?page=article&item=ryzen-37...]

So Servo is just snake-oil?

Firefox's quantum work comes from their servo work, so I'd say it's been valuable.

Firefox Kraken is faster on the 3700X, for example. It'll come down more to which browser you use than the processor.

> Web browsing is still single threaded.

Only in the narrow sense that processes are not threads. See `Window > Task Manager` in Chrome.