Pretty horrible article.
WiFi Browsing test: The CPU is asleep most of the time. Network access is incredibly slow by CPU standards. Any impact on battery life from the CPU during WiFi browsing would be negligible, as is shown here.
WebGL: GPU-based test. The GPU is an independent part, sourced from a third party. Perhaps customized somewhat knowing Apple, but the claim was that the samsung CPU was using more energy, not the GPU. This test is mostly irrelevant.
Geekbench: The only true CPU-based test isn't valid, because it isn't based on real-world usage? Interesting. Well, then I guess this whole article was a waste of time, since this is the only CPU-based test we have to go on.
GFXBench: Another GPU test. Not relevant, because the CPU is the item in question here.
What a poorly thought-out article. There's basically no data here. Geekbench is the only one that's of any real value, but it truly isn't indicative of real-world usage. Regardless, it still shows a clear difference in battery life between the two CPUs, and at the very least shows conclusive proof of this issue. There is a difference in battery life, and if whatever your doing is taxing the CPU, you WILL notice it. That's what this has proven. Real world usage is subjective. Not everyone spends their time surfing the net.
I trust more Arstechnica than you since you don't seem to know what you're talking about.
The GPU is on the same die as the CPU (NOT a separate part), you know the one SAMSUNG DID.
So, if there is an issue with the process it will turn up there too. Got that.
When building the pages, the CPU works, with modern complex pages, it can work pretty substantially.
Most of those pages have 50 links in them all being transferred/built asynchronously too.
There's a reason most smart phone stutter when loading pages (but not IOS), because it is not a trivial test.
Everything else you said is just blah blah blah.