GT Performance — WordPress Caching Plugin

GT Performance at a glance

Is GT Performance well maintained?

• Page cache: Pages are served from an advanced-cache.php drop-in before WordPress loads. Files are written atomically, so a visitor never gets a half-written…
• Unused CSS removal: Each page gets only the CSS it uses, built on your server. On one measured page, CSS dropped from 320 KB to 101 KB
• Cloudflare edge caching on the Free plan: One narrowly scoped Cache Rule and exact-URL purges. No Workers, no APO subscription
• Safe for stores: WooCommerce, Easy Digital Downloads, and FluentCart carts, checkouts, accounts, receipts, and session cookies are kept out of both the origin…
• Purges that follow your content: Updating a post also clears the listings, query loops, widgets, reusable blocks, and shop pages that showed it. Unrelated…
• Cache warming: Reads your sitemaps in resumable background batches, warms recently changed pages first, and stops at your cache size budget
• JavaScript defer and delay: Defer follows WordPress’s own script dependencies, so inline jQuery keeps working. Analytics plugin scripts are protected…
• Explain this page: Shows why any URL is or isn’t cached, what your server holds, and whether Cloudflare agrees
• Safe mode: One constant in wp-config.php switches off every optimization and cache read without touching a setting
• Multisite: Each site on a network keeps its own settings, bypass rules, and page cache, on subfolder and subdomain networks alike
• LiteSpeed’s own cache: On LiteSpeed and OpenLiteSpeed, the server keeps the pages GT Performance would cache and answers hits without starting PHP. Edits and…
• Compressed once: Every stored page keeps a gzip copy, plus Brotli when PHP has the extension, so no visit compresses it again