Well, specifically removing the html5 offline application cache if you don't need offline functionality.<p>That it causes duplicate requests, and apparently more of them in chrome mobile than other browsers, is interesting though.
> Never use the application cache (or service workers) unless you actually need offline features.<p>I disagree. Appcache is deprecated and you should never use it under any circumstances. On the other hand, service workers are cool and there are reasons to use them even if you don't need offline features.
Since when is only testing in Chrome an acceptable way to develop web applications?<p>I wish the author had shown us some other browser results. I'm curious if the iframe changes affected Safari, Firefox, or Edge. (Others have noted that app cache is deprecated).
This article just displays the author's lack of knowledge of the subject matter he is developing with. Something tells me it was written just to get the company's name out there.
Did you know you can use Firefox Developer Tools to remotely debug mobile Chrome? It's still in heavy development, but I'm guessing it's easier than trying to quiesce browser activity and tease out network events manually. <a href="https://developer.mozilla.org/en-US/docs/Tools/Valence" rel="nofollow">https://developer.mozilla.org/en-US/docs/Tools/Valence</a>