Debugging and speed guides

Turn on WordPress debug mode with three lines in wp-config.php, find debug.log, and learn what to do with what it shows you.

Every line in debug.log has four parts: time, severity, message and file. Here is how to read them and trace an error to the plugin or theme behind…

By default anyone can open wp-content/debug.log in a browser, and it grows without limit. Here is how to check, protect, move and clear it.

After a PHP upgrade, debug.log fills with "Deprecated" lines. They are warnings about the future, not errors. Here is how to sort them without hiding real problems.

Find a WordPress plugin conflict without breaking the live site: capture the error first, test on a copy, narrow it down by halves, and send the author a…

Find the slow WordPress plugin by measuring what each one costs per request, in place of switching them off one at a time. Three methods, compared.

A slow WooCommerce checkout is usually order emails, payment and shipping API calls, or repeated queries, all run while the customer waits. How to find which one, and…

A slow WordPress dashboard is usually plugins calling outside servers, heavy autoloaded data, or admin-ajax.php requests repeating in the background. How to tell which, and fix it.

The "past-due actions found" notice means WordPress background jobs are not running on time. Why the queue stalls, how to check it safely, and how to get it…