seramo

The output from PageSpeed Insights is mistakenly identifying the WhatsApp button as the largest contentful element, but I understand the issue. Try testing a simpler page, like the Contact Us page, which has fewer elements. This should help confirm that the WhatsApp button isn’t causing the LCP delay.

You could test this plugin on a simpler page with fewer elements to verify if the LCP issue is indeed related to the WhatsApp button. This can help confirm if PageSpeed is mistakenly flagging it.

Hi @josedavidbravo

The LCP issue seems to be linked to other elements on the page, not the WhatsApp button. This plugin is fully optimized, lightweight, and doesn’t use any JavaScript. PageSpeed has likely misidentified it as the cause.

Web link is not valid in mobile mode, it switches to the second format.
The structure is the same on all pages, but your caching plugin may have an issue causing this problem.
You can check the exclusion rules of this plugin in the cache settings.
For tracking in Google Tag Manager, you can also use ids or classes.

You can use the button ID, like id="simple-chat-button--button".

Hi @carsermil

Try other modes in the settings section.

Your issue might be resolved with the “API” option because it uses the default WhatsApp API.

In future versions, it might be possible to select the type of link for desktop and mobile modes.

I will try to check this problem in the new version so that when copying or importing such additional items are deleted before storing in the database.

Thanks for your support

If possible, send the website address

If you are familiar with SQL, please send the output of this command:

SELECT?*?FROM?wp_options?WHERE?option_name?LIKE?‘%scb_%’

To check more and send website information, you can send through the links on my personal website

Hi @moikirsch
Please check that there are no extra characters in the entered mobile number
Please send more information for review

Hi @herzbaum

Apparently, your problem is solved

Usually this happens due to browser cache or wordpress and server cache plugins

Changes were made to fix this in the new version (1.6.0).
please check it @adiltibari

• This reply was modified 1 year, 5 months ago by seramo.

This will change in the new version

I will follow up on this matter, but since I do not have detailed information about this matter, it may take some time

Hi @adiltibari
Thank you for your kindness

Yes, you can contribute to the translation of this plugin

Hi @eghasimi

This item will be checked and if there is no security problem, it will be changed in the next version

Hi @ricaneaga
This item may be added in the future or a separate plugin may be written for it