Unhooking addPreconnectLink

;hello

Hello there!

Thank you for contacting Tidio Support. My name is Ricardo, and I’ll be happy to help you with your inquiry.

Adding a pre-connnect link in your HTML serves to improve website performance by giving the browser a heads-up about domains it will need to establish connections with in the near future.

Could you please let us know more about why it is unnecesary for you? We’ll forward your request to our dev team for review.

Also, please let us know:
? The URL of your website
? The Public Key of your Tidio project, which can be found here:
https://www.tidio.com/panel/settings/developer/developerData
?
Looking forward to your reply!

Thanks for your reply, @olektidio.

In my case, I only load Tidio after cookie consent is granted by the visitor.

In this case, Tidio is always preconnecting, preceding other critical resources, while it often ends up not loading at all (because cookie consent wasn’t granted). That’s a waste.

In general, please refer to the MDN documentation:

If a page needs to make connections to many third-party domains, preconnecting them all can be counterproductive. The <link rel="preconnect"> hint is best used for only the most critical connections.

rel=preconnect – HTML: HyperText Markup Language | MDN (mozilla.org)

I don’t think Tidio is often a critical connection, as it isn’t usually the first thing a user interacts with. A user is likely to browse around and only use Tidio if they don’t find what they are looking for.

Having this in mind, preconnecting Tidio can unnecessarily compromise the performance of the website without providing any meaningful benefit.

Anyway, I believe it makes sense and good practice to let the developer or site owner decide whether Tidio is a critical asset or not.

Please let me know if makes sense to you and if you have any more questions.

URL of my website:

https://hobbies4.life

Thanks again.

@olektidio, just making sure my explanation was clear enough and checking if there is an update by any chance.

@olektidio, is ticket still being watched?

Hello there,

Thank you for your valuable feedback.

We apologize for any inconvenience this may cause. We have discussed your concerns with our engineering team, and currently, it won’t be possible to remove the preconnect. However, we have forwarded this feedback to our product team for consideration in future updates.

We’d also like to assure you that our chat widget is designed to load asynchronously. This means it loads independently of your website’s key elements, ensuring it doesn’t interfere with your site’s performance or loading speed. The crucial resources of your site remain unaffected, and the chat widget loads at its own pace without waiting for other content to load first.

For more details on how Tidio loads in your website, please refer to https://help.tidio.com/hc/en-us/articles/5462176187932-Tidio-Loading-Speed

Thank you for your understanding and for helping us improve our product.

• This reply was modified 5 months, 2 weeks ago by olektidio.

Thanks @olektidio for getting back to me.

Regardless of the widget design, the <link rel="preconnect"> takes precedence over other resources, and therefore impacts performance.

For this reason, your claim that “it doesn’t interfere with your site’s performance or loading speed” isn’t accurate.

Under optimal conditions – or lab conditions, as the document you referred me to describe – the impact may be minimal.

Nevertheless, the impact exists and under suboptimal – real life – conditions might make a difference.

I believe your plugin is the first I came across that forces <link rel="preconnect">.

Hopefully, your product team will make future changes.

Thanks again.

Hello, @olektidio.

Is there an update on this?

Thanks.

Hi again!

Thanks for your response.

With the details shared from your end we can assure you we understand your needs behind the request and we find your feedback valuable. We have already passed it to our developers.

They confirmed, that for most users having the widget preconnect enabled is better and by default should stay like that.

We may consider enabling the option in the checkbox to have preconnect disabled, but we are not able to promise introducing it. Your understanding will be appreciated.

Please contact us back in case of any other questions.

Thanks, @olektidio.

A filter may be a faster and easier to implement solution.

Thanks again.