Billy Lui

You can audit a live WordPress site's performance—fingerprinting its stack, measuring TTFB, payload, and Core Web Vitals—and then apply ranked fixes under a guarded write loop with per-change approval, rollback snapshots, and cache purges on the correct layer.

WordPress developers, site reliability engineers, and performance consultants investigating slow page loads, poor PageSpeed or Lighthouse scores, or caching, CDN, page-builder, and plugin performance issues on production WordPress sites.

Both skills require a shell, curl, and Python 3.9+, plus outbound network access to the target WordPress site. wp-perf-fix additionally needs the access level each change requires, such as wp-admin, WP-CLI, or a deploy path.

Yes. Both wp-perf-audit and wp-perf-fix are licensed under GPL-2.0-or-later, making them free to use, modify, and redistribute under the terms of that open-source license.

wp-perf-audit is read-only and safe against production. wp-perf-fix changes a live site but never runs unattended: it requires explicit per-change approval, captures a rollback snapshot first, purges the correct cache layer, and refuses changes the host prohibits.