Chrome 55 (latest beta build available via Chrome Canary) has the ability to specifically flag a HTTP website as non secure.
This is a pretty big step change in making encryption much more important for every site owner. There has been talk that Chrome will also introduce a warning for sites containing password fields but no HTTPS. At this time there is no difference with the standard HTTP website “Not Secure” warning.
It looks as though Chrome are slowly encouraging owners to go HTTPS even if they don’t think it is needed.
Switching your site to 100% HTTPS
Most of the time websites will just switch to HTTPS when they are asking for private data such as login or contact…
More prominence is also given to sites deploying correctly configured HTTPS certificates.
Finally EV Certificates continue to highlight the organisation details providing additional validation and trust.