Q: Change delay in preloading cache

FlyingPress default adds a delay of 0.5s while preloading the cache between each page. This slows down the process and ensures your server doesn't run out of resources. Here is how to set to delay as 1s - recommended for very low-resource servers: <pre><code class="php language-php"> add_filter('flying_press_preload_delay', function(){ return 1;}); </code></pre> If you have a dedicated or high-end server, you can remove this delay by setting it to 0s as below: <pre><code class="php language-php">add_filter('flying_press_preload_delay', function(){ return 0;}); </code></pre>

Q: Purge cache

Purge single URL: <pre><code class="php language-php">FlyingPress\Purge::purge_url($url); </code></pre> Purge multiple URLs: <pre><code class="php language-php">FlyingPress\Purge::purge_urls($urls); </code></pre> Purge all pages: <pre><code class="php language-php">FlyingPress\Purge::purge_pages(); </code></pre> Purge everything: <pre><code class="php language-php"> FlyingPress\Purge::purge_everything(); </code></pre>

Q: Installing FlyingPress

${youtube}<a href="iF2i22GKank">How to get started with FlyingPress.</a>

Question 1

Remove Unused CSS

Accepted Answer

The "Remove unused CSS" feature in FlyingPress is designed to improve the loading time and reduce the file size of your website by removing any unused CSS code. This feature is particularly useful for websites with large CSS files that are not optimized for performance.

Load unused CSS

There are three available options for "Load unused CSS" methods: "Asynchronously", "On user interaction", or "Remove".

Asynchronously - Load the unused CSS in the background, without affecting the loading time of your website.
On user interaction- Load the unused CSS only when the user interacts with the page, such as scrolling or mouse move or touch.
Remove - Completely remove the unused CSS from the website, resulting in a faster loading time and reduced file size.

Exclude stylesheets

You can also specify which CSS files should be excluded from the unused CSS removal process by entering their URL or path in the "Exclude stylesheets" section. This can be useful for CSS files that are essential for your website's functionality and cannot be removed.

Include selectors

Finally, you can also include selectors that should be forced to be included in the used CSS by entering them in the "Include selectors" section. This can be useful if you have selectors that are used on your website but are not automatically detected by FlyingPress.

Question 2

Delay JavaScript

Accepted Answer

Download and execute scripts after user interaction, like mouse movement, keyboard input, scrolling, etc. This helps to improve the page load time and overall performance.

The feature has two methods to delay scripts:

"Delay Selected": This method allows you to specify specific scripts to delay by entering the script selectors in the "Script to Delay" option.
"Delay All": This method delays all scripts except those specified in the "Exclude scripts from Delay" option. This option allows you to exclude specific scripts from being delayed.

With the Delay JavaScript feature, you can improve the user experience by reducing the initial load time and allowing the content to be rendered quickly. The scripts are executed after user interaction, providing a smoother and more responsive experience.

Question 3

Change delay in preloading cache

Accepted Answer

FlyingPress default adds a delay of 0.5s while preloading the cache between each page. This slows down the process and ensures your server doesn't run out of resources.

Here is how to set to delay as 1s - recommended for very low-resource servers:

 add_filter('flying_press_preload_delay', function(){ return 1;});

If you have a dedicated or high-end server, you can remove this delay by setting it to 0s as below:

add_filter('flying_press_preload_delay', function(){ return 0;});

Question 4

Purge cache

Accepted Answer

Purge single URL:

FlyingPress\Purge::purge_url($url);

Purge multiple URLs:

FlyingPress\Purge::purge_urls($urls);

Purge all pages:

FlyingPress\Purge::purge_pages();

Purge everything:

 FlyingPress\Purge::purge_everything();

Question 5

Using in Staging or Testing sites

Accepted Answer

If your domain matches any of the following patterns, it will not be counted towards the number of sites in a license.

localhost
.dev
.local
.test
dev.
staging.
stage.
test.
testing.
.closte.com
.runcloud.link
.kinsta.cloud
.cloudwaysapp.com
.pantheonsite.io
.sg-host.com
.onrocket.site
.pressdns.com
.wpengine.com
.bigscoots-staging.com
.e.wpstage.net
.stacks.run
.servebolt.com
.instawp.xyz
.tastewp.com
.wpdns.site
.updraftclone.com
.flywheelstaging.com

For example, if you've bought the personal plan (single site), it can be activated in "example.com" and "staging.example.com"

Question 6

Installing FlyingPress

Accepted Answer

${youtube}How to get started with FlyingPress.

Frequently Read Articles

Browse All Categories