more informations.

I did some tests on a stagging website. all pages are built with sp page builder latest version (production mode is disabled).

I have enabled default joomla page cache plugin => entire pages are cached I have enabled JSpeed plugin => manage css/js compression, webp conversion etc...

from website front-end, for example, I change text color + section background color from sp page builder front-end editor.

A) If cache is not cleaned ( joomla page cache plugin + JSpeed plugin ) = modifications are NOT visible on website front-end.

B) If I clean full cache ( joomla page cache plugin + JSpeed plugin ) = modifications are correctly visible on website front-end.

C) If I clean cache from JSpeed plugin = modifications are NOT visible on website front-end.

D) If I clean cache from joomla page cache plugin = modifications are correctly visible on website front-end.

This means that it is not necessary to clear the JSpeed cache in order to see the changes made by the user.

However, this also means that the Joomla page cache must be cleared in order for user modifications to be visible.

The problem is that after clearing the Joomla page cache, in order to display the changes made by the user, the next visitor returning to the page will have a long loading time, while the page cache is being rebuilt.

In your opinion, is there a way to optimize this regarding SP page builder behavior?

any news?

Hi there,

Thank you for reaching out. Here is the developer feedback.

How SP Page Builder works: SP Page Builder stores page layout and design (colors, padding, backgrounds, etc.) as JSON in the Joomla database. When the page loads, it generates the HTML and inline CSS dynamically.

It doesn't create a full static cached page by itself.

Why your changes only appear after clearing Joomla Page Cache: The Joomla Page Cache plugin stores the entire rendered HTML (including SPPB inline CSS). So when you edit a page, Joomla is still serving the old cached version until that cache is cleared.

JSpeed only optimizes/compresses CSS/JS files — it does not cache the full HTML — so clearing it is not required in your case.

About the slow first load after clearing cache: That’s normal behavior of full-page caching — the first visitor rebuilds the page.

Recommendation:

• Use server-level or CDN caching instead (more efficient and avoids rebuild delays)
• Preload Cache Automatically (e.g. use server cron job, crawler tool or CDN preloader) to keep the cache warm and avoid slow first loads.

Best regards,

Toufiqur Rahman (Team Lead, Support)

Hi,

Thanks for your feedback. Understood, just some last questions :

1. About Preload Cache Automatically when you say use server cron job or crawler tool, what do you mean exactly ? Do you have an example of server cron job task and crawler tool name ?

2. About server-level cache : If I use for instance litespeed cache, do you recommend using : lite speed server cache only or lite speed server cache + JSpeed plugin + joomla page cache default plugin or lite speed server cache + JSpeed plugin

?

3. also, with these caches solutions, is it relevant to use SPPB production mode setting ?

Thanks