Troubleshooting CSS Not Loading on HTTPS Pages (Mixed Content)
If your page looks unstyled on HTTPS URLs, your CSS files may still be loading over http://. Browsers block those requests as mixed content, so styles never load.
Verify that mixed content is the cause
- Open an affected HTTPS page in an incognito/private browser window.
- Open your browser Developer Tools and go to the Console or Network tab.
- Reload the page.
- Look for errors such as
blocked:mixed-contentor messages saying a stylesheet was loaded over HTTP and blocked.
If you see those errors, continue with the steps below.
Fix HTTP asset URLs
1) Confirm your WordPress site URLs use HTTPS
- In WordPress, go to Settings > General.
- Check both WordPress Address (URL) and Site Address (URL).
- Make sure both values start with
https://. - Save changes if you updated anything.
2) Replace hardcoded HTTP URLs in your content or settings
Old content, page builder data, theme settings, or plugin settings can still contain http:// asset URLs.
- Search for
http://your-domain.comreferences in your content and settings. - Update those references to
https://your-domain.com. - If your site uses a search-and-replace tool, run it carefully and back up your database first.
⚠️ Warning: Always create a full backup before running a database-wide URL replacement.
Purge all cache layers
After fixing URLs, clear every cache layer so visitors get fresh HTTPS assets:
- In WordPress admin, use the Purge Cache button from the Super Page Cache toolbar menu.
- If you use additional caching/optimization plugins, purge those caches too.
- In Cloudflare, purge cache from your dashboard.
- Hard refresh your browser (or test in a fresh incognito/private window).
Verify the fix
- Reload the same HTTPS page.
- In Developer Tools, confirm stylesheets now load from
https://URLs. - Confirm there are no new
blocked:mixed-contenterrors. - Confirm the page styling appears correctly.
If CSS is still missing
- Temporarily disable other optimization plugins that combine, rewrite, or defer CSS, then test again.
- Check your theme/plugin custom code for hardcoded
http://stylesheet links.
