-
Posts
-
Hi,
We worked on a few optimizations together in June, and things were going quite well to a certain extent.
Currently, this is a customer issue again. And despite all the optimizations, the score is at rock bottom, especially the mobile score. It doesn’t even pass the web core vitals.
Why doesn’t it stay stable at a good score?
What else can I do?
All practical ideas are helpful.Hey Sven,
Thank you for the inquiry.
The issue seems to be due to the addition of the Revolution Slider, which impacts the LCP (Largest Contentful Paint) score. We recommend hiding the default Revolution Slider on mobile view and display a more minimal replacement, like a static image or text.
The same slider also appears to be causing forced reflows, which can significantly affect performance. Unfortunately, we don’t have access to the Revolution Slider scripts, so we won’t be able to help directly with fixing this.
The server is responding well but there is a redirect on the first request which adds latency. This might be coming from a CDN or server configuration. You may need to contact your hosting provider or check redirect rules to resolve it.
Let us know if you need more info.
Best regards,
IsmaelHi Ismael,
Thanks for your feedback.
I know that the Revolution Slider costs performance. The customer wants it that way and also wants to see it on mobile. Furthermore, it’s no longer possible to disable it directly on mobile (it works via CSS). Personally, I don’t think the very poor mobile results have anything to do with that. I’ve attached a link from an Avada website with tons of slides from the same plugin. The result: decent results in Insights.
LCP is one problem, along with several others. I even deactivated the RS plugin once, and Insights then looks for another LCP problem.
My suspicion lies more in the consent and marketing tools and their code, which I had to use in many places. This includes Google Ads + GTM integration, various codes for Real Cookie banners, campaign tracking, and a service check widget in the footer code.
Is that possible? Do you see anything there or can you verify it?
It would be possible to create temporary access.Best regards Sven
Hi,
Thank you for the update.
The page speed reports clearly point to the Revolution Slider as the cause of the LCP issue, so it’s definitely the reason for the decreased score. On the second site, you’ll notice there is no LCP issue because the Revolution Slider only contains static images, without moving parts or animations, unlike the first site, which uses complex slides and effects.
This is the LCP report — note the element sr7-module#SR7_31_1.
LCP request discovery
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loadingLCP
lazy load not applied
fetchpriority=high should be applied
Request is discoverable in initial document
sr7-module#SR7_31_1 > sr7-content > sr7-slide#SR7_31_1-130 > sr7-img#SR7_31_1-130-23
Fixing this LCP issue should significantly increase the overall score. We recommend reaching out to the plugin developers for additional information about the issue.
Best regards,
IsmaelThanks!
Okay, I understand the difference in the animations of the plugin in this mentioned websites.
If I understood the report correctly, lazy loading shouldn’t be used, at least with the Revolution Slider plugin, so that the LCP resources are loaded immediately. (I always thought that would be good for optimization.) In the plugin with the new SR7 engine, which should actually be faster, you only have the following options:
SR7 Data Load Method: Preload / Smart Loading / on demand
SR7 Feed load Method: Preload / on demandOtherwise, I still don’t fully understand the report:
lazy load not applied => ?
fetchpriority=high should be applied => how??In the WP Rocket caching plugin, I’ve disabled lazy loading for images and background images for testing purposes.
Best Regards Sven
Hi,
It’s actually good to disable lazy loading for elements that affect LCP because lazy loading can delay their appearance. In this case, it’s already handled correctly, so there’s nothing you need to do for this part.
For the fetchpriority issue, if you’re using Image layers in the Layer Slider, go to Layer Settings > Attributes > Custom Attributes tab of the layer, then add fetchpriority as the attribute and set its value to high. The following article should explain what this attribute does.
— https://addyosmani.com/blog/fetch-priority/
Best regards,
Ismael
- You must be logged in to reply to this topic.