Everything else was either single threaded (all the browser benchmarks), in which case dual vs. quad is irrelevant, or they were GPU bottlenecked in which case you aren't talking 1.4GHz dual core, and on the GPU front Apple spends a huge amount of transistors on that. They throw oodles of power at the GPU.
Also thanks to power management the vast, vast majority of those "2+GHz Quad-cores" were not running at 2+GHz, they were running at closer to 1.4-1.6 GHz. Apple is really good about settings its max frequency to something sustainable, whereas everyone else advertises burst frequencies.
There is going to be painting and such while the benchmark runs, which will use a second thread, but that's about it. And that's going to be relatively light compared to actual usage where you're scrolling around and such.
The majority of the other threads of a browser are I/O bound (networking, disk, etc...) and won't be using much of the CPU.
Just because Qualcomm's design achieves high clock speeds doesn't mean there's a rat-race in the Android world. Since Qualcomm dominates, there is no race at all. Second, Qualcomm's competitors are much more moderately clocked. Samsung's, Intel's and Nvidia's current high end chips don't even touch 2 GHz yet.
For a rat race you need rats and a race. But there's only one rat and no race.
Critically even though they may not always have the best CPU cores or best GPUs, they do have the best radios. And integrating that into the SoC is just better from a power perspective, making Snapdragon overall the best SoC package for a phone.
Isn't that just... competitive?
In day to day life your performance is going to be in between these two extremes.
They show how a Moto E is more responsive than a Galaxy S5. Full stack system performance, when doable, gives you this kind of leverage.
Mind you I'm not a game player or anything, this is just the normal stuff of having a podcast app, spotify, HN and a few others daily used apps. Great phone, but it can't compare with a flagship. (I carried a Nexus 5 before)
Apple went "retina" to end the pixel-count competition: if you can't see the pixels, you don't care how many there are. Apple refused to state RAM size for mobile devices from the beginning: user doesn't have an option, and rarely (if ever) notices the limit, so the actual memory size doesn't matter. Processor count & speed is irrelevant if it's used efficiently enough to practically outrun the competition.
Sure, Apple does provide some specs. People are too used to seeing such numbers, despite few needing to see them IF the implementation is done right. People want options, so some specs are flexible (at a price). But remember that behind the scenes at retail, the devices options are labeled little more than "Good, Better, Best": most users don't want better numbers, they want superior performance with whatever it's got. Those gloating about size are likely less able to use it.
There's an old saw about the railroads getting killed by the tractor trailer in the 20th century because they thought they were in the railroad business, when in fact they were in the transportation business. This time, Apple knows exactly what business it's in, while the competition seems to have no idea (compare the highly-curated experience of shopping/buying/shipping/using an Apple product to the Android or Lenovo analogue).