Direct answer
A WordPress performance audit should include hosting checks, theme and plugin review, image weight, caching, CDN use, database health, script loading, Core Web Vitals, mobile experience, page templates, third-party scripts and the user journeys that matter commercially. Speed work should protect function, not just chase scores.
Why it matters
This answer helps site owners locate the real layer of a WordPress problem before applying a fix. WordPress issues often sit between hosting, DNS, themes, plugins, performance, accessibility, backups, schema, content and support responsibility.
What to check
- Is the issue caused by hosting, DNS, WordPress, theme, plugin, cache, content or custom code?
- Is there a current backup and rollback path?
- Does the fix reduce risk or only hide the symptom?
Common mistake
Installing another plugin or changing hosting before identifying the real failure layer and protecting the site with backup and rollback.
Caveats
Low caveat risk: suitable for publication from the available source pack, but still avoid pricing, guarantees, unsupported service promises or claims not visible in the linked public ecosystem.