The four layers of WordPress performance: a field guide

Every WordPress site has four places where performance can break. Knowing which one is failing is half the fix.

Layer 1 — Frontend

What gets shipped to the browser, and how the browser deals with it.

• Render-blocking CSS and JS in the head
• Oversized hero images, no loading="lazy", no srcset
• Long task chains during hydration on Gutenberg-heavy pages
• Layout shifts that show up as low CLS scores

Tells: the page feels slow even when TTFB is fast; Lighthouse complains about LCP and CLS.

Layer 2 — Backend

What WordPress and its plugins do per request before HTML hits the wire.

• Plugins that hook into init or wp_loaded and run expensive queries
• Cron jobs that fire on page loads (wp-cron.php instead of system cron)
• Calls to remote APIs without caching
• Hooks firing dozens of times per request

Tells: TTFB sits at 800ms-2s on uncached pages; admin pages feel sluggish; New Relic-style traces show slow PHP.

Layer 3 — Database

What happens inside MySQL.

• Autoloaded options table over 1MB (or worse, 10MB+)
• Transients that never expire and pile up
• wp_postmeta over a few million rows, often from leftover plugins
• Missing indexes on custom tables

Tells: even cached lookups feel slow; backups take ages; a SELECT * FROM wp_options WHERE autoload = 'yes' returns more data than the rest of your homepage.

Layer 4 — Infrastructure

Below WordPress. The host, the network, the geography.

• Slow PHP versions, low memory_limit, low max_execution_time
• Servers in a different region than your audience
• No HTTP/2 or HTTP/3, no Brotli, no CDN
• Object cache disabled or misconfigured

Tells: TTFB is bad even on a static page; visitors from one region report consistent slowness.

Why the order matters

If you fix the wrong layer, you spend effort and the score doesn't move. We see this constantly. A site with a 12MB autoload table won't feel meaningfully faster from image optimization, even though the image work was real.

That's why every BoltAudit report leads with the bottleneck layer — the one that, fixed, will move the score the most. Everything else stays in the report, ranked, but you know where to start.