It seems to be because the images are loaded from another domain name and the URLs are defined with HTTP protocol. The quickest fix would be for the Live Map to always use HTTPS for those images, since an HTTP page loading HTTPS resources is fine but the other way around can cause issues with some browsers.