LiteSpeed Cache
Free server-level cache and optimisation suite from LiteSpeed Technologies; full-page caching needs a LiteSpeed web server or QUIC.cloud CDN.
Premium all-in-one WordPress speed plugin: page cache, used-CSS generation, delayed JS, image optimisation, Redis and an optional FlyingCDN add-on.
FlyingPress is a premium-only WordPress performance plugin from FlyingWeb LLC that combines a disk-based page cache with a full set of front-end optimisations aimed squarely at Core Web Vitals. There is no free version on WordPress.org; instead every plan unlocks all features and starts with a 14-day free trial.
FlyingPress generates static HTML pages and serves them directly from the web server, preloading the cache automatically and purging only the related pages when content changes. On top of that it uses a cloud-based optimiser to extract the CSS each page actually uses, inline it, and load the rest of the stylesheets during idle time. JavaScript can be deferred, delayed until user interaction, or delayed selectively for third-party scripts, and external CSS/JS can be self-hosted.
Licences run from $59 a year for one site to $279 a year for unlimited sites. FlyingCDN is a separate, paid add-on built on Cloudflare Enterprise that adds edge HTML caching and image delivery for $10 per domain per month including 100GB, with extra bandwidth billed per 100GB.
There is no free tier to keep long term, unused-CSS processing relies on the vendor’s cloud service, browser-cache headers are only set automatically on Apache and LiteSpeed, and it deliberately avoids combining CSS/JS files. Multisite works, but the plugin must be activated per subsite rather than network-wide.
Who should pick it: freelancers, agencies and site owners who want one paid plugin to handle caching and most Core Web Vitals fixes with sensible defaults, and who are comfortable with an annual subscription.
Best for: Site owners and agencies who want a single paid plugin for caching plus Core Web Vitals optimisation with minimal tuning.
FlyingPress is a strong all-rounder that bundles caching, CSS/JS optimisation, image compression and Redis support into every plan. The lack of a free tier and the separately billed CDN are the main trade-offs.
What FlyingPress highlights on its own website, split by version.
24 of 25 features we track in Caching & Speed, feature score 97/100
Serves pre-built HTML pages.
Generates static HTML pages served directly by the web server.
Sets cache headers for static files.
Sets long cache headers for static files on Apache/LiteSpeed; Nginx manual.
Builds the cache before visitors arrive.
Preloads pages automatically and re-preloads related URLs after edits.
Redis or Memcached object caching.
Built-in Redis object cache; needs a Redis server and phpredis extension.
Different cache for mobile devices.
Optional separate cache and optimisations for mobile visitors.
Excludes cart, checkout and account pages automatically.
Cart, checkout and My Account are excluded from cache automatically.
Page caching works on Apache, Nginx and LiteSpeed alike.
Supports Apache, Nginx, LiteSpeed and OpenLiteSpeed on shared, VPS or managed hosts.
Works on WordPress multisite networks.
Multisite supported; activate per subsite, one licence covers all.
Strips whitespace from CSS and JavaScript.
Minifies CSS and JavaScript on the server or via FlyingCDN.
Merges CSS/JS files.
Does not combine CSS/JS files; only Google Fonts requests are combined.
Loads scripts after the page renders or on interaction.
Defers scripts and can delay all or selected JS until interaction.
Generates only the CSS each page uses.
Cloud optimiser extracts used CSS and loads the rest on idle.
Inlines above-the-fold CSS.
Inlines the generated used CSS in the page head for first render.
Self-hosts or preloads web fonts.
Self-hosts Google Fonts, preloads fonts and can show system fonts first.
Preload fonts, images or links and prefetch DNS.
Preloads critical images/fonts with priority hints and prefetches links on hover.
Defers off-screen images and iframes.
Lazy loads images, videos, iframes and HTML elements.
Compresses uploaded images.
Built-in lossy or lossless image compression (added in v5.3).
Serves next-gen image formats.
Converts images to WebP or AVIF, or keeps the original format.
Rewrites asset URLs to a CDN.
CDN URL field can point assets at third-party CDNs such as Bunny.
Purges or configures Cloudflare.
Cloudflare full-page caching without APO; also purges APO when used.
Replace YouTube and Vimeo embeds with a lightweight preview.
Replaces YouTube embeds with lightweight preview images.
A CDN is part of the product or plan, not just URL rewriting.
Paid FlyingCDN add-on: $10/domain/month incl. 100GB, Cloudflare Enterprise.
Removes revisions, transients and spam.
Cleans and optimises database tables, with scheduled automation.
Limits the WordPress Heartbeat API.
Bloat setting throttles the Heartbeat API to once every 60 seconds.
Clear or warm the cache from the command line.
WP-CLI commands to purge and preload the cache.
1 site
14-day free trial; card charged only if you continue.
3 sites
All features; 14-day free trial.
25 sites
All features; 14-day free trial.
Unlimited
All features; FlyingCDN add-on billed separately at $10/domain/month.
Prices are list prices from the vendor's site, checked 14 Oct 2026. Many vendors discount the first year.
Free installs from WordPress.org, the vendor's own claim, and our estimate of paid installs.
No free version on WordPress.org.
Paying customers claimed by the vendor. source
Our estimate, see method below.
How we estimated this: Website scans by WPoptic find the paid plugin (folder flying-press) on 25,991 live sites; the scans reach roughly 38% of WordPress sites, so each site found stands for about 2.6, giving 68K. 10,000 paying customers or sales over 6 years; assuming 40% still use it and 1.3 sites per licence gives 5.2K. Combining these (weighted average) gives about 24K. Likely range: 16K to 36K. This counts sites running the paid version, including sites whose licence has lapsed. Estimates are rough and based on public figures as of 14 Oct 2026.
| Paying customers claimed | 10,000+ (source, 5 Oct 2026) Homepage says 10,000+ freelancers, agencies and companies use FlyingPress. |
|---|---|
| Refund policy | 14-day free trial (no refunds after) (source, 5 Oct 2026) |
| Trustpilot rating | 4.7 (source, 5 Oct 2026) As displayed on the vendor homepage (300+ Trustpilot reviews). |
Free server-level cache and optimisation suite from LiteSpeed Technologies; full-page caching needs a LiteSpeed web server or QUIC.cloud CDN.
Free WordPress cache plugin with static page caching, Redis and Memcached object cache, database cleanup and a built-in MCP server.
Premium all-in-one caching and performance plugin for WordPress that applies page caching, file optimisation and lazy loading as soon as it is…
Cloud-based speed optimisation service with caching, critical CSS, image optimisation and a built-in Cloudflare-powered CDN, billed by pageviews.
WPMU DEV's performance plugin with page, browser and Gravatar caching, asset optimisation, Cloudflare tools and Redis; Pro adds critical CSS and a…
Host-agnostic caching framework with page, object, database and browser caching, minify and CDN tools; BoldGrid sells a Pro upgrade.
No. FlyingPress is a premium plugin. Paid plans start at $59/yr.
We estimate around 24K active installs.
Yes: included. Generates static HTML pages served directly by the web server.
Yes: included. Defers scripts and can delay all or selected JS until interaction.
Yes: included. Cloud optimiser extracts used CSS and loads the rest on idle.
No. FlyingPress is premium-only, but every plan starts with a 14-day free trial and your card is only charged if you keep it after the trial.
No. FlyingCDN is an optional add-on for FlyingPress customers, billed at $10 per domain per month with 100GB of bandwidth, plus $5 per extra 100GB.
Yes. The vendor lists Apache, Nginx, LiteSpeed and OpenLiteSpeed as supported. On Nginx you may need to add browser-cache rules yourself.
Yes. One licence covers all subsites, but you should activate the plugin on each subsite individually rather than network-wide.
Last updated 5 Oct 2026. Spotted something wrong? Suggest an edit.