In order to protect my visitors’ data, increase loading speed, and move up the ranks on Google, I recently converted this blog from an unsecured http://… site to a secure https://… site. What happened since, however, is not exactly as expected.
The site does not load any faster, the number of daily visitors has been cut by a factor of three, and some readers have told me that they are getting warnings from Google when connecting.
According to the company that hosts my blog and sold me my security certificate, the site is clean. To make sure it stays that way, I have also beefed up its security with tools from WordPress.
According to the hosting company, it may take four to six weeks for Google to notice that the site is safe and stop emitting the warnings.
Apr 18 2018
This blog is secure
The site does not load any faster, the number of daily visitors has been cut by a factor of three, and some readers have told me that they are getting warnings from Google when connecting.
According to the company that hosts my blog and sold me my security certificate, the site is clean. To make sure it stays that way, I have also beefed up its security with tools from WordPress.
According to the hosting company, it may take four to six weeks for Google to notice that the site is safe and stop emitting the warnings.
#BlogSecurity
Share this:
Like this:
By Michel Baudin • Announcements • 2 • Tags: Blog Security