Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 13:00 9:00 – 13:00 9:00 – 13:00 8:00 – 12:00 8:00 – 12:00 -
- 14:00 – 17:00 14:00 – 18:00 14:00 – 18:00 13:00 – 17:00 13:00 – 17:00 -

Supporter timezone: Europe/Zagreb (GMT+01:00)

Tagged: 

This topic contains 6 replies, has 0 voices.

Last updated by Bruno Kos 5 months, 3 weeks ago.

Assisted by: Bruno Kos.

Author Posts
September 11, 2025 at 6:11 am

hugyakA

Background of the issue:
I am trying to check why the website is very slow. I see a lot of WPML-related issues in the log file. The issue can be seen on the entire page: hidden link. [10-Sep-2025 17:56:00 UTC] PHP Warning: Cannot modify header information - headers already sent in /home/klauzalh/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/request-handling/class-wpml-language-per-domain-sso.php on line 123 [10-Sep-2025 19:53:01 UTC] Cron átütemezési eseményhiba a horoghoz: wp_fastest_cache_Preload, Hibakód: invalid_schedule, Hibaüzenet: Esemény ütemezés nem létezik., Adatok: {"schedule":"everyfiveminute","args":[],"interval":300} [10-Sep-2025 21:21:00 UTC] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/klauzalh/public_html/wp-cron.php:30) in /home/klauzalh/public_html/wp-content/plugins/sitepress-multilingual-cms/classes/request-handling/class-wpml-language-per-domain-sso.php on line 123

Symptoms:
The website is experiencing very slow loading times.

Questions:

September 11, 2025 at 7:17 am #17392878

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

I’ve tested the site with and without WPML to understand the performance issues:

* With WPML active, the site loads in about **17 seconds**.
* Without WPML, the site still takes about **10 seconds**, which is already quite slow.
* When I disable all plugins, the site loads in about **2 seconds** (with or without wpml)

This suggests that WPML is not the only factor slowing the site — there are likely other plugins contributing to the 10-second load time even before WPML is added.

Could you please help identify which plugin(s) are responsible for the slowdown when WPML is disabled? Once we know that, we’ll have a clearer picture of what’s causing the performance issues, and we can look at solutions for both the base speed and then the additional WPML overhead.

September 11, 2025 at 7:25 am #17392891

hugyakA

Hi, As I wrote, you need only deal wwith the wpml issues, I will manage the others, Thank you.

September 11, 2025 at 10:15 am #17393597

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

To troubleshoot this problem, I'll install the Duplicator plugin and generate packages for further debugging purposes. I'll ensure to exclude all media files to maintain a minimal package size.

You can find more information about the process here:
https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#get-help-from-support

Please confirm if this approach is acceptable to you!

September 18, 2025 at 4:28 am #17411571

hugyakA

I agree, of course, please feel free to do it. Thank you.

September 19, 2025 at 6:53 am #17415440

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

I am checking this with our 2nd tier and will keep you posted.

September 25, 2025 at 9:26 am #17431575

Bruno Kos
WPML Supporter since 12/2018

Languages: English (English ) German (Deutsch ) French (Français )

Timezone: Europe/Zagreb (GMT+01:00)

It looks like the performance hit happens because Divi’s Event Calendar add-on is looping through all 2228 events, and your snippet is filtering every single one via the_title / the_posts.

To avoid that overhead during the add-on’s get_eventSeries_data_name() routine, we can short-circuit your snippet when that function is running. That way, your “Teltház” title modification only runs where it’s actually needed (front-end views, loops, single templates), but not when TEC/Divi is bulk-processing events in the background.

defined( 'ABSPATH' ) || exit;

/**
 * Detect if we're inside the Divi Event Calendar add-on's event series function.
 */
function tec_telthaz_is_inside_eventseries_function() {
	foreach ( debug_backtrace( DEBUG_BACKTRACE_IGNORE_ARGS ) as $frame ) {
		if ( isset( $frame['function'] ) && 'get_eventSeries_data_name' === $frame['function'] ) {
			return true;
		}
	}
	return false;
}

/**
 * Append " - Teltház" to titles dynamically for single views (uses get_the_title or the_title).
 */
function tec_telthaz_append_title_suffix( $title, $post_id = null ) {
	// Bail early in admin, ajax, cron, REST, or during event series data processing
	if (
		is_admin() || wp_doing_ajax() || wp_doing_cron() ||
		( defined( 'REST_REQUEST' ) && REST_REQUEST ) ||
		tec_telthaz_is_inside_eventseries_function()
	) {
		return $title;
	}

	if ( empty( $post_id ) ) {
		return $title;
	}

	$post = get_post( $post_id );

	if ( ! $post || 'tribe_events' !== $post->post_type ) {
		return $title;
	}

	if ( has_tag( 'Teltház', $post ) ) {
		$suffix = ' - Teltház';
		if ( ! str_ends_with( $title, $suffix ) ) {
			$title .= $suffix;
		}
	}

	return esc_html( $title );
}
add_filter( 'the_title', 'tec_telthaz_append_title_suffix', 10, 2 );
add_filter( 'get_the_title', 'tec_telthaz_append_title_suffix', 10, 2 );

Please try updating your custom snippet in the WPCode plugin with the new version above. It detects when Divi’s Event Calendar add-on is bulk-processing events (get_eventSeries_data_name) and skips the “Teltház” modifications in that context. That way your titles still get the suffix on the front end, but we avoid looping through all 2228 events unnecessarily, which should improve performance significantly.

The topic ‘[Closed] Very s low website’ is closed to new replies.