If you want a FlyingPress alternative you pay for once, with most of the work on your own server, Novra Cache is worth testing. It combines page caching, image processing on your server and a Script Manager for each page. Keep FlyingPress if its cloud features are the reason your setup works well.
We make Novra Cache. This guide uses FlyingPress’s public website and documentation, checked on 6 October 2026. It is not a speed benchmark or a hands-on compatibility test.
When switching makes sense
A page cache saves ready-made copies of your pages, so WordPress repeats less work for each visitor. Both plugins do that. The real differences are where the rest of the work happens and how you pay. You can see Novra Cache’s features and plans on its product page.
- You want to pay once. Every Novra Cache plan is a one-time payment with updates for the life of the license. FlyingPress uses a yearly license that renews automatically.
- You want less dependence on a cloud service. FlyingPress’s license documentation says: “Most optimizations rely on cloud processing and will not work if your license expires or renewal fails.” In Novra Cache, ready-made pages, code changes, images and fonts run on your server. Only Remove Unused CSS uses our service.
- You want to switch off plugin files page by page. Novra Cache has a built-in Script Manager. FlyingPress’s documentation does not describe one.
Staying with FlyingPress is reasonable when you rely on what it does better. It can track Core Web Vitals, Google’s page experience measurements, from your real visitors. It analyses each page in its cloud and can cache full pages in Cloudflare. It also offers its own CDN and a cache for logged-in users. If your setup works and none of the points above bothers you, a switch adds testing work without a clear gain.
Coming from WP Rocket instead? See the WP Rocket alternative guide.
Coming from WP Super Cache instead? See the WP Super Cache alternative guide.
Novra Cache and FlyingPress: the practical differences
Both plugins cover the same basics: ready-made pages, smaller code, delayed JavaScript and lazy loading, which loads images only as visitors scroll. These differences matter more when you decide:
Where the work happens. Novra Cache builds pages, trims code and processes images on your own server. Remove Unused CSS keeps only the design code a page needs. In Novra Cache, it uses our service and needs an active license. FlyingPress also needs an active license for it, and it runs most of its optimizations in its cloud.
How images are handled. Novra Cache creates WebP and AVIF, two modern image formats, on your server. It also slims down JPEG, PNG and GIF files. Your original images and links stay as they are, with a fallback for older browsers. FlyingPress’s image optimization runs on its cloud servers and handles JPG and PNG only. It uses one format per site and rewrites image URLs in your content.
Control over plugin files. Novra Cache’s Script Manager turns off scripts and style files where a page does not need them. Rules can target a page, a post type, a URL pattern, a device or login status. A testing mode shows the changes to administrators first.
What FlyingPress does more of. It measures real visitors and delays drawing off-screen sections until visitors scroll near them. It includes Redis object caching and offers WP-CLI commands and automatic cache clearing for several hosts. Novra sells object caching as a separate plugin, Novra Object Cache.
See the full Novra Cache vs FlyingPress comparison for the feature table and every area where FlyingPress is stronger.
Compare the license terms, not just the first price
These were the displayed entry prices on 6 October 2026:
- Novra Cache: $79 once for 1 website.
- FlyingPress: $59 per year for 1 website.
FlyingPress costs less in the first year for one site. Novra Cache’s appeal is that there is nothing to renew, not a lower day-one bill. Both vendors offer plans for more websites. Check the FlyingPress pricing page and the Novra Cache plans for the number of sites you need, including taxes and current checkout terms.
FlyingPress’s license renewal documentation says the license renews automatically every year. Manual or early renewals are not supported. FlyingPress offers a 14-day free trial instead of refunds. Novra Cache comes with a 30-day money-back guarantee.
The three-year cost comparison shows the totals from one website up to unlimited websites, with the same number of sites on both sides.
Check your host and your site first
A price comparison cannot tell you whether your hosting suits Novra Cache. Before you test it, confirm these basics:
- Supported software: Novra Cache needs WordPress 6.2 or later and PHP 8.1 or later. FlyingPress also runs on PHP 7.4, so check your PHP version before you plan a switch.
- Working cache storage: the server must let Novra Cache write its cached files. Its health panel checks the cache folder, the cache file and the WordPress cache setting.
- Image formats: Novra Cache creates WebP and AVIF with your server’s image tools. Which formats you get depends on your server.
- Cloudflare and host caches: Novra Cache clears Cloudflare with an API token and clears NGINX server caches. It does not set up Cloudflare page caching for you. Ask your host which caching layers it runs.
- Logged-in visitors: Novra Cache always shows logged-in users live pages. If you use FlyingPress’s cache for logged-in users, for example on a membership site, test those pages carefully.
- Object cache: FlyingPress’s Redis object caching is part of FlyingPress. If you turned it on, decide before the switch whether you need a replacement, such as Novra Object Cache.
On shops, include cart, checkout and account pages, forms and your cookie banner in every check. A page cache alone does not fix slow checkout requests, so diagnose those separately.
Test a switch step by step
Treat the switch as a controlled test, not a one-click move. Novra Cache does not import FlyingPress settings, so plan to set it up by hand.
- Back up your site and note your settings. Write down your FlyingPress settings, especially excluded pages and scripts. Keep a separate copy of your media files.
- Record a baseline. Test your homepage, a content page and an important product or form page. You can run our free speed test and note the device and connection you used.
- Restore your original images if you used FlyingPress image optimization. FlyingPress rewrites image URLs in your content. Restore the originals in FlyingPress before you deactivate it, so your content points to the original files again. This works only if you kept the originals.
- Check your Cloudflare setup. FlyingPress’s Cloudflare integration sets up Cloudflare to cache full pages. If you used it, review those Cloudflare settings with whoever manages your account, so visitors do not get outdated pages.
- Keep one page cache only. Deactivate FlyingPress before you turn on caching in Novra Cache. FlyingPress’s documentation also recommends not running other caching or optimization plugins alongside it.
- Set up Novra Cache in small steps. Activate your license and check the health panel. Page caching and code changes start switched off. Some image options for new uploads start switched on, so review them first. Turn on page caching, then add code and image improvements one group at a time.
- Check as a logged-out visitor after each step. Look at menus, popups, forms and your cookie banner on desktop and mobile. On shops, place a safe test order. The Script Manager testing mode shows changes only to administrators, so it is not a full visitor test.
- Measure again and decide. Compare the same pages under the same conditions. If a problem remains that you cannot fix, roll back as described below.
Roll back if something doesn’t fit
Export your Novra Cache settings as a file before you change them. You can also reset everything from the Tools tab. To go back to FlyingPress:
- Deactivate Novra Cache.
- Reactivate FlyingPress, which needs an active license, and check your settings.
- Clear your Cloudflare and host caches, then check your key pages while logged out.
The Novra Cache documentation explains each setting, so you can rebuild your exclusions with confidence.
Choose the setup you can maintain
- Test Novra Cache if paying once, image processing on your server or a Script Manager for each page solves a problem you can name.
- Keep FlyingPress if you rely on its visitor speed data, cloud page analysis, Cloudflare page caching or cache for logged-in users.
- Wait with the switch if your host requirements are unclear or you have not yet found what makes your site slow.
If Novra Cache fits your needs, compare the Novra Cache plans and try it on your own site. One payment, no subscription and a 30-day money-back guarantee. Judge the result by working pages and customer journeys, not by a promised score.
FAQ
Can I run Novra Cache and FlyingPress together?
Not as two page caches. Only one plugin can be your page cache, so deactivate FlyingPress before you turn on caching in Novra Cache.
Will my images still work after the switch?
If you used FlyingPress image optimization, restore your original images in FlyingPress before you deactivate it. Novra Cache leaves your image links as they are and serves WebP and AVIF with a fallback for older browsers.
Does Novra Cache import my FlyingPress settings?
No. Note your FlyingPress settings and exclusions first, then set up Novra Cache step by step and check your pages after each change.
What happens when a FlyingPress license ends?
According to FlyingPress’s documentation, the plugin needs an active license to work fully, and most optimizations rely on its cloud. Novra Cache is paid once. Only its Remove Unused CSS feature uses our service and needs your license to be active.
