Skip to main content

GT Performance

GT Performance beta-4: your cache clears itself when you publish

Two beta drops since beta-2, and the one you'll notice first landed in beta-4. Publishing or updating a post now clears the right caches on its own. No more reaching for the purge button after every edit.

You choose how aggressive it gets. Four modes:

  • Related pages. The post, the homepage, its post-type archive, and now the author and public taxonomy archives too. This is the one most sites want.
  • Post only. Just the URL you touched.
  • Page and edge. Full purge, origin and Cloudflare.
  • Off. You handle purging yourself.

Related-pages mode got wider in beta-4 for a reason. Author archives and public taxonomy archives weren't being cleared before, so a fresh post could sit missing from its own category page until the cache aged out.

I also fixed something that quietly undercut the narrower modes. WordPress revision cleanup was purging the homepage through the real-content deletion hook, which meant "post only" and "off" weren't actually staying in their lane. They are now.

beta-3 was analytics compatibility. GT Performance now detects and excludes JavaScript for Independent Analytics, Burst Statistics, Koko Analytics, Matomo, WP Statistics, Site Kit by Google, MonsterInsights, ExactMetrics, and PixelYourSite. If your pageview counts went light after you switched optimization on, that was this, and it's fixed.

Update from your dashboard.

What I want from you: tell me which publishing policy you settled on, and whether related-page purge is missing anything on your setup. Odd post types and heavily filtered archives are where I expect the gaps to be, and I'd rather hear about them here than find them in three weeks.

If something breaks, post the site type and your cache mode and I'll dig in.