Did you know that the web browser on your phone or tablet waits three tenths of a second after you tap something to actually perform that action? You did if you're a web developer - it's a de-facto standard for mobile browsers, a built-in delay for the double-tap zoom function. But if you're on the newest Chrome beta, you won't see the delay, at least on mobile sites.

Why is this? According to Jake Archibald of HTML5 Rocks (a promotional and instructional project page from Google), it's because this delay is unnecessary if you're browsing on a page that's already optimized for mobile viewing. Since these sites typically restrict content zooming by double-tap or the pinch gesture anyway, there's no need for the artificial limitation, and Chrome can effectively run faster from an end-user standpoint. Archibald has an excellent demonstration above: notice how the browser on the left has a definite delay after each touch action. Here's the site from the demo if you want to try it in Chrome Beta.

2013-12-13 17.42.53

Mobile sites will need to be properly coded to take advantage of this, and the 300 millisecond delay will probably remain in effect for standard, non-mobile pages for the foreseeable future. Even so, it's an impressively simple way to increase performance with a very small change. Other mobile browsers may follow Google's lead here - Firefox already has a bug report and will likely implement a similar change soon. You can expect to see the delay on mobile sites disappear when Chrome 32 graduates to a stable build. Web developers, check the source link below for a technical explanation that will help you make sure your mobile sites are faster in Chrome.

Source: HTML5 Rocks - Thanks, Chromeguy