diagnostic-architecture

WordPress architecture diagnostics identify slow load causes by detecting custom post types used as data stores, excessive callbacks on init hooks, and missing persistent object cache. It pinpoints CPT misuse and expensive init operations.

To detect CPT misuse in WordPress, run a diagnostic review that identifies dead custom post types, low-entry CPTs, and data-store abuse via row count gating. CPT checks require WP-CLI to accurately query and analyze custom post type entries.

Yes, WordPress hook abuse and priority conflict checks use static analysis on synced files, requiring no live environment. This detects excessive callbacks, expensive init hooks, and plugin priority conflicts without executing code.

WordPress caching anti-patterns include missing persistent object cache, permanent transients that never expire, and uncached direct database queries. Static analysis flags these caching issues to prevent performance degradation and scalability problems.

WP-CLI is required for CPT checks to identify dead custom post types and data-store abuse via row count gating. Hook and caching anti-pattern checks use static analysis on synced files, so WP-CLI is not needed for those specific reviews.