Wordpress LScache Plugin: ESI vs TTL change for nonce
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hello, I have a site which has only one main page (Im ignoring Contact us etc for the sake of this question which doesnt get a lot of views). On that main page there is a nonce which comes from a custom plugin I wrote. I currently have ESI enabled on your plugin to support this nonce. My question is, since I read on your blog that using ESI also has a performance cost, for a site like mine which has only one page, what should (in general of course) be better for fastest page load speeds ? enabling ESI or changing the TTL to support the nonce? Not sure if it matters but my hosting provider utilize LiteSpeed Webserver. Thank you Hi, the ESI will affect performance WHEN there is a lot of ESI block e.g. lets say if one ESI request adds additional 0.05 seconds , then obviously having 1 ESI is very much different than 50 ESIs I dont know how your plugin works , but you can simple try both ways , see how much speed ESI affects and then decide to use ESI way or short TTL way Best regards, What determines the number of ESI blocks? Should I disable cache admin bar and cache comment form settings which I dont think I need and that would leave only the one nonce ESI block? And for the TTL option just to make sure ? 12 hours is the setting for nonce support? and should I change default public page TTL or default front page TTL ? My plugin just has the one nonce which is used to make an AJAX request on page load. Thank you for your answer, Ill try to make a comparison. Hi, these 2 default ESI block should be very light you can check the debug log to see how many ESI block it generates Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference