Don't forget the appointments

B2C Data Innovating with Forum and Technology
Post Reply
badsha0016
Posts: 12
Joined: Tue Dec 17, 2024 6:02 am

Don't forget the appointments

Post by badsha0016 »

This reason is for all marketers. If you use Google Analytics, you're probably familiar with referral data. Many people don't realize that HTTPS to HTTP referral data is blocked in Google Analytics. So what happens to the data? Most of it is lumped into the "direct traffic" section. The referrer is still passed through if someone switches from HTTP to HTTPS.

This is also important because if your referral traffic has algeria whatsapp number data suddenly dropped, but direct traffic has gone up, it could mean that one of your biggest referrers has recently migrated to HTTPS. The opposite is also true.

5. Chrome Warnings
Since 2018, Chrome versions 68 and above mark all non-HTTPS sites as "Not secure" even though they don't collect data:

Not secure connection in Chrome
Not secure connection in Chrome
In 2021, the browser started using the HTTPS protocol by default for incomplete URLs. For example, if a user types “domain.com,” Chrome will automatically use “https://domain.com.” If HTTPS fails because it lacks SSL/TLS, it will fall back to HTTP.

Chrome has over 77% of the browser market share, so this will affect a lot of your visitors. You can also check which browsers your visitors are using in Google Analytics under Audience > Technology > Browser & OS:

Google Analytics Browser Share
Check Browsers in Google Analytics
Google is making it clear to visitors that your WordPress website might not work over a secure connection. Here are some tips from Google on how to avoid the warning.

Firefox also followed suit with the release of Firefox 51 in 2017, displaying a grey padlock with a red line for unsecured sites that collect passwords. Of course, if you migrate your entire site to HTTPS, you won't have to worry about this:

Non-private connection
Non-private connection
You may also start receiving the following Google Search Console warnings if you haven't migrated to HTTPS yet:


The following URLs include password or credit card input fields that will trigger the new Chrome warning. Review these examples to see where these warnings will appear, and you can take steps to help protect user data. The list is not exhaustive.


The new warning is the first stage of a long-term plan to mark all pages served over the unencrypted HTTP protocol as "Not secure."

6. Performance
Last but not least, we have performance. Thanks to a protocol called HTTP/2, those running properly optimized sites over HTTPS can often see speed improvements.

HTTP/2 requires HTTPS due to browser compatibility. The performance boost is due to a number of reasons, including HTTP/2 being able to support better multiplexing, parallelism, HPACK compression with Huffman encoding, the ALPN extension, and server push. There used to be quite a bit of TLS overhead on HTTPS, but it's much less now.

TLS 1.3 is also out, which speeds up HTTPS connections even further. Kinsta supports TLS 1.3 on all of our servers and our Kinsta CDN.

It's also important to note that web performance optimizations like domain sharding and concatenation can hurt your performance. They're now deprecated and should mostly no longer be used.

Everything on the web should be encrypted by default. – Jeff Atwood, Co-Founder of Stack Overflow

HTTP to HTTPS Migration Guide
It's time to move on to the fun part: migrating your WordPress site from HTTP to HTTPS. Let’s go over some of the basic requirements first, plus a few things to keep in mind.

You’ll need an SSL certificate. We’ll go into more detail on this later.
Check that your WordPress host and CDN provider support HTTP/2. Kinsta has HTTP/2 support for all of our clients. It’s not required, but you’ll want it for performance.

Image

You’ll need to set aside significant time to redirect HTTP to HTTPS. Migrating isn’t something that can be done in 5 minutes.
Double-check that all of the external services and scripts you use have an HTTPS version available.

It’s important to know that you will lose social share counts on all of your posts and pages unless you use a plugin that supports share retrieval. This is because your share counts are based on an API that looks at the HTTP version, and you have no control over third-party social networks.
Depending on the size of your site, it may take some time for Google to re-crawl all of your new HTTPS pages and posts. During this period, you could see variations in traffic or rankings.
Post Reply