FlyWP Cache.
Your questions answered.

No. Every FlyWP Cache Early Bird plan is a one-time payment. There is no recurring subscription and nothing to cancel.

Yes. The prices shown on the FlyWP Cache sales page already include the 50% Early Bird discount.

Log in to My Account for your purchases, available downloads and licenses — all in one place.

Yes — 30 days, full refund, no conditions beyond the Refund Policy. Read it for the details.

FlyWP Cache combines page caching and preloading with CSS, JavaScript, image and font optimization, database cleanup and per-page control over which assets load — one plugin instead of a stack of five.

Download the plugin from your account, install and activate it in WordPress, then activate your license in the plugin’s License section. The setup guide in the documentation walks you through the rest.

No. Remove Unused CSS uses the FlyWP Cache license activated on your website. A valid, active license is all the processing service needs.

Most features run in WordPress. Remove Unused CSS uses the FlyWP Cache processing service. WebP and AVIF generation depend on your server's image support.

Deactivate the license on the previous website before activating it on the new one. Your plan's website activation limit still applies.

Compatibility depends on your setup and on which optimizations you enable. Start with the setup guide, test changes on staging first, and check your important pages, forms and checkout flows.

FlyWP Cache does not write logged-in responses to the public page cache, and Remove Unused CSS normally skips logged-in visits. To check the visitor experience, open the page in a private browser window while logged out.

Yes. You can exclude URL patterns, cookies and user agents in the cache exclusion settings. URL exclusions support wildcard patterns. Use exclusions for personalized or dynamic pages that should not be served from the public page cache.

The plugin excludes requests with WooCommerce cart and session cookies from page caching and clears affected product caches when product or stock data changes. These safeguards do not replace testing: check your cart, checkout and account flows with your theme and extensions.

FlyWP Cache includes automatic cache purging for published content changes, WooCommerce product and stock updates, and comments or reviews. Certain site-wide changes, such as menu updates or switching themes, trigger a full purge.

Cache preloading warms eligible URLs from your sitemap in the background. Link preloading anticipates navigation using the selected strategy, such as hovering over a link or pressing it. Both have their own settings and exclusions.

Yes. The mobile cache option creates separate cache files for detected mobile requests. It does not create a mobile design; your theme or page builder still controls the responsive layout.

CSS processing runs in the background for each eligible URL. While a job is pending or processing, FlyWP Cache serves the original HTML and styles. Check the license and dashboard status, allow processing to finish, then inspect the page while logged out.

If there is no usable generated CSS, FlyWP Cache keeps the original HTML and styles instead of applying an incomplete result. The queue includes retry handling. Check the dashboard status and your license or connection if processing does not recover.

Yes. The Remove Unused CSS settings include a CSS Safelist. Add the selectors you need to preserve, then clear the affected used CSS so it can be regenerated. Test interactive states such as open menus, popups and form validation after regeneration.

Use the separate exclusions for JavaScript Delay and Defer to keep affected scripts out of that optimization. Change one setting at a time, clear the relevant cache and test the feature again. If needed, turn off the affected optimization while identifying the script.

Yes. Script Manager includes a testing mode that applies script-disabling rules only to logged-in administrators. Test the affected pages and interactions before turning testing mode off and applying the rules to visitors.

Each format must be enabled and supported by your server's image libraries. Background generation also depends on scheduled WordPress tasks running. FlyWP Cache discards generated variants that are not smaller than the source, so not every image will keep every format.

WebP and AVIF generation creates additional variants, but the plugin also contains original-image optimization routines that can rewrite source files when enabled. Keep a separate backup before bulk optimization; variant generation and original-file optimization are different operations.

Yes. Lazy-load settings include keyword exclusions and an option to skip the first images. Use these controls for immediately visible images, then check the result on your actual pages.

Yes. Enable the Cloudflare integration and configure a suitable API token and Zone ID. The integration connects Cloudflare purging to FlyWP Cache's cache-clearing workflow. It requires valid Cloudflare credentials in addition to your FlyWP Cache license.

The integration purges a configured FastCGI cache directory and depends on your server's cache setup and filesystem permissions. It does not configure NGINX for you. Check the path and access with your hosting provider before enabling it.

Yes. Export your settings as JSON and import the file on the other website. Stored credentials are excluded from the settings export, and imports preserve the target website's existing stored credentials. Activate the appropriate license separately on the destination site.

Cleanup permanently removes the selected data, such as revisions, auto-drafts, trashed content, spam comments and expired transients. Back up your database first. In the current implementation, enabling revision cleanup removes all saved revisions rather than keeping a chosen number.