I thought about images too, but now the warning went away (certificate is OK), and I checked that the page has images served over HTTP. So it must have been something else.

Seems like the problem is solved now, though. By the way, I noticed bitcoin.org serves as HTTP. Why? I think it should be HTTPS-only, considering it provides software that deals with money.