Exclude Perfmatters Plugin

Not sure how Perfmatters work but you can ask them.

I had a ticket with WPMN and discovered that PerfMatters was interfering with my password reset and some other issues. Once disabled, no problems. I haven't put it on a test site yet to find out what caused the conflict, but I decided it was best to leave it disabled.

FluentAuth and FluentSnippets share some features, which may be where the conflict arose.

Short answer: you usually can’t fully exclude Fluent Community from Perfmatters as a whole plugin.

Fluent Community works as an SPA (Single Page Application), so its scripts are tightly connected to dynamic navigation. Because of this, trying to globally delay/defer or exclude everything often breaks core functionality.

What you can do instead is:

• Avoid aggressive settings like “Delay All JS”
• Exclude specific critical scripts (instead of the whole plugin)
• Use Script Manager carefully on non-community pages
• Keep lazy loading and other optimizations enabled (these usually work fine)

From my experience (and after discussing this with the Perfmatters team), going too aggressive with JS optimization in Fluent Community tends to cause more issues than benefits.

With a balanced setup, you can still achieve excellent performance (e.g. ~0.3s server response, ~85 mobile / ~99 desktop PageSpeed) without breaking anything.

So the key is not full exclusion, but controlled optimization.

Hope that helps!

About cache plugins : WP Rocket works fine with fluent plugins, litespeedcache can be a problem sometimes