Google Chrome developed a way to warn every user about insecure sites. It is easier for some to shop or pay their bills online, but they need to know that the site they accessed is secured and that they can safely type in their credit card information. Sometimes sites do not indicate whether they are protecting sensitive data.
Nevertheless, Chrome thought they should come up with a plan. The last update of Google Chrome is bound to make everything easier for users. When you access a site which asks for your credit card info or a password and the site does not use HTTPS, it will be automatically flagged by Google as insecure. The warning sign will occur in the address field.
It is like Google uses this red letters to mark and promote their new initiative known as “HTTPS for all.” In this way, they hope that they will be able to determine more internet browser companies to use this method too. Besides these warnings regarding insecure sites, we find out from Google Chrome’s blog that they update a lot of features.
For instance, the speeds of page reload were boosted, now reaching 28% on mobile for one particular site. Google Chrome on cell phone developed a simplified loading behavior for validating the primary resource and then it goes on to a normal page reload. The new action is bound to boost the reuse of cached sources, resulting in data usage, power consumption and reduced response time.
Takashi Toyoshima from Google stated that Facebook has recently contacted the company, arguing that Google Chrome was imposing triple validation requests from other browsers. The changes recently implemented resulted in the speed boost for loading on the social network. However, it is not clear whether or how that performance increases are used across the network as a whole.
Based on the statements of developers, the newly updated version of Google Chrome did not only boost the speed of different loading sites, but it also uses less power and bandwidth. When reloading an individual site, browsers tend to check first with the web server searching for any available stored resources. Unfortunately, the outcome of this kind of situation represents numerous network requests per page rendered to dozens of domains.
Image courtesy of: wikipedia