Earlier quoted context omitted.
Encrypting site content increases server load, so response time may lack a little.. and we all know Google does take that into account. Also, it might be important that robot files and sitemaps are under the https protocol. I am guessing Google is pretty darn smart about it, I can only imagine though that a broken certificate throws a red flag.
Ha! Interesting.. I wonder if Google does count that against you since part of their latest algorithm factors in page load times.. though I would think that having your site behind https might give you some extra kudos somewhere.. considering you verified the integrity of your site at least.. (ALTHOUGH, there was that recent security breach where we someone can spoof being a CA...)
Ask HN: Put my entire website behind ssl?
21–23 of 23 posts
Re: Ask HN: Put my entire website behind ssl?
#22Earlier quoted context omitted.
Wow, I didn't think about twitter's button. :-/ We use the twitter widget.. Do you know if the twitter js is behind a valid cert?
Unfortunately, it's been invalid for awhile. You can check it out for yourself here: http://platform.twitter.com/widgets.js vs https://platform.twitter.com/widgets.js
Luckily, we don't use that js, we use:
http://twitter.com/javascripts/blogger.js
and I just checked the certificate behind this and it's valid (I should hope twitter's main cert is valid!):
https://twitter.com/javascripts/blogger.js
and we use the json API:
http://api.twitter.com/statuses/user_timeline/healpay.json?c...
which also happens to have a valid cert:
https://api.twitter.com/statuses/user_timeline/healpay.json?...
So it looks like we're in the clear for this at least :)