WPSSL.com

My understanding is that GA tracks through the code on your site, rather than the details you enter into their admin panel. It’s easiest to make sure it’s all consistent, but you shouldn’t get any tracking issues when switching your URLs to HTTPS. Redirects are going to be more of a pain on the SEO side than analytics.

It looks like you’ve already made the switch to HTTPS which is great, however I noticed a couple of mixed content warnings on the homepage. You just need to fix up the URL paths for these hero images to make sure you get that padlock symbol:

https://www.*.com/wp-content/uploads/b*-dental-care-children.jpg
https://www.*.com/wp-content/uploads/b*-dental-clinic.jpg

I’ve hidden the specifics as per your requests above but it should be easy enough to find those files and swap to HTTPS at the start.

Hi Julie. I’m still seeing mixed content warnings on your homepage. This now appears to be coming from the webcam feed. Are you able to make the webcam images come through over HTTPS also?

The JS file is hosted with Rafflecopter so it needs to be updated at their end.

Is there an option in the editor at Rafflecopter to turn off Facebook login or sharing? The image in question is a Facebook icon so if you stop that part of the script running you might have some luck.

Otherwise try some other Rafflecopter themes or styles. Anything you can do that might change the JS file provided by Rafflecopter is worth testing.

You could in theory just copy that JS file to your own server and update the code directly. But that can get messy quickly and is probably not allowed per the license agreement with Rafflecopter.

• This reply was modified 5 years, 4 months ago by WPSSL.com.

Looks like a CSS conflict somewhere. Can you open the developer view in Chrome and see what it might be causing it in there?