Skip to main content

FluentCommunity

#General

Discussion: LiteSpeed Cache for FluentCommunity

Please share your experience of setting up the LiteSpeed ​​Cache plugin for a site with FluentCommunity.

I understand that the cache plugin settings are not universal for everyone, but perhaps you have identified some peculiarities regarding working with FluentCommunity?

What functions do you use and what have you disabled? What pages of the site have you added that are not used for cache?

Discussion: LiteSpeed Cache for FluentCommunity
  • 4 likes
  • 8 comments

Artur Abakarov

ChatGPT prepared this answer for me, I'm sharing it as an example, be careful and make backups.

###1. Redis Settings in LiteSpeed Cache
Go to LiteSpeed Cache > Cache > Object Cache and set:

  • Enable Object Cache – Yes
  • Method – Redis
  • Host – 127.0.0.1
  • Port – 6379
  • Redis Database ID – 0
  • Key postfix – you can leave it empty or set a unique one (for example, kadence_site1) if you plan to use multiple sites on the server.
  • Redis timeout – 360 seconds (can be adjusted)
  • Prefix for cache – it is advisable to set it for convenience when clearing the cache.
  • Checking the connection with Redis – do a test (it should be OK).

2. General LiteSpeed Cache Settings

Go to LiteSpeed Cache > Cache:

  • Enable cache – Yes
  • Cache logins – No (for CRM and the community it is better to disable)
  • Cache the REST API – Yes
  • Cache pages with query string – Yes
  • Enable mobile device caching – Yes (if there is a mobile version of the site)
  • Cache users with roles – disable caching for admins and editors, but leave it for regular users and community members.

3. Kadence and FluentCommunity/CRM optimization

  • Enable Caching of JS and CSS, but with an exception for FluentCRM and FluentCommunity pages (for example, exclude /community/* and CRM pages).
  • Use Deferred loading of JS and CSS asynchronously, but again, it is important to test so as not to break the functionality of the plugins.
  • Critical CSS – enable and generate using templates.

4. Database Settings (MariaDB)

Since FluentCRM and FluentCommunity generate a lot of queries (especially to the wp_users and wp_postmeta tables), I recommend:

  • Enable query cache (if it is not present by default).
  • Increase innodb_buffer_pool_size to 60-70% of available RAM.
  • Optimize indexes if you notice long queries.

5. LiteSpeed Cache > CDN

If you are not using an external CDN yet, you can activate at least QUIC.cloud CDN (it is compatible with LiteSpeed), this will speed up the loading of static (images, CSS, JS).

Hoang Hxn

Cuong Thach Can be used as a reference for setting up the HXN Tribe.

Cuong Thach

Hoang Hxn I never receive notification via email to engage, why FluentCommunity lack of the most important notification like this?

Even login to the account, notification for tag or mentioned didn't display too.

I cannot login all day to observe the notification.

Artur Abakarov

I continued my search for optimal LiteSpeed Cache settings, it started working better, sharing an example, but please back it up, I don't know yet if my site will go down despite the nice speed.

ChatGPT Answers snippet: Here's a list of recommended settings for the "Page Optimization" section of LiteSpeed Cache, assuming you have WordPress with the Kadence theme and FluentCommunity + FluentCRM plugins (they use JS and dynamic data loading, so let's be careful).

LiteSpeed Cache → Page Optimization

CSS Settings

  • ✅ CSS Minify = ON
  • ✅ CSS Combine = OFF (Kadence works better without CSS merging)
  • ✅ Generate UCSS = ON
  • ✅ UCSS Inline = ON
  • ✅ CSS Combine External and Inline = OFF
  • ✅ Load CSS Asynchronously = ON
  • ✅ Font Display Optimization = Swap

JS Settings

  • ✅ JS Minify = ON
  • ✅ JS Combine = OFF (otherwise the interactive blocks in Kadence and FluentCRM may be broken)
  • ✅ JS Combine External and Inline = OFF
  • ✅ Load JS Deferred = ON
  • ✅ Exclude jQuery = ON (mandatory for compatibility with Kadence and plugins)

HTML Settings

  • ✅ HTML Minify = ON
  • ✅ Inline CSS Minify = ON
  • ✅ Inline JS Minify = ON
  • ✅ DNS Prefetch = ON
    (Enter external domains here if you load third-party fonts, icons or scripts, e.g. fonts.gstatic.com).
  • ✅ Remove Comments = ON

Media Settings

(they are in a different section, but often go "in conjunction" with Page Optimization)

  • ✅ Lazy Load Images = ON
  • ✅ Lazy Load Iframes = ON
  • ✅ Add Missing Sizes = ON
  • ✅ Optimize Automatically = ON

Why these settings?

  • Kadence itself is well optimized, but is sensitive to combine settings (especially JS Combine ).
  • FluentCRM and FluentCommunity are dynamic SPA components with AJAX requests, it's important for them not to touch jQuery and break the order of loading scripts.
  • Asynchronous loading of styles and scripts with UCSS will give a nice speed boost.

Artur Abakarov

The next step that accelerated my site turned out to be individual for everyone. It is related to the functions of excluding dynamic pages and AJAX requests, CSS, JS code and so on. This is an important and painstaking way, it will give more optimization and speed up the site.

Artur Abakarov

Shahjahan Jewel If it is possible, can you suggest which AJAX can be excluded in theLiteSpeed Cache → Cache → Excludes → Do Not Cache Query Strings
This will prevent dynamic requests from being cached.

I've now added:

action=fluent_community_*

nonce=*

Artur Abakarov

After I made a site without the /portal/ slug, I had a cache malfunction on the site, I tried for a couple days to deal with it, but unfortunately had to revert the backup to when FluentCommunity opened via the slug instead of the root site.

Artur Abakarov

My new research with object caching is that I moved this function to Redis object cache, and left page cache in LiteSpeed Cache. They work well together.

I wonder if anyone has tried the Pro version, but this is a distant question.