How to Audit WordPress Performance

A good audit moves from symptoms to causes: field data, templates, server response, network waterfall, main-thread work and application behavior.

Start with field evidence

Use real-user data when available to identify which metrics, devices and page groups actually struggle.

Choose representative URLs

Audit at least one URL from each important template: homepage, article, landing page, product, checkout or membership area as relevant.

Inspect the request lifecycle

Separate origin delay, transfer size, render-blocking resources, media, third parties and long JavaScript tasks.

Inspect WordPress itself

For uncached or dynamic problems, look at database queries, plugin hooks, cron jobs, remote APIs and hosting resource limits.

Prioritize by impact and risk

Fix broad high-impact causes first, then retest. An audit should end with a ranked backlog, not a 100-item checklist.