---
title: WP Performance
category: product
entity_type: skill
price: $15
canonical: https://forgehouse.ai/skills/wp-performance/
lang: en
hreflang_alt: https://forgehouse.ai/tr/skiller/wp-performance/
last_updated: 2026-06-20
---

# WP Performance

> Audit and optimize WordPress performance.

A systematic WordPress performance audit and optimization toolkit that diagnoses high TTFB, poor LCP and runaway query counts, then applies production-grade fixes. It hunts down N+1 query patterns, autoload bloat in wp_options, plugin overhead and unoptimized assets to hit concrete targets: TTFB under 200ms, LCP under 2.5s, page weight under 1MB.

## Use cases
- Sites loading slowly with 3+ second TTFB
- PageSpeed scores stuck below 60
- Core Web Vitals (LCP, INP, CLS) failing
- Slow WordPress admin after a plugin install
- wp_options autoload bloat suspicion
- N+1 query patterns dragging down templates

## Benefits
- Cold-start TTFB drops from ~800ms to ~200ms with persistent Redis object cache
- N+1 query storms collapse from 41 queries to 2 via eager meta loading
- Autoload bloat detection reclaims the ~30% of DB load wasted on every request
- Core Web Vitals fixes feed directly into Google ranking and lower bounce rate

## What’s included
- N+1 detection and the eager-loading fix (no_found_rows, update_post_meta_cache)
- Redis object cache config plus transient API caching strategy with stampede prevention
- Autoload bloat detection queries and safe cleanup of expired transients
- WP-CLI query profiling (wp profile stage/hook) to find the slow 20%
- Image optimization (WebP, srcset, native lazy load) and critical-CSS/defer patterns
- Verification checklist with measurable targets and curl/Lighthouse commands

## Who it’s for
Developers and agencies who maintain WordPress sites and need measurable speed gains tied to Core Web Vitals and SEO.

## How it runs
A slow WordPress site usually has two or three plugins eating most of its TTFB. This skill measures first, names the offenders, then fixes queries, autoload bloat and caching with a number checked after every move.
1. Measures before touching anything: Query Monitor counts queries per page (target under 10 on the homepage), curl times TTFB, and wp profile stage/hook with spotlight surfaces the top 10 slowest hooks, where typically 2 or 3 plugins consume 60 percent of TTFB.
2. Audits autoload bloat with SQL: sums all autoload='yes' rows in wp_options (over 800KB is critical), lists the top 20 offenders, then flips expired transients and oversized records to autoload='no' in small batches with a TTFB check after each batch.
3. Kills N+1 query patterns: get_posts loops with per-post get_post_meta are rewritten with update_post_meta_cache and no_found_rows, collapsing 41 queries into 2.
4. Installs the cache layer: Redis persistent object cache configured in wp-config with a site prefix, plus Transient API caching with 5-minute TTL and stampede protection, dropping cold-start TTFB from around 800ms to around 200ms.
5. Optimizes asset delivery: critical CSS inlined in head under 14KB, remaining CSS preloaded async, scripts deferred, images converted to WebP with srcset and lazy loading, explicitly never lazy-loading the above-the-fold hero because that breaks LCP.
6. Closes with the verification checklist: queries under 10, TTFB under 200ms, LCP under 2.5s, INP under 200ms, CLS under 0.1, autoload under 800KB, Redis hit rate over 80 percent, each one measured, not assumed.

## FAQ
### My site is on cheap shared hosting, will these optimizations still help?
Most of the toolkit targets things hosting cannot fix for you: N+1 query patterns, wp_options autoload bloat, unoptimized images and render-blocking assets. The one exception is the persistent Redis object cache, which needs Redis available on the server; without it you still get the query fixes, transient cleanup and asset work.

### How does it actually find what is slow, instead of just guessing at plugins?
It profiles before it touches anything: WP-CLI query profiling (wp profile stage/hook) isolates the slow 20%, autoload detection queries measure wp_options weight, and the N+1 hunt counts real query storms per template. Fixes then target measured bottlenecks against concrete numbers like TTFB under 200ms and LCP under 2.5s.

### Will it rewrite my theme or replace my page builder to get the speed gains?
No. It works at the query, cache and asset-delivery layer: eager meta loading, Redis object cache, transient strategy, WebP/srcset/lazy-load and critical-CSS patterns. A fundamentally heavy theme or builder stays your call; the audit will show its cost, but the skill does not swap it out.

## Price
$15, one-time, no subscription. VAT included.

Related guide: [AI code review and developer workflow](https://forgehouse.ai/guides/ai-code-review/)