So you have already Installed FlyingPress Plugin, but don’t know what FlyingPress setting will speed up your website?
Here is the solution!
In this “FlyingPress Settings” blog, I will discuss and share the best FlyingPress Settings that I am currently using with my websites.
By using these settings, I have already optimized my website and boosted its performance. You can check out our FlyingPress Review, where I have shared the details of the performance of my website.
With my recommended FlyingPress settings, you can pass Google’s Core Web Vitals in Google PageSpeed Insights and even get a score of 100 on the mobile tab of Google PageSpeed Insights which is the hardest one to optimize for.
You can also use the Table Of Content of est FlyingPress Setting below to jump around as you need:
Table Of Contents
So let’s get started!
Best FlyingPress Setting [Tested Setting]
FlyingPress is an all-in-one solution to WordPress sites that take care of everything. From page caching, and CDN to image optimization. Any non-techie should be able to create super-fast WordPress sites without going to too many tutorials or multiple plugins for speed optimization.
FlyingPress Plugin is super easy to use and comes with the most affordable yearly pricing. However, you cannot get Flyingpress lifetime deals.
1. Best FlyingPress Settings On – Dashboard
The FlyingPress dashboard comes with a simple UI and is very basic with three different sections – Cache, Account, and Support.
The FlyingPress dashboard has a straightforward user interface and only has three sections: Cache, Account, and Support.
The cache sections have buttons to either ‘Purge Cache‘ or ‘Purge & Preload Cache‘.
In general, you shouldn’t need to use these buttons unless you need to manually clear the cache, but if you do, I recommend using the ‘Purge & Preload Cache‘ button because it will go ahead and warm up your pages so that first-time visitors experience a quick loading time.
You can find the following information in the Account section:
- Whether the Status of your FlyingPress account is ‘Valid‘ or not
- The Name that appears on your FlyingPress account.
- Your FlyingPress license’s expiration date, so you’ll know when it needs to be renewed.
Additionally, there is a quick link to your FlyingPress account in the account section’s upper right-hand corner.
The Support section includes the following useful quick links:
Documentation – If you’re unsure of which FlyingPress settings to use, I recommend you to use the FlyingPress documentation which will explain each area within the plugin.
Facebook Community – With over 1,500 members, the FlyingPress Facebook Group is excellent. The community is very beneficial, and Gijo, the creator of FlyingPress, actively participates in the forum and answers lots of queries.
Open a ticket – Use this link to create a support ticket if you have a question or concern about FlyingPress. The FlyingPress team is always happy to assist and will respond to your question within 24 hours.
2. Best FlyingPress Settings On – Cache
Cache Pages – Enabled
- Additional Auto Purge – None
- Cache Lifespan – Never
- Exclude Pages from Caching – Enter in the URL or path of pages that you want to be excluded from caching
- Ignore Query Strings – Query strings that match will be removed and the cached page will be served
- Optimize for Logged in Users – Disabled
FlyingPress’s “Cache Pages” setting needs to be turned on.
FlyingPress will create static HTML versions of all of your pages when “Cache Pages” is enabled, which can significantly reduce the time it takes for a page to load (TTFB).
This is due to the fact that the HTML versions of your pages are cached and do not need to be dynamically generated each time a user accesses them, which significantly slows down the rendering of a page and uses calls to PHP, WordPress, and your database.
The FlyingPress cache is created in what manner? By preloading the pages listed in your sitemap, which is automatically recognized by FlyingPress, your static HTML page cache will be created.
To make sure the FlyingPress cache is working, open your website in an incognito window and look for the FlyingPress response header (x-flying-press-cache: HIT) on the first request/HTML page.
Additional Auto Purge: None In most cases
When you publish/update a post or update the stock in WooCommerce, FlyingPress already FlyingPress already detects many URLs and purges key pages.
However, you may want to purge the cache for additional posts or pages.
The three options are:
- All Posts and Pages – Purge the cache for all posts and pages
- Pages only – Only purge the cache for pages along with the automatically detected URLs
- None – Only purge the automatically detected URLs
Cache Lifespan – None in most cases
You can specify if you want to automatically purge and preload your site’s cache after a specific lifespan.
Most websites should have “Cache Lifespan” set to “Never,” but if you are experiencing problems with “nonce” validation, you might need to change it to a lower value.
Remember that the cache will use more server resources the more frequently you automatically purge it.
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
You can enter query strings here that you want to replace with the cached version of the page. FlyingPress doesn’t cache pages that contain query strings; instead, it optimizes them as they load.
However, there is a large list of query strings that FlyingPress ignores by default and instead serves the cached page.
You can enter the keywords in the “Ignore Query Strings” box if you require query strings other than the standard FlyingPress ones.
Optimize for Logged in Users: Off
Turning it on means that pages will remain uncached (dynamic). By turning this setting ON, FlyingPress just optimizes pages for logger-in uses “on the fly.” Johnny says this can speed up your admin but will probably cause some issues.
3. Best FlyingPress Settings On – CSS
- Minify & Optimize CSS Files – Enabled
Generate Critical and Used CSS – Enabled
- Load Unused CSS – Asynchronously
- Force Include Selectors – Specify CSS selectors that you want to be included in the Critical & Used CSS
- Lazy Render HTML Elements – Skips the rendering of HTML elements until they’re needed based on CSS selectors that you specify.
Minify & Optimize CSS Files: On
You should enable the “Minify & Optimize CSS Files” setting in FlyingPress.
Doing this will increase the loading speeds of your site by removing all unnecessary characters in your CSS files such as empty spaces, empty lines, and comments.
After saving this option, click through your site and make sure everything still looks good.
Generate Critical and Used CSS: On
Critical CSS can fix render-blocking resources by creating a critical CSS file that is injected into the head. Unused CSS removes unused CSS selectors and the new file will be loaded asynchronously from an external stylesheet.
You should enable the “Generate Critical and Used CSS” setting in FlyingPress.
Keep in mind that Critical CSS and Used CSS are slightly different.
The Critical CSS is all the CSS needed for rendering your page above the fold.
The Used CSS is all the remaining CSS generated after removing all the unused CSS for your page. The used CSS is then injected as an external stylesheet that is loaded asynchronously.
Load Unused CSS- Asynchronously
You have three options for how you want to load your unused CSS after you enable the “Generate Critical and Used CSS” setting:
- Asynchronously – Your remaining CSS files will load alongside the rest of your files in an asynchronous manner. The most secure choice is this.
- On user interaction – Similar to loading files asynchronously, but with the additional CSS files starting to load only after a user interaction (mouse movement, keyboard input, scrolling, etc.)
- Remove – By selecting this option, all of the unnecessary CSS files will be deleted and never loaded. The best performance is provided by this option, but use extreme caution as using it might result in problems.
If you select the “on user interaction” or “remove” options, make sure to thoroughly test your website. This is especially important right after the first page loads, as you might notice things “jump” or the styling adjust itself. In this case, you should select the “asynchronously” option to be safe.
Force Include Selectors
Sometimes, FlyingPress may not include all the Critical and Used CSS that it needs to. You can enter specific selectors in the “Force Include Selectors” box if you discover that some of the selectors for required elements are missing.
Lazy Render HTML Elements
I personally am a huge fan of this FlyingPress Feature.
FlyingPress’s “Lazy Render HTML Elements” setting needs to be turned on.
Enter the selectors for the elements you want to have lazy rendering in the box.
Your Time to Interactive (TTI), Total Blocking Time (TBT), and Largest Contentful Paint (LCP) scores can all be significantly increased by using lazy HTML elements.
- Preload Links – Enabled
- Exclude Scripts from Defer – Specify which scripts should be excluded from deferring
- Load Scripts on User Interaction – Enabled – Specify which scripts should download and execute only after a user interaction (such as mouse movement, keyboard input, scroll, etc.)
Essentially the same improvements as minify JS, but for CSS.
By removing all unnecessary characters from your JS files, such as blank spaces, empty lines, and comments, you will speed up the loading times of your website.
Once you’ve saved this choice, visit your website to make sure everything still looks good.
You should enable the “Preload Links” setting in FlyingPress.
Enabling this option will improve the perceived loading time of pages for a user that is navigating around your site.
If a user hovers over or touches a link, that page will start to be fetched in the background. That way, when the user does actually click or taps the link, the page will appear to load instantly.
Can fix render-blocking errors by loading JS asynchronously, but Johnny says to not enable it since it improves scores at the cost of a slower website.
Exclude Scripts from Defer
In this box, you can specify which scripts you want to be excluded from being deferred.
As a result, you can add the URL of the script or a keyword that matches the script tag if you need to prevent a specific script from receiving the defer attribute.
Load Scripts on User Interaction-On
This FlyingPress setting is primarily used to delay the loading of particular plugins and third-party code until user interaction.
FlyingPress has a fantastic feature called Load Scripts on User Interaction that has the potential to add several seconds to the loading time of your website.
The FlyingPress setting “Load Scripts on User Interaction” needs to be enabled.
By loading and executing the designated scripts only when there is user interaction, such as mouse movement, keyboard input, scrolling, touching a mobile screen, etc., Load Scripts on User Interaction enhances performance.
Enabling this feature can greatly improve a number of speed recommendations in Google PageSpeed Insights including the following:
- Minimize Main thread work
- Total Blocking Time (TBT)
- Time to Interactive (TTI)
- First Contentful Paint (FCP)
- Largest Contentful Paint (LCP)
5. Best FlyingPress Settings On – Font
- Optimize Google Fonts – Enabled (if you use Google Fonts on your website)
- Display Fallback Fonts – Enabled (if you want to ensure text remains visible during Webfont load)
- Preload Fonts – Enter font URLs to prioritize loading fonts that are required for rendering
If your website uses Google Fonts, these are the FlyingPress settings for the Font section that you should use.
The fastest way to use fonts is on this site, which only uses system fonts, which require zero extra requests or downloads. There is nothing you need to do for this section if your website uses system fonts.
Optimize Google Fonts: On
You should enable the “Optimize Google Fonts” setting in FlyingPress if you are using Google Fonts on your website.
When you enable the optimize Google Fonts setting, FlyingPress will:
- Combine all Google Fonts on the page to reduce HTTP requests
- Self-host Google Fonts (download and save the fonts locally)
- Inline Google Fonts CSS
With all of the new GDPR rules, the Google Fonts optimization that FlyingPress provides is clutch It will self-host your Google Fonts and take care of all the technical details so you don’t have to.
Display Fallback Fonts: On
If your website uses Google Fonts, you should activate the “Display Fallback Fonts” option in FlyingPress.
System fonts don’t require a fallback font, so if your website (like this one) uses them, you don’t need to do anything else.
If you use external fonts, like Google Fonts, they won’t display until they have fully loaded. The “Flash of Invisible Text” effect, also known as FOIT, may result from this. The Display Fallback Fonts FlyingPress documentation contains a nice GIF of this.
When “Display Fallback Fonts” is enabled in FlyingPress, your website will initially display a system font to users until your Google Font is prepared, at which point it will take over and display.
The Google PageSpeed Insights recommendation to “Ensure text remains visible during Webfont load” is fixed by doing this, but it will result in what is known as “Flash of Unstyled Text” (FOUT).
Preload Fonts -On
You can enter the URLs of any fonts you want to preload that are necessary right away for rendering your page in this box.
FlyingPress’s Preload Fonts feature lets you instruct the browser to begin downloading fonts that it ordinarily wouldn’t notice until much later, typically because the font is referenced in a CSS file.
How do I choose which FlyingPress font URLs to preload? The easiest way to do this is to go to Google PageSpeed Insights and enter the URL for the page you want to analyze.
If you see a suggestion that says “Preload Key Requests,” then look for a list of font URLs under that section.
Right-click on each one, choose “Copy Link Address,” and then add it to the “Preload Fonts” box in FlyingPress.
6. Best FlyingPress Settings On – Image
Lazy Load Images – Enabled
- Exclude Above Fold Images from Lazy Load – 2 images
- Exclude Images from Lazy Load – Specify which images you want to preload and have displayed immediately without lazy loading them
- Add Responsive Images – Enabled (only enable this if you are using FlyingCDN)
- Add Width and Height Attributes – Enabled
- Preload Critical Images – Enabled
- Disable Emoji – Enabled
Lazy Load Images- 0n
The “Lazy Load Images” check box in FlyingPress needs to be enabled.
You should lazy load your images if you want to pass Google’s Core Web Vitals.
My blog posts occasionally feature dozens of high-resolution images, like the ones in this tutorial. Imagine if, when the user first clicked on this page, each and every one of those images had to load. That might take some time, particularly with a slow connection.
When the “Lazy Load Images” option is turned on, images that aren’t necessary for the page’s initial rendering (which is the majority of them) won’t load until the user scrolls them close to their viewport.
If you’re using another performance plugin or theme that lazy loads images, make sure to disable it in other plugins and only enable this option in FlyingPress.
Exclude Above Fold Images from Lazy Load
Flying Press’s “Exclude Above Fold Images from Lazy Load” setting should be set to 2 images, but yours may be different depending on how many images are above the fold on each page.
It’s good when images load slowly. It stops the browser from having to load numerous images that are below the fold and are not required for a web page’s initial rendering.
Exclude Images from Lazy Load
You can manually exclude a list of images from being lazy-loaded by entering them in this box.
By entering “flyingpress-best-settings.png” or “wp-image-3159” in the “Exclude Images from Lazy Load” box, you can prevent that image from being lazy-loaded.
Add Responsive Images – On
FlyingPress’ “Add Responsive Images” setting should be enabled, but there are a few crucial details to remember.
Based on render size, this resizes the images to the proper size. similar to the image resizing offered by Cloudflare.
Add Width and Height Attributes – On
You should enable the “Add Width and Height Attributes” setting in FlyingPress.
Your CLS (Cumulative Layout Shift) scores will increase as a result of this setting’s significant contribution to the reduction of layout shifts brought on by images.
Preload Critical Images – On
FlyingPress’s “Preload Critical Images” setting needs to be turned on.
FlyingPress will make an effort to identify any images that are visible in the viewport so that they can be preloaded and automatically excluded from lazy loading.
Disable Emoji: -On
7. Best FlyingPress Settings On -iFrame
- Lazy Load iFrames – Enabled
Use Placeholder Images for YouTube iFrames – Enabled
- Self-host YouTube Placeholder – Enabled
If your website uses components like embedded YouTube videos or other iFrames, you should enable all three options in FlyingPress’ iFrame section.
Lazy Load iFrames: On
iFrames with Google Maps and embedded videos will only load when they are close to the viewport and will not load if they are in the viewport.
Use Placeholder Image for YouTube iFrames: On
Self-host YouTube Placeholder: On
This FlyingPress setting is absolutely amazing. You should enable the “Self-host YouTube Placeholder” setting in FlyingPress.
This setting works in conjunction with the “Use Placeholder Images for YouTube iFrames” option. When you have that option enabled, YouTube videos will be replaced with the thumbnail image from your video.
Even when using placeholders, you may still notice third-party requests from ytimg.com. This should eliminate them by hosting the placeholder on your server instead of pulling them from that external domain.
8. Best FlyingPress Settings On With CDN
Enable CDN – Enabled (if you are using FlyingCDN)
- CDN URL – Specify the URL of the CDN that will be used for delivering static files
- Type of files – All files
If you’re using FlyingCDN, make sure the “Enable CDN” setting is activated.
A content delivery network is a CDN. In other words, it essentially consists of a number of servers dispersed across the globe that collaborate to deliver content to users quickly regardless of their location.
Why should I use FlyingCDN?
- 70+ PoPs with under 30ms global latency
- Automatically compress your images and serve them in WebP format (you no longer will need a plugin like ShortPixel to do this)
- Responsive images which save you tons of time from needing to manually resize images
- Minify CSS and JS files on the fly
- Global file replication
- Custom subdomain (instead of a URL like flyingcdn-302b4ac6.b-cdn.net on all your files, you can make it really nice so it only says cdn.your-site.com)
👉 Best Web Hosting Service
How to Set Up FlyingCDN with FlyingPress
FlyingCDN costs $3/month per 100GB, so it’s very affordable for all of the benefits that it offers.
Step 1: Recharge your FlyingCDN account.
Step 2: Set up a custom CDN URL by adding a CNAME record in 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 are being served from FlyingCDN. You can also try purging, or just waiting some time for the CDN files to update.
- Post Revisions – Disabled
- Post Auto Drafts – Disabled
- Trashed Posts – Enabled
- Spam Comments – Enabled
- Trashed Comments – Enabled
- Expired Transients – Enabled
- All Transients – Enabled
- Optimize Tables – Enabled
- Automatic Cleaning – Weekly
Let’s go over each of the database cleanup options in more detail:
- Post Revisions – After you officially publish a post or page, revisions are the older versions of your post or page that are saved.
- Post Auto Drafts – As you’re creating or editing a post or page, automatic drafts get saved of your content along the way so that you don’t lose your work.
- Trashed Posts – These are posts that you’ve deleted and put in the trash.
- Spam Comments – These are comments that have been marked as spam, either by a plugin or manually yourself.
- Trashed Comments – These are comments that have been deleted and put in the trash.
- Expired Transients – Transients are temporary options that are created by plugins. They are safe to remove.
- All Transients – As stated above, transients are temporary options that are created by plugins and are safe to remove. Transients are frequently re-created by plugins so you may not see the number hit zero even after removing them.
- Optimize Tables – This will optimize the tables in your database so they are running efficiently without any bloat. You should always have the latest backup of your site and database as a best practice (I use the free version of UpdraftPlus).
- Automatic Cleaning – Here you can choose how frequently you want your database to be cleaned up and optimized by FlyingPress. You can choose “Never,” “Daily,” “Weekly,” or “Monthly.” I would recommend choosing “Weekly” so your database stays optimized every week.
10. Best FlyingPress Settings On – License
- License Key – Your license key. If the keyless activation doesn’t work for whatever reason, you can manually enter your license key here.
- Enable Beta Versions – Disabled
You will receive a purchase receipt after paying for FlyingPress, and it will include your License Key.
The FlyingPress Setup section at the top explains how to download FlyingPress directly from your Account, in which case your license will be activated when you upload it to your WordPress website.
You can paste your license key into the box in the License section and click “Activate License” to activate your license manually if FlyingPress doesn’t do so automatically.
Conclusion On Best FlyingPress Settings
I’m done now! Really simple, wasn’t it?
I sincerely hope that this in-depth guide to FlyingPress’ ideal settings will enable you to speed up your sluggish WordPress website and pass Google’s Core Web Vitals, which will grant you the much-desired ranking boost!
If you have any questions, let me know in the comment section below. I will be happy to respond.