ConceptionJFG
All articles
Technology2 min read

The little padlock: why your site needs HTTPS

That padlock in the address bar isn’t decoration. Without it, browsers flag your site “Not secure,” and clients run.

By Jean-François Gauthier

Look at the address bar of any serious site: there’s a little padlock right before the address. That padlock means the connection is encrypted, that what travels between the visitor and your site is protected. It’s called HTTPS, and today it’s no longer optional. Without it, your site can flat-out show “Not secure” in red, and that scares people off.

What the padlock really protects

Without HTTPS, information travels in the clear between the visitor’s browser and your site. On a café’s public wifi, someone malicious could intercept a contact form or a card number. HTTPS scrambles all of that: even intercepted, the content is unreadable. It’s the difference between mailing a postcard anyone can read and a sealed envelope.

What visitors see

Browsers have gotten strict. A site without HTTPS shows a “Not secure” warning, sometimes a big red page blocking access. No matter how good your content is, most people back away from that screen. For a business, it’s like hanging a “warning, danger” sign on your front door. Nobody walks in.

  • A padlock = instant trust for the visitor.
  • “Not secure” = many people close the tab.
  • Mandatory the moment you have a form or a payment.
  • One of the signals Google weighs when ranking you.

Good news: it’s free and automatic

It used to be that a security certificate cost money and was installed by hand. Today, good hosts add it for free and renew it on their own. A site exported from CJFG Studio and hosted on a modern service gets its HTTPS automatically, without you touching a thing. You don’t even need to understand the details, just make sure it’s active.

HTTPS isn’t a technical luxury. It’s the bare minimum for a visitor to trust you before they even read you.

How to check yours in ten seconds

Open your site and look at the address bar. See a padlock and an address starting with “https://”? Great, you’re protected. See “Not secure” or a crossed-out padlock? That needs fixing fast. Test on your phone too, because that’s where most of your visitors arrive.

If your site still shows the warning, don’t let it linger: every day, it costs you clients who back away without telling you. Write me and I’ll put your padlock back in place. It’s quick, and it’s sorted once and for all.

Share this article
  • HTTPS
  • SSL certificate
  • secure site
  • browser padlock
  • not secure warning

A web project in mind?

Like these ideas? Let's put them to work on your site. You'll be talking directly with the founder.