Hello Harry,
if your admin screen has to load 130 custom fields that need to be looked up and parsed, it will slow down the edit screen because of the heavy load compared to the usual posts.
If you really need to edit this large amount of custom fields for one post type you will have to adjust your server settings to meet the larger amount of queries when editing the custom post.
Generally speaking there are some factors that influence the page load in the admin screens, like the memory of your WP installation and the php settings. If you are using posts with a heavy load you will need a good amount of memory and a generous time limit set in php to manage the load.
So please try this in the first place:
- Increase the memory assigned to your WordPress to at least 256 MB in your wp-config.php file.
- Please try to maximize also your values for upload_max_filesize and post_max_size in your wp-config.php file
- Also the amount of max input variables may be need to be set higher, as you will be setting and reading this amount of fields. Try to increase the max_input_vars at least to 6000 in your php.ini.
- Also increase the php memory limit as well as the php execution time limit in your server settings (php.ini).
- If you are using any cache plugin like W3 Total Cache try to disable the object cache at least for admin users as this sometimes can slow down the admin screen too.
- Please check also if you are getting problems with the admin ajax request. In that case it may help to slow down the WordPress heartbeat API. There are plugins like the WordPress Heartbeat Control plugin where you can set the frequency lower and choose to disable it if you are the only one updating the site.
In case this does not really help you out when editing, I would need some more information about your site and server settings to see if and where this loading time could be optimized specifically for your site.
Please provide some more detailed info about your site to check this.
I am enabling the debug info box and the private reply box for your next reply.
Kind regards,
Cristina
