WordPress Site Health reports large WPML config files

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
-	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	9:00 – 13:00	-
-	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	14:00 – 18:00	-

Supporter timezone: America/Los_Angeles (GMT-07:00)

This topic contains 1 reply, has 0 voices.

Last updated by Bobby 2 weeks, 5 days ago.

Assisted by: Bobby.

Author	Posts
October 9, 2025 at 6:55 am #17469539
simpleT	Background of the issue: We have critical issues reported by Site Health related to autoloaded options on our WordPress site hidden link. In particular, two database entries tied to WPML are considerably large: icl_sitepress_settings (~200 KB) and wp_installer_options (~130 KB). We are aware of other forum topics and know that version 4.9 is expected to address this issue. Symptoms: Site Health reports large WPML config files, specifically icl_sitepress_settings and wp_installer_options. Questions: What specifically are you fixing in version 4.9, and how are you addressing the issue of these large two files? Is there anything that we can do on our end in the meantime, such as setting wp_installer_options to 'auto' or 'no/off'? Can you confirm that setting wp_installer_options to 'auto' or 'no/off' is an appropriate course of action? Are there any other effective solutions beyond the small gains from WPML -> Support -> Troubleshooting options?
October 9, 2025 at 5:10 pm #17472231
Bobby WPML Supporter since 04/2015 Languages: English (English ) Timezone: America/Los_Angeles (GMT-07:00)	Hi there, It sounds like you are aware of the current issues regarding the performance our team is working. If you have not yet reviewed my latest reply in this thread please take a look: https://wpml.org/forums/topic/wp_installer_settingsis-autoload-and-large/page/4/ At the moment unfortunately there is no other workarounds I can provide that would have a significant effect. There are many subtasks that are being tackled at the same time to resolve this and not just one task in terms of development. Unfortunately it is not a procedure I could easily share for somebody to follow and per say implement on their own so you wouldnt have to wait until the full release. I can however share that our tests are showing positive results.

The topic ‘[Closed] WordPress Site Health reports large WPML config files’ is closed to new replies.