19 articles
Finding what makes WordPress and WooCommerce slow: TTFB, Core Web Vitals, the database and caching.
Server response time, the caching layers, the database, the admin and the Core Web Vitals visitors feel. The guides go from the first measurement to the specific fixes; the free tools run the first checks in your browser.
Not covered yet: hosting comparisons with measured tests and media offloading for large WordPress libraries.
Message
Ask me about your site
Tell me what is wrong or what you need built. I reply by email.
Performance8 min read
PageSpeed good, Core Web Vitals failed: read the right data
If PageSpeed looks good but Core Web Vitals failed, check the data source before you change WordPress. The green Lighthouse score and the failed Core Web Vitals assessment can both be correct because they measure different populations, time periods and conditions.
Performance8 min read
Fix INP in WordPress by finding the slow interaction
To fix INP in WordPress, start by reproducing the exact tap or key interaction that feels slow, then record it in Chrome DevTools and split its delay into input, processing, and presentation.
Performance10 min read
WooCommerce checkout slow: diagnose the request that blocks payment
When your WooCommerce checkout is slow, start with the single browser request that begins when the delay begins. Record that request's timing, then match it to a server trace so you can separate browser delay from WooCommerce, shipping, tax, gateway, database, or server work.
Performance7 min read
WooCommerce Action Scheduler: clear a backlog and keep it healthy
A WooCommerce Action Scheduler backlog means scheduled background work is arriving faster than it is being processed, or processing has stopped. Start by grouping pending and failed actions by hook, fix the hook or cron problem, then drain the queue with WP-CLI instead of deleting unknown jobs.
Performance9 min read
WooCommerce cart fragments: what they cost and when to remove them
WooCommerce cart fragments keep a legacy mini cart synchronized after cart changes, but the refresh request reaches PHP and cannot use a normal full-page cache.
Performance7 min read
WooCommerce HPOS: migrate to High-Performance Order Storage safely
WooCommerce HPOS moves core order data out of WordPress post storage into dedicated WooCommerce tables. Migrate safely by checking extension compatibility, synchronizing both data stores, verifying them, switching HPOS to authoritative, then testing every order workflow before you disable synchronization.
Performance6 min read
Why a cache purge can overload WordPress and how to stop it
A WordPress cache stampede happens when many requests lose the same cached data at once and all try to rebuild it. The fix is to limit rebuilds with a shared lock, keep stale data available during refresh, and spread expiries so misses do not arrive as one burst.
Performance8 min read
WordPress CDN caching: cache full pages safely at the edge
WordPress CDN caching is safe when the CDN stores only anonymous, public HTML and bypasses requests that can vary by user, session, cart, preview, or admin state. Cache static assets broadly, cache full pages selectively, purge changed URLs, and verify the response headers before trusting the policy in production.
Performance7 min read
WordPress LCP image optimization: make the largest image load first
A slow WordPress LCP image usually needs three things: early discovery, high fetch priority, and a file sized for the space it occupies. Find the actual LCP element first, then remove accidental lazy loading, fix responsive image markup, preload late-discovered backgrounds, and retest.