Skip to main content

Debug Mode - Troubleshooting Page Creation Performance Issues

Experiencing slow page creation? Enable Debug Mode in Preview Mode to capture diagnostic data

Niklas avatar
Written by Niklas
Updated over a week ago

If you're experiencing slow page creation or encountering errors, LPagery's built-in Debug Mode can help identify the cause. This guide explains how to use it and share diagnostic information with our support team.

How to Enable Debug Mode

  1. Navigate to LPagery in your WordPress admin

  2. Click "Create Pages" to open the confirmation modal

  3. Enable Preview Mode - Toggle the "Preview Mode" switch (this creates only 1 page for testing)

  4. Enable Debug Mode - Once Preview Mode is on, a new "Debug Mode" option appears. Toggle it on.

  5. Click "Create Pages" to run the preview with debugging enabled

What Debug Mode Captures

When Debug Mode is enabled, LPagery collects:

  • Database Queries - All SQL queries executed during page creation, including execution time

  • Slow Hooks - The top 20 slowest WordPress hooks (actions/filters) that ran, showing which plugins may be causing delays

Downloading the Debug Log

After the preview page is created:

  1. You'll see the success screen with debug information

  1. Click the download icon (↓) next to the debug panel

  1. A .log file will be downloaded to your computer

Sending the Debug Log to Support

If you're experiencing issues, please send your debug log to:

Include in your email:

  • The downloaded debug log file

  • A brief description of the issue you're experiencing

  • Any error messages you've seen

Our support team will analyze the log to identify performance bottlenecks or conflicts with other plugins.

Understanding the Debug Output

Database Queries

Shows each SQL query with:

  • Query number and execution time (in milliseconds)

  • The full SQL statement

Slow Hooks

Shows WordPress hooks that took the most time:

  • Hook name (e.g., save_post, wp_insert_post)

  • The callback function that was executed

  • The source file/plugin

  • Execution time

Did this answer your question?