Title: Slow cache functionality
Last modified: March 30, 2023

---

# Slow cache functionality

 *  Resolved [capoan](https://wordpress.org/support/users/capoan/)
 * (@capoan)
 * [3 years ago](https://wordpress.org/support/topic/slow-cache-functionality/)
 * Hello,
 * I have a strange situation with litespeed cache and the problem is that is taking
   a lot of tine on the server to process the information and store it into cache.
 * I’ve monitor the load of the pages with x-ray and the only 2 issues that I have
   are
 * _`Issue name Type Duration (%)`_
 * _`WordPress/litespeed-cache Module/Plugin 66.805% (2.605 sec)`_
 * _`ob\_end\_flush System function 41.748% (1.628 sec)`_
 * If I disable the plugin then the website is faster.
 * If a page is cached then everything is fast, so delivery from server cache to
   browser is very good.
 * I’ve had multiple discussions with hosting support team for this and they’ve 
   made update to litespeed 6.1 and still the same issue.
 * As features that we are using are:
    - Browser cache complete
    - Object cache => in Redis
    - webp image replacement (all images are already webp)
    - cron managed by WP Toolkit from cPanel
    - Public cache complete
    - Private cache complete
 * One last thing that I want to mention is that we have aproximative 3.800 products
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fslow-cache-functionality%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [serpentdriver](https://wordpress.org/support/users/serpentdriver/)
 * (@serpentdriver)
 * [3 years ago](https://wordpress.org/support/topic/slow-cache-functionality/#post-16610626)
 * First of all you have completely wrong settings for browser cache. Never enable
   browser caching for dynamically generated pages. This always displays stale content.
   Remove that configuration and try again.
 *  Plugin Support [qtwrk](https://wordpress.org/support/users/qtwrk/)
 * (@qtwrk)
 * [3 years ago](https://wordpress.org/support/topic/slow-cache-functionality/#post-16612377)
 * this is normal , our plugin will use ob_start() to buffer the output , this means
   it is hook into system as soon as possible, after wordpress initialize the plugins
   and finish the output buffer at end of process, so basically this function is
   running as long as most of page generation life cycle
 * 2 things you could try , 1) disable ESI if you have that enabled , 2) disable
   object cache , some times the object cache could even slow thing down
 *  Thread Starter [capoan](https://wordpress.org/support/users/capoan/)
 * (@capoan)
 * [3 years ago](https://wordpress.org/support/topic/slow-cache-functionality/#post-16613034)
 * Hello,
 * [@serpentdriver](https://wordpress.org/support/users/serpentdriver/) => I’ve 
   done this and the speed improved. Thank you
 * [@qtwrk](https://wordpress.org/support/users/qtwrk/) => ESI was disabled and 
   with object cache disabled is much better.
 * I will monitor it for one more week and come back on this ticket with a feedback.
 * Thank you very much for your help and settings feedback, it helped!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Slow cache functionality’ is closed to new replies.

 * ![](https://ps.w.org/litespeed-cache/assets/icon-256x256.png?rev=2554181)
 * [LiteSpeed Cache](https://wordpress.org/plugins/litespeed-cache/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/litespeed-cache/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/litespeed-cache/)
 * [Active Topics](https://wordpress.org/support/plugin/litespeed-cache/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/litespeed-cache/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/litespeed-cache/reviews/)

 * 3 replies
 * 3 participants
 * Last reply from: [capoan](https://wordpress.org/support/users/capoan/)
 * Last activity: [3 years ago](https://wordpress.org/support/topic/slow-cache-functionality/#post-16613034)
 * Status: resolved