Google’s SSL Fail
This is stunning: I just spent the last two hours tracking down a checkout page problem and it turns out it was Google’s fail on SSL! This from a company that is promoting the hell out of “https” and security.
I went in to our checkout page and tracked every single element to make certain it was secure — and the Woocommerce software we use performs a “force SSL” on page elements to ensure they’re secure — but I just couldn’t figure out why I was receiving a warning in Google Chrome that said, “This page has insecure content.“
The problem? Warnings like this are overwhelming for most people and almost ALWAYS why they abandon their shopping carts. When you’re running a business, that’s the LAST thing you want people doing when they’re checking out!
Guess what I discovered after I did a “View Source” and finally an “Inspect Element” of the page viewing the console to see errors? THAT THE WARNING WAS BEING TRIGGERED BY THE GOOGLE FONTS BEING PULLED FROM THEIR SITE. Yep. It was the CSS declaration: @import url(http://fonts.googleapis.com/css?family=PT+Sans); that was the culprit. Simply adding an “s” after “http” fixed it and the warning vanished.
Seriously Google? Perhaps making SSL pulls mandatory will fix it. I know, I know…the SSL adds a lot of overhead and I’ll work on selectively pulling an SSL font just on the checkout pages, but you sure don’t make this stuff any easier with crap like this you guys.
About Steve Borsch
Connecting the Dots Podcast
Podcasting hit the mainstream in July of 2005 when Apple added podcast show support within iTunes. I'd seen this coming so started podcasting in May of 2005 and kept going until August of 2007. Unfortunately was never 'discovered' by national broadcasters, but made a delightfully large number of connections with people all over the world because of these shows. Click here to view the archive of my podcast posts.