Fixed HTTPS mixed content warning

The script scr for both javascript resources is HTTP only. If a site is using HTTPS, the browser gives a mixed content warning because both HTTPS and HTTP content is being used on an HTTPS page.  This is the easiest way for data leakage (like cookies).

Refactored code to using protocol relative links. This will allow the javascript files to be downloaded on the same protocol (HTTP or HTTPS) depending on the current protocol for the page. I have checked and Google serves the files on both HTTP and HTTPS.