[Closed] Massive SQL Query Requests when WPML is active

OK, let me mark this as awaiting feedback from you, and you can update when you have more details.

In your initial post you said the problem was in the backend, but the profile you just linked to is for a front-end page.

Looking at the profile it does show WPML as consuming the most time (plugins.php), but on that page you will notice a warning about the number of plugins using Composer, and how this might distort the time reported for WPML.

The full text of the explanation is here: hidden link

Composer is a shared library, and WPML happens to load it before all of the other plugins which also use it, which means their use of Composer to autoload classes gets attributed to WPML, so that WPML's execution time is distorted up and the times of all the other plugins which use Composer are distorted down.

And on the second tab (Scripts.png) it shows that the main "problem" script is the Composer ClassLoader script provided by WPML.

Discounting this, it's not obvious that there is a problem originating with WPML.

I temporarily activated Query Monitor to inspect the queries for the test page, but it doesn't seem to work on the front end for some reason, so I wasn't able to go any further.

Hello again Ronny

When I visit the same page you referred to after activating Query Monitor it looks pretty normal (screenshot), so I only have the profile results to go on in terms of evaluating what might be wrong.

There is one thing that jumps out in the profiles to me that I'd like to fix, and then run some fresh profiles without that distortion so that we can get a cleaner look at page loading process.

Some of the profile results are more affected than others by this code that you have added to your child theme's functions.php:

function wpml_fix_missing_icl_tables() {
  
    if( function_exists( 'icl_sitepress_activate' ) )
  
        icl_sitepress_activate();
  
}
add_action( 'wp_footer', 'wpml_fix_missing_icl_tables' );

On every page load you are triggering the WPML plugin activation code (i.e. the code that runs when you first activate the WPML plugin). As you can imagine that does a lot of tasks such as checking the existence and integrity of the WPML database tables which are redundant when loading pages (front-end or back-end), and I can't imagine why you are running that code from your child theme.

Please edit the file and remove that code to provide more of a clean slate for testing.