Large Newspaper/TagDiv autoloaded options and possible impact on wp-adm

Hello,

Since August 1, I have noticed that the WordPress administration panel has been responding more slowly than usual.

I have reviewed several possible causes and found that WordPress is currently reporting a critical Site Health issue related to autoloaded options.

Current data reported by WordPress:

– 1,326 autoloaded options.
– Approximate size shown by Site Health: 2 MB.
– WordPress indicates that this volume could affect performance.

I also checked the options table directly in the database. The current autoloaded volume is approximately:

– autoload = yes: 1.54 MB
– autoload = auto: 0.12 MB
– autoload = on: 0.11 MB

Approximate total loaded automatically: 1.77 MB.

The total number also matches the 1,326 options reported by Site Health:

– yes: 1,131 options
– auto: 164 options
– on: 31 options
– total: 1,326 options

The largest individual options related to Newspaper/TagDiv are:

– td_011_settings: 820.24 KB — autoload yes
– td_011: 164.02 KB — autoload yes
– td_011_remote_cache: 35.64 KB — autoload yes
– td_011_log: 8.18 KB — autoload yes

The td_011_settings and td_011 options alone total approximately 984 KB. Therefore, these two options currently represent more than half of all the data WordPress loads automatically.

As an additional check, I also found a residual option from an old plugin:

– wpts_compat: 287.02 KB — autoload yes

Using WP-CLI, I confirmed that it belonged to a previous WPtouch installation:

– Original serialized class: WPtouchDefaultSettingsCompat
– WPtouch is no longer installed.
– There is no active or inactive WPtouch plugin or WPtouch folder on the server.

I did not delete the option. I only changed its autoload value from yes to off in a fully reversible way.

After making this change:

– The total autoloaded size decreased from approximately 2.05 MB to 1.77 MB.
– The autoload = yes group decreased from 1.82 MB to 1.54 MB.
– The administration panel appears to respond slightly faster, although I cannot confirm with complete certainty that the improvement is exclusively related to this change.
– Site Health still reports a critical issue related to autoloaded options.

I have also reviewed other possible causes of the slow administration panel.

1. Action Scheduler

The active Action Scheduler table appears to be working normally:

– No actions are currently in progress.
– Only three actions are pending, and all of them are scheduled for future dates.
– There have been no new failed actions since August 1.
– There is no active backlog of blocked or repeatedly failing jobs.

2. WP-Cron

The WordPress cron option is approximately 12.28 KB, so it does not appear unusually large.

3. WP Rocket RUCSS and background processes

There are periodic checks related to WP Rocket SaaS jobs, but the actions are completed successfully and do not accumulate. There does not appear to be a blocked queue that would independently explain the continued wp-admin slowdown.

Therefore, I cannot confirm that Newspaper options are the only cause of the problem, but they currently represent the main remaining portion of the autoloaded data.

I would like you to review the following questions specifically:

1. Is it normal for td_011_settings to exceed 820 KB?

2. Do td_011_settings and td_011 need to remain autoloaded on every WordPress request, including wp-admin requests?

3. Is it safe to change the autoload value of either of these options to off, or does Newspaper require them during almost every request?

4. Does Newspaper provide an official process for cleaning, rebuilding, or reducing td_011_settings and removing old configuration data that is no longer used?

5. Could td_011_settings contain accumulated data from Cloud Templates, the Theme Panel, blocks, advertisements, headers, footers, or old configurations that are no longer active?

6. Is there a diagnostic tool or recommended method to identify which internal settings are responsible for the 820 KB stored in td_011_settings?

7. Would it be possible to split this option into several smaller options and avoid autoloading data that is only required on specific screens?

8. Has there been any recent change in Newspaper or TagDiv Composer that could have increased the size of these options or the amount of processing performed inside wp-admin?

I have not modified or deleted any Newspaper-related option. Before changing their autoload values or altering their contents, I need confirmation from your team regarding which options must remain autoloaded and what official procedure you recommend to reduce their size without affecting the theme or the Cloud Templates.

Thank you.