WordPress: mixed content blocks CSS and photos after HTTPS
When SSL is enabled, the page looks incorrect because the browser blocks the resources loaded by HTTP. Old addresses http:// in the recital, CSS or database may remain despite the domain itself transition to HTTPS.
How to determine the source of the error
Open Console and Network, establish the exact mixed resources and the place where they are generated.
Compare WordPress Address, Site Address and Static Theme URL.
What to do step by step
1. Replace the internal HTTP with valid HTTPS and unify theme and plugin settings. After the amendment, perform a subpage test with the oldest photos, because that is where the historical HTTP URL remains most often.
2 . Check that the external source actually supports TLS; otherwise, replace the service or resource.
How to check the score
The console does not report mixed content, and all styles and images load up on HTTPS.
What to do
Do not mask the problem by disabling the protection of mixed content in the browser.