How to fix mixed content on Wix

Steps for Wix

1. Wix serves all its own assets over HTTPS automatically. Mixed content typically comes from custom HTML widgets or Velo (code) blocks.
2. In the Wix Editor, click on any HTML Embed or Custom Embed widget → Enter Code, and manually update any 'http://' src or href values to 'https://'.
3. If you use Wix Velo, open the code panel (Dev Mode) and search your page and site-level code files for 'http://' string literals — update them.
4. For third-party apps added via the Wix App Market, contact the app developer if their embed code references HTTP resources.
5. Re-test using browser DevTools Console on your published site.

What is mixed content?

Mixed content happens when a webpage is served securely over HTTPS but one or more of its resources — images, JavaScript files, CSS stylesheets, fonts, videos, or iframes — are still requested over the old, unencrypted HTTP protocol. Browsers treat this as a security problem because the page itself is encrypted but parts of it are not. Modern browsers either silently upgrade, actively block, or display a security warning when they detect mixed content. The result is a broken or degraded experience for your shoppers.

Mixed content can break visible elements on your store (images that won't load, styles that don't apply, widgets that silently fail), directly hurting conversion rates. Browsers like Chrome and Firefox block "active" mixed content (scripts and stylesheets) outright, meaning functionality you depend on — checkout widgets, live chat, reviews — may simply stop working. A broken padlock icon or "Not Secure" warning in the address bar destroys shopper trust at the exact moment they are deciding whether to buy. Search engines also use HTTPS as a ranking signal, and a compromised security indicator can undermine the SEO benefit your SSL certificate is supposed to provide.

See the complete Mixed content guide for every platform and the full background.