@JimLad and Over Kill
Yes I am sure it will be front and centre for Google to fix. It appears to be a huge priority at Google.
In the past few days, Google has hosted the Chrome Developer Conference and according to this excellent blog post by Michael Bleigh in Divshot, performance and capability of software from Google is a really big deal for them.
First I quote from the blog on mobile web performance:
"The magic number is 60 (or 16). Google is doing everything it can to get mobile web to 60fps, which gives you about 16ms per frame to do everything you need to do. It's hard to even enumerate all the different ways they're working on this. From speeding up paint to putting more workload into the GPU to providing flame charts (so cool!) in DevTools so you can figure out what causes that jank."
He defines capability "pretty loosely as "having the ability to easily build native-like experiences on mobile web." That includes things you'd expect (like push notifications) but also things you might not (like Polymer)." And web apps are prime, front and centre on Android L as "each tab gets its own place in the new web switcher."
And check out Service Worker which is a real serious effort by Google that Michael says "gives you the power to program the network layer of the browser. It's a comprehensive low-level technology that can completely solve the offline problem. Offline is a big deal, it's one of the most defining features of native apps vs. web in today's climate. As Alex Russell put it in his talk: "It isn't an app if it doesn't run when you tap."
So lots of interesting stuff going on in Google's effort in improving the entire mobile experience across mobile devices. The line between mobile and web is already blurring and will only increase.
As Nexus owners and in a number of cases here on Overclockers, web/mobile devs, this is a big deal.
https://divshot.com/blog/opinion/the-future-of-the-web-according-to-google/