Skip to main content

FluentCommunity

#General

My Community is a Little Bit Slow to Load - Any tips?

My community takes about 5 to 12 seconds to load (whereas this community takes about 2 seconds!)

My regular pages are usually very fast so I was wondering if there is perhaps some Wordpress setting I need to tweak.

Is there anything I can do in settings to help the community pages load faster? or anything to look out for?

UPDATE:
I think I found the culprit. I think it's Google Tag Manager or something in there. Seems to be a second or two faster when I disable GTM and the 'feed' is very fast.

I will see what's in there and remove it if there's nothing relevant to the community.

  • 1 like
  • 10 comments

WiLson Eberechi

Get some plugins like lite speed, cache plugins and others.

Or you get a vps hosting.

I'm using shared hosting and my Fluent community is my main domain and it loads fast

Ross FCA

WiLson Eberechi No you shouldn't use that kind of caching plugin for Fcom - I think redis is the only recommended option.

WiLson Eberechi

Ross FCA okay.

But why? What reasons?

Prosper

Ross FCA Hi Ross why Redis Cache is the only one we can use? And it's a good idea to have it?

Thomas Oates

Are you running on a VPS or shared hosting? Is PHP Opcache enabled?

Nicolai

Thomas Oates Shared hosting. I don't know the answer regarding Opcache.

I think I found the culprit. I think it's Google Tag Manager. Seems to be a second or two faster when I disable GTM and the 'feed' is very fast.

I will see what's in there and remove it if there's nothing relevant to the community.

Ert K

The community system is like social media, so I don't recommend classic caching plugins like Litespeed etc. Instead, you can use caches like Redis Cache.

David Scurlock

Ert K can you exclude fc via lightspeed?

Claudy Scoufy

David Scurlock : Do it from LiteSpeed.

In the WordPress dashboard, go to Cache
(/wp-admin/admin.php?page=litespeed-cache#excludes).
Open the Exclude tab, then the "Do Not Cache URIs" section.

Your exclusion value is likely /portal/* if you have not changed anything.
On my setup, it is /communaute/*.

Save. Pages matching that pattern will not be cached.

Ert K2

CLAUDY SCOUFY You are absolutely right. Dynamic pages like the community must be excluded from page caching (like Litespeed). My advice for Redis was about object caching.

​To be clear for everyone:

  1. ​Page Cache (Litespeed): Use it for static pages (blog, homepage etc.), but exclude the community URLs (/portal/*) as you said.
  2. ​Object Cache (Redis): Use this to speed up the database queries for the entire site, which gives the dynamic community pages a big boost.

​They are not alternatives, it's best to use both together.

(I got help from ai to avoid any misunderstandings.)