The Ideal FlyingPress Settings 2025: The Fastest Cache Plugin For Nginx + Apache With Cloudflare Enterprise On FlyingCDN

Unless you use a LiteSpeed host with LiteSpeed Cache, you should be using FlyingPress.

Unlike WP Rocket, FlyingPress removes bloat, hosts third-party code locally, and better optimizes LCP images. The remove unused CSS feature is faster and Cloudflare Enterprise (FlyingCDN) is much more powerful. But the biggest difference I found is Gijo Varghese seems more interested in innovation and listening to community feedback over “following a roadmap.” That’s why FlyingPress is usually first to release new features, and WP Rocket eventually follows.

FlyingPress also makes SiteGround’s Speed Optimizer nearly obsolete which lacks a ton of features. Compared to FlyingPress, it does a poor job optimizing core web vitals, uses a less performance/secure CDN, and there’s a reason it has a 4.2/5 star rating on WordPress. In this case, use SiteGround Optimizer for Memcached and FlyingPress/FlyingCDN for everything else. However, there are many LiteSpeed hosts that have better performance/price than SiteGround.

If you don’t know Gijo Varghese, he runs the WP Speed Matters Facebook group and is one of the smartest speed gurus. Activate your license key and let’s configure your FlyingPress settings.

My current setup is Rocket.net (with free Cloudflare Enterprise) + FlyingPress + Perfmatters. I kept Perfmatters since I still use the script manager, but you can just use Asset CleanUp (free).

 

1. Dashboard

Just an overview with some purge/preload options.

• Purge pages: HTML pages are purged from the cache.
• Preload cache: cached pages are overwritten instead of purging entire cache.
• Purge pages and preload: HTML pages are purged, then preloaded.
• Purge everything and preload: same as previous setting only it includes everything.
• Documentation – FlyingPress has great documentation. Download the plugin from the FlyingPress website and upload it (key is attached to the zip file and added automatically).
• Facebook community – the FlyingPress Facebook Group is a great place to browse questions, ask new questions, give Gijo feedback, and see upcoming features/updates.
• Open a ticket – leads to the contact page where you can get support (often from Gijo himself) which is the best support I’ve gotten from any cache plugin, including WP Rocket.

 

2. Cache

FlyingPress’ cache now always remains on. If you’re using another caching layer like Nginx, Varnish, or APO, FlyingPress will serve as a fallback cache which can improve cache hit ratio. Since page caching is a different layer than these, there shouldn’t be any compatibility issues.

• Cache logged in users: Off – only enable if you run a membership site (or similar) and have users logging in that need their own cache, otherwise it requires server resources.
• Scheduled preload: Never – Gijo says you should only change it when facing problems with the cache where it’s not updated on time (the cache will be overwritten, not purged).
• Exclude Pages from Caching: key eCommerce pages, admin/login pages, and several others are automatically excluded from the cache (see list), but you can add more here.
• Ignore Query Strings: if you have query strings that should be ignored and not cached (i.e. ad campaigns), add them here. FlyingPress has a list of query strings it ignores by default. Johnny also has a detailed guide on when to ignore query strings with examples.
• Bypass cookies: can decrease performance and not recommended unless you need to.
• Test the cache – test your website in uptrends.com and look for x-flying-press-cache: HIT.

 

3. CSS

