LCP on PageSpeed

Hi @texnavi2024

Thank you for reaching out and letting us know about the issue.
Could you please share a link where the widget is visible?
This will help us investigate the matter more thoroughly and provide assistance as quickly as possible.

Thank you for your patience and the details! ??

Best regards,
Laca from Trustindex

@lacadev please see picture attached

https://ibb.co/Y7CD97p

Hi @texnavi2024

Our Pro widget offers a solution for the LCP issue highlighted in Google Speed Insights. In the widget editor, you can find this feature under Main Settings -> Other -> Delay Load checkbox.

I have enabled this feature for you. However, it seems that your website is currently using the free shortcode of the plugin. Please replace the embedded shortcode with the Pro widget shortcode.

Could you kindly let us know if this resolves the issue on your end?

Best regards,
Laca from Trustindex

Hi @lacadev, I have changed the widget for the free version yesterday after I noticed the pro widget is delayed, I do NOT want the widget to be delayed as I want it to be shown on first page load (I am using perfmatters and added the loader.js to exclusions list). I have been using the free version of the plugin for a couple of months now and all was fine (pagespeed score was always over 90) until newer versions of the plugin were released. I’d like to stick to the pro version so please let me know if there’s anything else I should try other than delaying it. Thank you

Hi @texnavi2024

I’ve investigated the issue and found that Google PageSpeed Insights does not always flag the widget as the Largest Contentful Paint (LCP) element. For example, here is a test where no such issue occurs:
?? View test results

I believe that if the server response time is slower — as seen in this other test:
?? View test results
— then it’s possible that the widget may be flagged as the LCP. However, even in this case, the widget was not marked as the LCP.

From the widget’s perspective, there is nothing to optimize on our end. I recommend reaching out to Perfmatters support to investigate what might be causing the increase in server response time. Identifying and addressing that root cause should provide more clarity on this issue.

Let me know if you’d like further assistance or clarification.

Best regards,
Laca from Trustindex

Hi @lacadev

The issue is not occuring anymore because I have sorted the problem since my last post, the problem is that the widget is for some reason going over the width of the section (or container) on the mobile, I even tried to set the widget width to 100% (or smaller) using css code and that didn’t work. In the end I set the section to full width and that solved it, but if I set the section as it was before the problem will still be there.

Thank you

Hi @texnavi2024

Thank you for your update.

To clarify, the widget automatically fills the available space by taking the width of its parent element. For optimal performance, it’s important that the parent element is set as a block-level element. This ensures the widget can fully occupy the available width without overflowing or requiring manual adjustments.

.parent-container {
display: block; /* Ensures the parent is a block element
*/ width: 100%; /* Full width for the parent */
}

If you have any further questions or need additional guidance, feel free to reach out. We’re happy to assist! ??

Best regards,
Laca from Trustindex