After investigating, this is the image that’s causing the mixed content warning:
Looking at the source code, here’s a snippet of what you currently have:
<section class="section-contact" id="section-contact" style="background-image: url( https://fourfincreative.com/online/wp-content/uploads/2014/03/iStock_000045557738_Small.jpg);">
This issue can be easily fixed on your end by changing manually to the following:
<section class="section-contact" id="section-contact" style="background-image: url(//fourfincreative.com/online/wp-content/uploads/2014/03/iStock_000045557738_Small.jpg);">
Q: Why doesn’t Remove HTTP remove the protocol in this case?
We only have protocols removed from the following sources:
script
,link
,base
,img
,form
,a
,meta
,iframe
,svg
In previous versions, we did have a more aggressive algorithm to remove any reference of https://
or https://
. However, we discovered that it was too aggressive and caused issues with some plugins.
I also see that your other <section>
tags use protocol-relative URLs:
<div class="services-bg" style="background-image: url(//fourfincreative.com/online/wp-content/uploads/2014/03/smallboat.jpg);"></div>
<div class="blog-bg" style="background-image: url( '//fourfincreative.com/online/wp-content/uploads/2014/03/blog.jpg' );"></div>