• Hi Elementor support team,

    It looks that the development team at Elementor is quickly derailing, and you have to provide them with feedback from the users to help to get back on track.

    With the new version of Elementor Pro 3.1 and Elementor 3.1, you keep adding more JS files that cannot be removed with Asset CleanUp. Now you have added 150kB “pro-preloaded-elements-handlers” and only a tiny function – animated text – is dependent on it on my website.

    So, during just single month you have added extra 7 files:
    Elementor front-end legacy
    elementor_webpack_runtime
    elementor_pro_wepack_runtime
    pro-preloaded-elements-handlers
    wp-i18n
    wp-polyfill
    elementor-pro-app

    Congratulation, by the end of this year, Elementor Pro will be viewed as the slowest Page builder option on the market.

    Your company effort to provide new Experimental options is a slow car crash disaster. The reduced DOM option does slow down the website. The improved asset loading is calling JS files from other JS files.

    I have managed to preload this strange JS calls from JS files via adding to the HTML something like:
    <link rel=”preload” as=”script” href=”/wp-content/plugins/elementor-pro/assets/js/form.9c115e6f5683e739f4d6.bundle.min.js” />
    For wiper.JS we have to use a slightly different option by adding crossorigin=”anonymous”
    <link rel=”preload” href=”/wp-content/plugins/elementor/assets/lib/swiper/swiper.min.js?ver=5.3.6″ crossorigin=”anonymous” as=”script” />
    But even after the files are preloaded and thus are already there for the parsing process, your terrible implementation of the new “Improved Experiment” results in an extra second of the parsing of JavaScript files on mobile and desktop devices. Is it worth to save 100k of unused JS to slow down the website by one second? Who is working in your testing department to wet such new features through? Especially as selecting your Experimental options leads to irreversible degradation of the page loading speed. I had to restore from the backup to gain my previous page speed results!

    The main question to your support team:
    Why don’t you care about the page speed score?

    Best regard

    Victor

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter zhiv12

    (@zhiv12)

    The test department’s job is to stop the Elementor team from releasing changes that slow down every website built using Elementor Pro. It is a sad story that the Elementor team does not have enough budget to hire professionals for their test department.

    Hello,

    Regarding your message, I want to let you know that we are already aware of this bug caused due to recent 3.1.1 update and it’s been already reported to our developers.

    I don’t have any ETA on when it will be addressed or a fix released, but as this issue is a high priority for us I believe it should be fixed in one of the upcoming plugin’s updates.

    Once the fix is released we will update it on our changelog page:
    https://elementor.com/pro/changelog/
    https://github.com/elementor/elementor#changelog

    If this feature is critical for you, you can currently downgrade the Elementor plugin to the previous 3.1.0 version where it should work as expected.

    Rolling Back To a Previous Version of Elementor

    Regards,
    Said

    Moderator Jan Dembowski

    (@jdembowski)

    Forum Moderator and Brute Squad

    The test department’s job is to stop the Elementor team from releasing changes that slow down every website built using Elementor Pro.

    For pro or commercial product support please contact the developer directly on their site. This includes any pre-sales topics as well.

    As the developer is aware, commercial products are not supported in these forums. I am sure they will have no problem supporting you there.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Degradation of page loading speed’ is closed to new replies.