Performance

Cloudflare's March and April 2026 cache changes turned origin-header cleanup from an app-team dependency into a staged edge-ops job. The practical opportunity now is to trace BYPASS and DYNAMIC responses, fix response headers at the edge, and improve cache behavior without waiting on origin releases.

WordPress 6.6 and 6.7 made autoload behavior easier to see and stricter in places, but the Site Health warning is still only an alert. The real performance work is figuring out which options should be autoloaded, correcting how they are written, and removing stale data without breaking anything.

URL parameters usually get added for sensible reasons, then quietly become an expensive operational mess. This piece explains why filters, tracking tags, and search parameters create duplicate URLs, wasted crawling, fragmented caching, and harder reporting, and where Greg Nowak can help fix it.