diagnostic-db-autoload

WordPress autoload bloat slows down every page request by loading excessive data from the wp_options table. When total autoloaded data exceeds healthy thresholds under 900KB, it becomes critical over 2MB, significantly degrading site performance and increasing response times.

To find which plugins cause wp_options autoload bloat, analyze the database to list individual autoloaded options exceeding 10KB. This process attributes each large option to specific plugins or WordPress Core, identifying the exact contributors to your database overhead.

Yes, you need WP-CLI to check the WordPress database options table size. This analysis requires WP-CLI for all checks, dynamically retrieving table prefixes and routing database access through WP_CLI_PREFIX to measure autoloaded data accurately.

The maximum recommended size for autoloaded data in wp_options is under 900KB for healthy performance. Autoloaded data becomes critical and causes significant slowdowns when it exceeds 2MB, requiring immediate optimization to reduce overhead.

You can measure the total size of autoloaded options in WordPress by running a database analysis through WP-CLI. This calculates the total autoloaded data size, flags options over 10KB, and identifies specific plugins contributing to the overhead.

Yes, you can identify specific large options in wp_options without manual SQL queries by using an automated analysis tool. It lists all autoloaded options over 10KB and attributes them to specific plugins or WordPress Core automatically.