WordPress page caching
Faster pages.
With built-in caching.
Airlift saves a ready-to-serve copy of your public pages. Visitors get that copy without waiting for WordPress to load your plugins, query the database and build the page again.
Get Airlift freePage caching is included in Free.
WooCommerce cart, checkout and account pages stay uncached.
What makes Airlift’s
page cache fast?
It saves the finished page—including Airlift’s optimizations—and serves it early in the request, before the full WordPress page build.
Less work on every cache hit.
The server reads a saved file instead of running the theme, plugins and database queries needed to build that page.
Optimized once. Reused on later visits.
The saved HTML already includes the image, CSS, font and JavaScript changes applied by Airlift. That work does not need to repeat for every cache hit.
Measure your server response time.
Compare the time to first byte before and after caching. Results depend on your host and page; the first request after clearing a copy still has to build it.
WooCommerce support
Cache the shop.
Keep checkout personal.
Public product and shop pages can be cached. Cart, checkout and account pages go to WordPress for a fresh response.
Uses your WooCommerce page settings.
Airlift identifies cart, checkout and account pages from your store configuration. A checkout with a different URL is not missed just because it is not called “checkout”.
Supports configured currency variants.
Supported WCML and Aelia configurations can keep separate cached copies for currency choices. Custom pricing, memberships and other personal content need appropriate rules and testing.
Compatibility
Does it support
your WordPress setup?
Airlift supports common WordPress sites, WooCommerce and several language and currency plugins. Not every request should be cached, and not every custom setup can be handled without additional rules.
Blogs, business sites and public pages
Cache public HTML pages when the request and response pass Airlift’s checks.
Logged-in users and private requests
Logged-in sessions, form posts, admin pages and supported authorization signals bypass the page cache.
Multilingual sites
Compatibility rules for supported Weglot, Polylang and GTranslate configurations keep language choices separate or wait for the plugin to establish the choice.
Memberships and custom personalization
Use the appropriate URL, cookie and request exclusions. Check each visitor type rather than assuming one public copy fits everyone.
Cache clearing
Edit your content.
Clear the old copy.
On paid plans, supported publishing events clear affected cached pages automatically. On Free, clear the cache manually after your changes.
Reading chair- Product page
- Shop and related listings
- Front page
Airlift saves it for later visitors.
Clear one page or the whole cache.
Manual controls include Purge This Page, Purge URLs and Purge All Cache. Clearing the cache removes saved copies—not your posts or products.
Clear related pages too.
Supported updates include relevant category and tag pages, the shop listing and front page. An old URL can also be cleared after a slug change.
Clearing and re-optimization are different.
Clearing gets new content into the next generated page. Re-optimization recalculates image, CSS, font and script treatments separately.
Other caches
Works with supported
host caches and Cloudflare.
Clearing Airlift’s cache is not enough if your host still has the old page. Airlift has integrations to clear supported host caches and a connected Cloudflare zone too.
Managed host and server caches
Integrations include Kinsta, WP Engine, SiteGround, Cloudways, LiteSpeed and others. Kinsta, LiteSpeed and Presslabs support per-URL purges; other integrations may clear the full host cache.
Cloudflare
When your Cloudflare zone is connected, Airlift can send cache-clearing requests there alongside its own purge.
Hosts that manage page caching themselves
On hosts such as Pressable and WordPress.com, Airlift can optimize the page without adding a second disk-based page cache.
Redis, object caches and other cache plugins
Page caching is different from object caching; Airlift does not provide Redis. Supported cache purges can flush the WordPress object cache. Do not assume every third-party page-cache plugin is integrated—avoid overlapping page-cache rules and verify how each cache is cleared.
How does Airlift check whether a purge worked?
Post-optimization purge checks can compare cached timestamps before and after to record whether delivery changed. This does not guarantee that every publishing event has immediately cleared every external cache.
Questions about page caching
Paid plans include automatic cache refresh for supported publish and edit events. Affected saved copies are cleared, and subsequent eligible requests generate fresh pages. Purges can be queued or limited, and other cache layers can affect delivery, so this is not an instant-update guarantee. On Free, refresh manually after publishing.
Recognized cart, checkout and account pages are excluded from page caching. Airlift resolves supported store pages from the store settings, rather than relying only on familiar URL names. Logged-in requests, form posts and supported authorization or exclusion signals also bypass the cache. Custom personalization still needs appropriate rules and testing.
Airlift has compatibility handling for supported configurations of Weglot, Polylang, GTranslate, WCML and Aelia. Rules can create separate saved copies for cookie values, require a choice cookie, or bypass caching. This is not automatic coverage for every language, currency or membership plugin. Check each important visitor context after setup.
Airlift has purge integrations for supported hosts and can clear a connected Cloudflare cache too. Some hosts support per-URL purges; others require a full host-cache purge. On hosts such as Pressable and WordPress.com, Airlift can optimize output without installing a second page-cache layer. Your host cache may already store optimized HTML.
No. Airlift’s page cache stores finished HTML on your site. Object caching speeds up work inside WordPress; page-cache hits avoid much of that build work altogether. Airlift’s asset CDN is a separate feature and does not make this an edge HTML cache.
A cleared or missing copy has to be generated again on a subsequent eligible request, then saved for later requests. The purge process does not crawl the whole site to warm every page. A cache hit is faster because that work has already been done.
No. Purging removes saved HTML so new content can be generated. Re-optimization recalculates eligible image, CSS, JavaScript and font treatments. Paid plans include scheduled re-optimization; Free supports manual runs within its allowance.
Free includes page caching and manual refresh. Automatic cache purge on supported post updates is included on paid plans. See the pricing page for current limits and the other optimization features.
Add page caching.
Serve WordPress pages faster.
Page caching is included in Free. Paid plans add automatic cache clearing after supported content updates.