Wordpress LScache Plugin: Feature Suggestion: Simple CDN Solution
Last Updated on: Wed, 15 Apr 2026 00:00:02 You should consider to add simple CDN solution like https://wordpress.org/plugins/cdn-enabler/ to your app instead of suggesting clients to use additional Cache system which has CDN solution. In my opinion most of the people use additional cache solutions just for their CDN feature. Thanks @endery, This is indeed our next scheduled feature for development. One question about it, do you think we need to enable users to upload attachments to AWS S3 for CDN solution? Or just simply give users ability to replace their links to CDN path. Thanks again. Im also really looking forward to it. Hi I am selling CDN service to my clients too. It should be CDN provider independent and give user ro replace their links to CDN path. Not a problem. Thanks @endery Yes, this would be a good feature to have. If possible, make it so that the cached page itself is also served by cdn. CDN is added in v1.2.3. nice! Does this also allow the cached page itself to be served via the cdn? Or is it only for static assets like css, js, and images? Can you tell a bit more about cached pages? Currently its only for static files. I mean the page cache created by the plugin. This is a static file. You can join our https://golitespeed.slack.com/messages/C3RJHNBTQ for further suggestion if you prefer. Do you mean Pages in WP or all pages included post page? I mean that when a post or page is published litespeed will create a cached version of that page/post which is a static file (built-in page cache (LSCache)) shown by looking at the headers and seeing litespeed HIT. I am wondering whether this cached page/post will also be served via the cdn with the new feature added this update? Or does the CDN integration only serve css,js,images? No, unless the CDN provider is using LiteSpeed WebADC. I believe there will be in future. Because there are many situations normal CDN cant handle. For example, private cache and ESI.
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference