How to Debug a Slow WordPress Website

1. Identify the Bottleneck: The Waterfall Analysis

Before changing settings, you must know where the delay happens. Use the Network Tab in Chrome DevTools or GTmetrix.

• High TTFB (Time to First Byte): If your TTFB is over 500ms, the issue is server-side (slow PHP, no object cache, or poor hosting).
• Large Page Weight: If the TTFB is fast but the page takes 10 seconds to load, your images are unoptimized or you have too many third-party scripts (ads, tracking pixels).
• DOM Content Loaded: If this is high, your JavaScript is “render-blocking” the browser.

2. Profile the Application with Query Monitor

The Query Monitor plugin is the most essential tool for debugging WordPress. It shows you exactly what is happening during the page generation.

• Slow Queries: It highlights database queries that take too long to execute.
• Duplicate Queries: It finds plugins that are hitting the database 50 times for the same piece of data.
• Component Breakdown: It shows you exactly which plugin is adding the most time to the “Page Generation Time.”

3. Check for PHP-FPM and Script Bottlenecks

If the server is hanging, your PHP processes might be hitting a wall.

• The Slow Log: Enable the PHP-FPM Slow Log on your server. It records the stack trace of any script that takes longer than a set threshold (e.g., 3 seconds).
• External API Calls: Many sites slow down because a plugin is waiting for a response from an external API (like a social media feed or a license check). Query Monitor will flag these under “HTTP Requests.”

4. Database “Cruft” and Indexing

As a database grows, queries that were fast on a fresh install become slow.

• The Autoload Audit: Check your wp_options table for high “autoload” values. If WordPress is loading 2MB of data on every single click, the site will feel sluggish.
• Orphaned Transients: Millions of expired transients can bloat the database. Clear them and implement Redis or Memcached so they stay in RAM instead of the disk.

5. Frontend: The “Critical Path” Audit

If the backend is fast but the site feels slow to the user:

• Unused CSS/JS: Use the “Coverage” tab in DevTools to see how much code is being loaded but not used.
• LCP (Largest Contentful Paint): Check if your “Hero Image” is being lazy-loaded. You should never lazy-load the image “above the fold.”