my client has a poor performance score on PageSpeed ​​(between 35 and 45). He is obviously aiming for higher scores (beyond 90) and therefore this score is a problem.

His website is on Prestashop 1.7 with creative elements.

The main problem seems to come from the LCP which has a rendering delay of around 15s. What I don't understand is that the element in question is an and I don't know how to solve this problem.

An image can be optimized or lazy loaded but i don't know how to optimize a text.

Anyone have an idea to resolve this issue?

Here is the link to the pagespeed report: /analysis/https-auditionet-fr/qowjjcks02?form_factor=mobile

Already tried to optimized the images, convert all to webp (with module). I've already activate js and css compress on back office.

my client has a poor performance score on PageSpeed ​​(between 35 and 45). He is obviously aiming for higher scores (beyond 90) and therefore this score is a problem.

His website is on Prestashop 1.7 with creative elements.

The main problem seems to come from the LCP which has a rendering delay of around 15s. What I don't understand is that the element in question is an and I don't know how to solve this problem.

An image can be optimized or lazy loaded but i don't know how to optimize a text.

Anyone have an idea to resolve this issue?

Here is the link to the pagespeed report: https://pagespeed.web.dev/analysis/https-auditionet-fr/qowjjcks02?form_factor=mobile

Already tried to optimized the images, convert all to webp (with module). I've already activate js and css compress on back office.

• prestashop
• pagespeed
• lighthouse

1 Answer 1

So this is due to the fact that you have a carousel that changes after some time.

If you look at the screenshots of the page loading you see the full page loads all at roughly the same time:

So LCP should equal FCP which is 2.3 seconds. Instead LCP is much later.

However, we can also see the LCP is a different element:

When I load the page and wait 15 seconds I can see that the cookie banner pops up (and that has the potential to be a new LCP element) and that the carousel then automatically moves to the next item (and that IS what is recorded as the LCP element).

LCP will continue considering new elements until the user interacts with the page (including scrolling). So these late displaying elements can be considered when the page is loaded but not interacted with (and Lighthouse does not interact with a page but just loads and waits for the page to settle).

The good news is that your actual users experience a very fast LCP as shown in the MUCH MORE IMPORTANT “Discover what your real users are experiencing” section at the top of the report, so I guess most users are interacting with the page before those late loading items load. So there is no issue here really.

If you want the lab-based, diagnostic, Lighthouse tests to more accurately reflect this real LCP then do try not to load larger elements after the main page load (either by switching off auto carousel scrolls or by ensuring that text is smaller).