Todor Piryankov

Hi @miloss84 ,

Suggesting that a user should buy a new phone because an Elementor widget fails is not a solution – it’s a lazy excuse. As @sebascalidoso clearly stated, this bug persists on high-end desktop environments too, so your “outdated Android 10” argument is completely irrelevant.

The truth is, your JS logic after v3.32.5 is broken. To prove how poorly optimized your current slideshow engine is, I’ve completely removed the Elementor Slides widget and replaced it with a simple custom CSS/JS solution using the exact same images.

The result? My “insecure” and “outdated” device now runs the Ken Burns effect perfectly and smoothly, while my Mobile PageSpeed score jumped to 90.

It’s embarrassing that a multi-million dollar builder fails where a few lines of manual code succeed flawlessly. Instead of sending me links to “System Requirements”, maybe you should send this to your dev team so they can fix the regression they’ve ignored for months. I’m moving forward with my custom fix since Elementor is clearly no longer reliable for professional use.

Best regards,
Todor

@sebascalidoso Come to think of it, it really isn’t right that the Ken Burns effect only works on newer devices and browsers—it should work on all of them. And it’s really strange that the issue still hasn’t been fixed in subsequent versions, which is why I’m also forced to stick with 3.32.5. So I’m marking this thread as unresolved.

@richardk23

Thank you for your cooperation!

For now, I will stick to the latest working version because Android is more widespread than iOS where I am, and I prefer it to work well on older devices as well as being able to test it on mine. I am marking the thread as resolved.

Hi @richardk23

I updated Elementor to the latest version again and the Ken Burns effect stopped working again on mobiles. I also noticed that the slideshow freezes on the second image, even though there are four. I’m inclined to leave it like this for a while so you can check it out, but I’m not sure I want to change the theme and disable plugins because I don’t want to interrupt the functionality of the website. Yes, I have custom code added with WPCode, but as I said, there have been no conflicts with Elementor so far.

• This reply was modified 6 months, 1 week ago by Todor Piryankov.
• This reply was modified 6 months, 1 week ago by Todor Piryankov.

Thanks for the reply.

I tried again. I updated Elementor to the latest version (3.33.0) again.

1. I cleared all caches and disabled mobile optimizations everywhere.

2. I regenerated CSS and Sync Library.

I tested again on several mobile devices on different browsers in incognito mode, and the Ken Burns Effect still does not work on them. As I mentioned above, as soon as I downgrade to the previous version, it works as before. Therefore, I am inclined to think that the problem is neither in the theme nor in a conflict with plugins, but is directly related to the Elementor update. In other words, the problem comes directly from the update, given that the current configuration has been working flawlessly with previous versions so far. For now, I am staying with version 3.32.5 and disabling updates until the problem is fixed.

Hi! I saw your reply late. These are the metrics from my home page. Interestingly, there is a Turnstale on the newsletter form, but I don’t think it comes from your plugin. It’s strange that it has an effect, but it’s a fact. I use WP Rocket for optimization. I am attaching screenshots from GSI for comparison, including the error it registers.

TurnstileError: [Cloudflare Turnstile] Error: 600010. at v (https://challenges.cloudflare.com/turnstile/v0/api.js:1:10343) at M (https://challenges.cloudflare.com/turnstile/v0/api.js:1:37691)