• Minify CSS: On – usually gives you better results, but test it. Johnny says leave it off on larger sites. Cloudways says enable it in your cache plugin, then disable it in Cloudflare.
• Remove unused CSS: On – use either FlyingPress or Perfmatters for this, but not WP Rocket (see loading used CSS inline vs. separate file). FlyingPress loads used in a separate file which is faster for users, but slightly worse for scores. WP Rocket loads used CSS inline which is better for scores, but slower for actual users. Perfmatters has an option for both.
• Load unused CSS: remove – best for performance but requires excluding files if they break your site. View common unused CSS exclusions in the Perfmatters documentation for Elementor, Divi, and several others. If you’re still having trouble, “on user interaction” in the next best setting. FlyingPress’ documentation explains the difference between the 3.
• Exclude stylesheets: if the setting above, breaks your site, exclude problematic CSS files.
• Include selectors: if FlyingPress isn’t able to detect certain CSS selectors to include in used CSS, add them here. Gijo originally gave the example of a cookie-notice CSS selector.
• Lazy render elements – similar to lazy loading images only for anything on your site if it loads below the fold. Comments (#comments) and footer (#footer) are common as well as Elementor/Divi sections and WooCommerce related products. Check your own site’s CSS selectors by viewing your site → right click any element you want to lazy render → inspect → right click highlighted code → copy → copy selector → paste into FlyingPress.

 

4. JavaScript

• Minify JavaScript: On – same principle as minify CSS only for JavaScript (test results).
• Preload links: On for VPS hosting, Off for shared – when users hover over a link, that page is preloaded so by the time users actually click it, it appears to load instantly. While this doesn’t improve scores, it does improve perceived load time. But it also means if users hover over lots of links (such as a WooCommerce site with tons of image links), a bunch of pages will be preloaded which stresses your server. Whether you should enable it depends whether your hosting is powerful enough, and whether your users hover over lots of links.
• Defer JavaScript: On – can fix render-blocking errors by loading JS asynchronously. WP Johnny suggests disabling it since it improves scores but slows down your site, so test it.
• Defer inline: On – if you enabled the previous setting, you usually want to enable this too.
• Exclude scripts from defer: check the Console tab in Chrome Dev Tools to see whether certain JS files are causing issues when being deferred, then exclude them here if needed. “hooks.min.js” and “i18n.min.js” are common exclusions in Perfmatters’ documentation.
• Delay JavaScript: Delay all – best for performance but like removing unused CSS, you’ll need to exclude files. Luckily, Perfmatters also has common JS delay exclusions. If you’re having trouble, use “delay selected” and add JS files manually found in your “third-party code” + “remove unused JavaScript” report (see screenshot). FlyingPress already delays many of them like Google Analytics and reCAPTCHA, but there may be others. You can also try delaying plugins loading below the fold (wp-content/plugins/plugin-name), AdSense (adsbygoogle.js), and GTM (googletagmanager.com). AdSense isn’t delayed by default because it can affect your revenue, and because some people load it above the fold (ugh).

Common third-party code to delay:

google-analytics.com
xfbml.customerchat.js
fbevents.js
widget.manychat.com
cookie-law-info
grecaptcha.execute
static.hotjar.com
hs-scripts.com
embed.tawk.to
disqus.com/embed.js
client.crisp.chat
matomo.js
usefathom.com
code.tidio.co
metomic.io
js.driftt.com
cdn.onesignal.com

 

5. Fonts

• Optimize Google Fonts: On – hosts fonts locally (instead of creating external requests to fonts.gstatic.com), combines, and inlines them. This can’t be done for third-party JS files.
• Display fallback fonts: On – adds font-display: swap to CSS which fixes “ensure text remains visible during webfont load” in PSI. Until your font is loaded, a fallback font is used to prevent FOIT (flash of invisible text), but it can cause FOUT (flash of unstyled text).
• Preload fonts: view font files in a Waterfall chart (like GTmetrix) and test preloading them. Gijo recommends only preloading fonts mentioned in the CSS file and fonts loading above the fold. When you’re done, check for preloading errors in the Console tab of Chrome Dev Tools. Preloading fonts that aren’t being loaded is a no no, so make sure URLs are correct.

 

6. Images

• Lazy load images: On – FlyingPress uses native lazy load while Perfmatters’ is JS-based. There are arguments for both, but only enable lazy load in one plugin (I use FlyingPress).
• Exclude above the fold images: Usually 2-3 – this should be the number of images that usually load above the fold. Most my posts have 3 above the fold images (see screenshot below) so I set it to 3. These will automatically be excluded from lazy load and set as high priority for better LCP. You can also exclude them manually by adding their image URLs.
• Add responsive images using FlyingCDN: On – serves smaller images to mobile for better mobile LCP scores when using FlyingCDN (which uses Cloudflare Mirage + Polish).
• Add missing width and height: On – adds width/height to images which can fix “use explicit weight and height” in PSI. If you’re still seeing this error, it’s probably from CSS or custom coded images. In this case, add the dimensions manually or specify them in CSS.
• Host Gravatar images locally: On – Gravatars create third-party requests which hurts scores if you have lots of comments. This hosts Gravatar images locally to prevent this.
• Preload critical images: On – FlyingPress will attempt to detect above the fold images and preload them for better LCP. Most other cache plugins make this a manual process.
• Disable emoji: On – removes a small JavaScript code in WordPress that displays emojis.

 

7. IFrames

• Lazy load iFrames: On – iFrames like embedded YouTube videos and Google Maps will only be load when they’re near the viewport, then excluded when they’re in the viewport.
• Use placeholder image for YouTube videos:  On – replaces YouTube iFrames with a preview image and self-hosts YouTube placeholder images to prevent external requests to i.ytimg.com. This also means YouTube thumbnails can be cached and served from a CDN.

 

8. Bloat

These can overlap with Perfmatters’ General settings, so only enable them in 1 plugin.

• Remove Google Fonts: Off – only use if you’re in the process of using system fonts or custom fonts and need them disabled. Otherwise, it removes Google Fonts from the site.
• Disable XML-RPC: On – bad for speed + security (used to publish content from mobile).
• Disable RSS feed: Off – you would only turn this on if your website doesn’t have a blog.
• Disable Block editor CSS: Off – if you’re using Gutenberg, leave it off. If you’re using a page builder instead, turn this on. This prevents a CSS file from loading across your site.
• Disable oEmbeds: On – when you paste a URL into your WordPress editor, this loads a pretty preview (from YouTube, Facebook, Tweets, etc). If you don’t need this, turn it on.
• Disable Emojis: On – removes a JavaScript file needed for emojis (use Unicode instead).
• Disable WP Cron: Off – easy way to disable wp-cron, then you would add a real cron job (see your hosting instructions) which can reduce CPU usage. In which case, turn this on.
• Disable jQuery Migrate: Off – if you’re not using a page builder, turn it on. Perfmatters has docs on dealing with jQuery in the script manager, defer, delay, and preload settings.
• Disable Dashicons: On – prevents admin icons from loading a CSS file on the frontend.
• Control Post Revisions: 5 or 10 – this gives you enough revisions where if you need a backup, you have a few to choose from, but still stops them from adding too much bloat.
• Control Heartbeat: Enable only while editing posts for 60s – also recommended by Perfmatters (especially if using page builders) to disable it unless you’re editing content.

 

9. CDN

FlyingCDN uses arguably the fastest CDN, Cloudflare Enterprise.

Unlike many host’s CDN (SiteGround, Kinsta, WP Engine), FlyingCDN is specifically good for optimizing dynamic/WooCommerce sites. Argo Smart Routing (which includes Tiered Cache) can reduce TTFB by 33% alone. You should also see reduced server load with their Enterprise-level firewall and by using Cloudflare Mirage + Polish to optimize images as opposed to a plugin.

TTFB is 40% of LCP and hosting/CDN are 2 key factors. That’s why my global TTFB is so low in KeyCDN & SpeedVitals which test TTFB in multiple locations, unlike GTmetrix and other tools.

FlyingCDN Instructions

Step 1: Add money to your FlyingCDN account.

Step 2: Set up a custom CDN URL by adding a CNAME record to your DNS.

Step 3: Add your CDN URL to FlyingPress and select the types of files to serve (i.e. all files).

Step 4: View your source code and make sure the correct files (i.e. CSS/JS/fonts) are being served from FlyingCDN. You can also try purging or waiting some time for the files to update.

 

10. Database

I prefer WP-Optimize for database cleanups since it can take backups via UpdraftPlus and remove tables from old plugins. If I were to use FlyingPress, here are the settings I would use (just remember to keep about 5-10 post revisions in the bloat settings before saving changes).

Otherwise, keep everything off in FlyingPress and use WP-Optimize.

You can remove tables left behind by old plugins you uninstalled (that is, if you don’t use it anymore), and see how much overhead certain plugin features/modules add to your database.

 

11. Configure FlyingPress With Rocket.net

Rocket.net with their free Cloudflare Enterprise is the host/CDN I use and why I have a 100ms global TTFB (great for WooCommerce and international sites). Configure FlyingPress normally.

• No need to add Rocket.net’s CDN URL to FlyingPress.
• No need to use FlyingCDN with Cloudflare Enterprise.
• FlyingPress will automatically purge Rocket.net’s cache.
• FlyingPress’ cache will remain on as a fallback cache to improve cache hit ratio.

 

12. Configure FlyingPress With SiteGround Optimizer

Configure SiteGround Optimizer normally except:

• Disable file-based caching and browser caching.
• Use 1 plugin to disable emojis.
• Use 1 plugin to control Heartbeat.
• Use 1 plugin to clean your database.
• Use 1 plugin to minify/defer JavaScript.
• Use 1 plugin for lazy loading (I recommend FlyingPress).
• Use 1 plugin to preload fonts.
• Leave SG’s CSS settings off and use FlyingPress’ CSS settings with remove unused CSS.

Configure FlyingPress normally while taking advantage of these features:

• Bloat removal.
• Delay JavaScript.
• Remove unused CSS.
• Lazy render HTML elements.
• Preload links.
• Host Gravatars images locally
• Optimize Google Fonts to host them locally.
• Lazy load iframes and use placeholder images.
• Image optimizations (lazy load, add missing dimensions, preload critical images).

 

13. Configure FlyingPress With Perfmatters

Configure FlyingPress normally, then disable everything in Perfmatters except:

General Settings – FlyingPress already removes bloat, but the General settings still have a few extra features like increasing the autosave interval and moving your wp-login page for security.

Script Manager – this is the main reason to keep Perfmatters when using FlyingPress. Enable the script manager in the Assets settings, then view any page/posts on your site. In your admin menu, click Perfmatters → Script Manager. Go to your script manager settings and enable test mode (this only shows changes to logged-in admins to prevent your site from breaking while testing the script manager), but remember to disable it when you’re done to publish changes. Also enable display dependencies which shows all plugins using jQuery, which is bad for speed.

Next, disable plugins or individual CSS/JS files on pages (or posts) where they don’t need to load. For example, if you only use a social sharing plugin on your blog, disable it “everywhere but posts.” Or disable contact forms everywhere but the contact page. You can also use regex.

Preloading – FlyingPress only preloads images/fonts. If there’s anything else you want to preload such as wp-block-library when using Gutenberg, you can do that in Perfmatters. You shouldn’t need to use preconnect/prefetch anything because your CDN URL is preconnected automatically by FlyingPress when you add it, and third-party fonts should be hosted locally. The rest of your third-party code should usually be delayed. Instant page (link preloading) and preloading critical images is already done by FlyingPress, so they should be off in Perfmatters.

Notes

• You don’t need local analytics since FlyingPress delays Google Analytics.
• Only use 1 plugin for lazy load. Perfmatters’ JS-based lazy load while FlyingPress uses native (as I mentioned earlier, there are arguments for both). Both have similar features.

You don’t know until you know: flyingpress.com

You rock Gijo, keep up the great work and thanks for building the awesome community/plugins.

Cheers,
Tom