WordPress — Performance & Compatibility wp‑config.php Constants

This checklist defines wp‑config.php constants used to optimize WordPress performance and ensure compatibility with caching systems, page builders, and hosting environments.

These constants are applied early in the site lifecycle so downstream systems can detect and operate against an optimized baseline.

Checklist Objective

Apply a documented set of wp‑config.php constants that improve performance, reduce overhead, and prevent conflicts with plugins, builders, and caching layers.

Preconditions

• WordPress is installed and accessible
• wp‑config.php is writable
• No page builders or themes have been configured yet

Checklist Steps — Required Constants

1. Disable WordPress debugging in production.
   • define('WP_DEBUG', false); define('WP_DEBUG_LOG', false); define('WP_DEBUG_DISPLAY', false);
2. Disable automatic core updates if managed manually.
   • define('WP_AUTO_UPDATE_CORE', false);
3. Increase PHP memory limits where appropriate.
   • define('WP_MEMORY_LIMIT', '256M'); define('WP_MAX_MEMORY_LIMIT', '256M');
4. Disable WordPress cron in favor of system cron (if applicable).
   • define('DISABLE_WP_CRON', true);
5. Enable file system direct access (if supported).
   • define('FS_METHOD', 'direct');
6. Disable file editing from the admin dashboard.
   • define('DISALLOW_FILE_EDIT', true);

Checklist Steps — Validation

1. Save wp‑config.php and clear opcode cache if applicable
2. Confirm WordPress loads without errors
3. Verify performance tools and builders report healthy system status

Required Output

• wp‑config.php constants applied and documented
• WordPress operating in optimized, production‑safe mode
• Baseline compatible with caching and builder systems

Pause & Lock

Once approved, these constants become locked inputs for all subsequent setup and operational workflows.

Changes should only be made with documented justification.