For the past few years, we have seen Google sending clear messages through their blog and Google Search Console to switch from HTTP and implement the HTTPS encryption. It was their share in pushing to more secure browsing. Migrating to an HTTPS site is not something most companies consider easy, so they avoided to adopt this push and switch to HTTPS. Now, we have a deadline – as of July 2018, Chrome will begin explicitly warning users if a site is insecure.<\/p>\n
![\"unlocking-lock-icon\"](\"https:\/\/paprika.paprikartdev.com\/wp-content\/uploads\/2022\/12\/unlocking-lock-icon.jpg\"){kind=icon}
Google announces that a warning will begin to be shown with all insecure websites. Currently, there is an icon displaying for HTTP pages in the address bar, and starting from July, we will also see the \u201cnot secure\u201d message. This would be in Chrome\u2019s address bar (also known as the Omnibox), indicating the website is \u201cNot secure.\u201d This warning will show for all HTTP websites.<\/p>\n
By this announcement we have seen that Google has a firm goal to warn users of insecure sites, directing more web publishers into upgrading to HTTPS. Google\u2019s announcement provided an example of how the \u201cOmnibox\u201d address bar security warning will appear.<\/p>\n
![\"treatment-of-HTTP-pages\"](\"https:\/\/paprika.paprikartdev.com\/wp-content\/uploads\/2022\/12\/treatment-of-HTTP-pages.png\")
<\/p>\n
This kind of a warning most certainly affects user experience, causing many visitors to leave a site. This causes a bounce rate jump, and a significant drop in advertising impressions, affiliate clicks, and e-commerce sales.<\/p>\n
A site that is not updated to HTTPS will most likely experience a loss of organic search rankings for their content within a Google search results page.<\/strong> With 92% of searches occurring on Google, this has the potential to greatly impact your sites organic SEO traffic.<\/p>\n This issue wasn`t explicitly mentioned in Google\u2019s announcement. But we can expect that mixed (secure and insecure) webpages will eventually trigger the warning. This is safe to assume, having in mind Google`s long-term commitment to a more secure browsing.<\/p>\n Chrome\u2019s Lighthouse web page auditing tool can identify what web page elements are triggering a mixed content warning. It states that mixed content audits can help developers migrate to HTTPS, with a help from an automated tool. The Lighthouse helps developers find which resources a site loads using HTTP, and which of those are ready to be upgraded to HTTPS simply by changing the subresource reference to the HTTPS version.<\/p>\n Despite many past controversies regarding SSL certificates and site speed, everywhere we implemented HTTPS we have seen speed improvements.<\/strong> We are running all procedure over HTTP\/2, and this is important to pinpoint.<\/p>\n Our past experience teaches us that performance benefits with HTTP\/2, noticing slight ranking and SEO benefit.<\/p>\n Security, as obviously is very important. Even WordPress blogs shouldn’t be passing login info in plain text. All information, and meaning no matter where it is passed should always be encrypted \u2013 just think of passwords, usernames and so. It involves trust and reliability, so the \u2018green light\u201d helps both ways.<\/p>\n We should also include the last but not least reason and it`s referral data. HTTPs to HTTP referral data is blocked in Google Analytics and usually ends up in the black hole of “direct traffic.” If someone is going from HTTP to HTTPS, the referrer is still passed.<\/p>\n No matter what, all web publishers should consider upgrading to HTTPS. This, by all means, is no longer an obligation limited to e-commerce sites.<\/p>\n Migration from HTTP to HTTPS is not a simple task, no matter the amount of information available on how to complete an HTTPS migration. Adding security to your site is now a crucial step in providing user confidence and improving the performance of your website.<\/strong><\/p>\n PaprikArt has the skills and methodology to create a plan for your site if it is currently running on the non-secure HTTP encryption.<\/p>\n Now is the time to act. With Google placing a high priority around security for their users, all websites need to follow suit and do the same.<\/p>\n","protected":false},"excerpt":{"rendered":" For the past few years, we have seen Google sending clear messages through their blog and Google Search Console to switch from HTTP and implement the HTTPS encryption. It was their share in pushing to more secure browsing. Migrating to an HTTPS site is not something most companies consider easy, so they avoided to adopt […]<\/p>\n","protected":false},"author":1,"featured_media":3603,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false,"footnotes":""},"categories":[12],"tags":[],"ppma_author":[29],"class_list":["post-3610","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"acf":[],"yoast_head":"\nWill Chrome display warnings for Mixed Content Pages?<\/h2>\n
HTTPS speed issues<\/h2>\n
What should you do?<\/h2>\n
![\"hand-pressing-security-button\"](\"https:\/\/paprika.paprikartdev.com\/wp-content\/uploads\/2022\/12\/hand-pressing-security-button.jpg\")
Most web hosting providers already provide free HTTPS certificates as well as low-cost certificates. The budget for upgrading should no longer be an excuse for waiting. Perhaps the most valid reason for waiting is technical issues. Among the considerations for upgrading to HTTPS are the mixed content issues, where a secure webpage links to a webpage asset such as JavaScript or CSS using an insecure URL. There are issues a publisher needs to consider against possibly losing traffic and revenue.<\/p>\n