"Today we’re announcing that Chrome will gradually start ensuring that https:// pages can only load secure https:// subresources. In a series of steps outlined below, we’ll start blocking mixed content (insecure http:// subresources on https:// pages) by default. This change will improve user privacy and security on the web, and present a clearer browser security UX to users."

https://security.googleblog.com/2019/10/no-more-mixed-messages-about-https_3.html

Good idea to start checking your sites now for this problem.

Marshall
CENLYT Productions - ms designs
Affordable Web Design
Custom Ecommerce Designs
Responsive Websites
Cenlyt.com

Thanks for the heads up Marshall!

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

And by default, Firefox now [url="https://www.searchenginejournal.com/google-analytics-is-blocked-by-firefox-mozilla-explains-why/311471/"]blocks all Tracking Cookies like Google Analytics[/url], Statcounter, Facebook and Twitter, unless your website visitor has [url="https://support.mozilla.org/en-US/kb/content-blocking"]changed the default Content Blocking settings to "Custom"[/url].

If you notice a drop in Website Visit and Page View Counts, this could be one factor as to why.

Gary
[img]https://itzap.com.au/pics/logo/itzap-website-design-works-mini-logo.png[/img]