In 2010, Google claimed it had a way to significantly reduce the time it took to load encrypted websites, and in 2011, it proclaimed success: "False Start" reportedly reduced the latency of SSL handshakes for users of the Google Chrome browser by 30 percent. The only problem was that the company couldn't find a way to make it work with all such websites, only about 95 percent, and those that didn't work couldn't fail reliably enough that Google could add them to a blacklist or refused to fix their incompatibility. That's why Google security researcher Adam Langley announced that starting in version 20 of the Chrome browser, False Start will be turned off by default... and why the Google initiative will likely join the ranks of other tech industry in-jokes like Digital Rights Management and Microsoft Works.
Chrome's False Start lives up to its name: web security gets slower (but more compatible) in Chrome 20
Chrome's False Start lives up to its name: web security gets slower (but more compatible) in Chrome 20/
Google is turning off False Start in Google Chrome, which reduced the latency of SSL handshakes but was found to have lingering incompatibilities.