I deal with this every day.
Most browsers are now pointing out a 'not secure connection', even when a secure connection isn't needed.
They did give developers a little warning, but it's a pretty aggressive change.
At work, we are seriously considering paying a couple grand a year to alleviate the problem .. per server on multiple servers.

On the flip side there's really no need for a browser to point out the connection is 'not secure' when it doesn't need to be secure.
Secure is of course better, but browsers are indeed leaning to alarming the user unnecessarily.

They need to give SysAdmins a little more time to adapt, and the Consumer a little more time to absorb the cost (costs get passed on).
If I gotta make a server 'all https' (secure) it costs me more .. and therefore your charges go up to cover it.

FWIW I'm cool with wanting a totally encrypted internet (which is all this initiative really is) but it will indeed cost more. So don't complain unless you are willing to pony up ..
smile
/just my thoughts

Make your sound your own!
.. I do not work here, but the benefits are still awesome