Guide to Installing and Using LiteSpeed Cache Plugin

Plugin LiteSpeed Cache (LSCache)is a powerful WordPress acceleration solution developed by CompanyVPTS recommended for all customers using Hosting or VPS running LiteSpeed. This is a comprehensive optimization tool that helps websites load faster, save resources, improve user experience, and boost Google PageSpeed scores.

▶

1. Introduction to LiteSpeed Cache

LiteSpeed Cache is a performance optimization plugin for WordPress with outstanding features:

• High-speed full-page caching

• Automatic image optimization

• Optimize CSS/JS

• Database optimization

• Supports QUIC.cloud CDN

• Reduce CPU load for the server

• Accelerate access speed and improve SEO

VPTSuses LiteSpeed Webserver across the entire Hosting/VPS system, so the LiteSpeed Cache plugin worksmaximize performancewhen installing on company services.

2. Install LiteSpeed Cache

Step 1:Hover overPluginon the WordPress admin menu bar and selectFresh installto begin the process of adding the Plugin.

Step 2:In the search box, enter the plugin nameLiteSpeed Cachefor the system to display the plugin to be installed.

Step 3:When the LiteSpeed Cache plugin appears, click the buttonIntall Now to proceed with installing the plugin on the website.

Step 4:After installation is complete, clickActivatefor the LiteSpeed Cache plugin to work on the website.

3. Quick setup - Presets

Regarding quick configuration setup for the LiteSpeed Cache plugin, you can utilize pre-configured presets provided by the plugin vendor. Simply select an appropriate preset and clickApply Preset. When a message appears asking whether to keep the old configuration, please clickOKto continue applying.

4. User guide

Overview

The LiteSpeed Cache overview screen provides you with quick information on the operational status of all LSCache and QUIC.cloud services, making monitoring and management more convenient.

LiteSpeed Cache General Settings

The "QUIC.cloud Online Services" page allows you to enable or disable QUIC.cloud online optimization services, including image optimization, page optimization, and CDN usage. Here, you can view descriptions of features such as image compression, WebP/AVIF conversion, Critical CSS generation, CSS/JS optimization, and advanced acceleration tools, making your website faster and more efficient.

General settings pageregarding auto-upgrade (Recommended off): This option allows the LiteSpeed Cache plugin to update automatically when a new version is available. However, you should disable it to manually update proactively and inspect changes in new versions beforehand.

Guest Mode:When enabled, the plugin pre-generates a cacheable version of the page for first-time visitors. This feature speeds up page loading, especially on mobile devices or unstable connections. However, this mode may modify the file.htaccessand generate additional collected data, so it should only be enabled when truly necessary.

Guest Optimization:This feature enhances optimization for Guest Mode, giving first-time visitors maximum loading speed. When enabling it, read the warning carefully as it can consume a large amount of your UCSS/CCSS quota on QUIC.cloud.

Server IP:This field is used to enter the server IP, allowing QUIC.cloud to call the IP directly instead of the domain name. This helps reduce DNS resolution time and speed up service processing.

Notifications (Off):When enabled, the plugin displays the latest information such as updates, patches, beta versions, or promotions from LiteSpeed. You can turn it off if you do not wish to receive notifications.

Guest Mode User Agent (Default):This list includes speed test bots, web crawlers, and automated User Agents. Listed agents will always be treated asguestand receive the cached page upon access. You can add or remove User Agents according to actual needs.

Guest Mode IP (Default):IP addresses in the list will always be served the guest mode page upon access, as long as Guest Mode is enabled. This helps optimize load speeds for fixed IPs or testing systems.

Cache

Enable Cache (On):Main feature that activates the entire cache system. When enabled, the website will be cached and load faster. When disabled, all cached data will be cleared and the plugin stops caching.

Logged-in User Cache (Off):Create a separate cache for each logged-in account.

• Enable: suitable for sites where few users log in regularly.

• Off: avoid generating unnecessary cache copies for websites with multiple accounts.

Commenter Cache (Off):Cache for recent commenters.

• Enable: comments are displayed immediately upon page reload for websites with high comment activity.

• Off: suitable for websites without comments or where comments require prior approval.

REST API Cache (Off):Cache WordPress REST API requests.
Enable when the website heavily relies on APIs; otherwise keep default.

Login Page Cache (On):Helps speed up the login page and improve admin performance.

• Enable: recommended for standard websites.

• Off: if the website changes login URL and errors occur.

Mobile Cache (Off):Create a dedicated cache for mobile devices.

• Enable: only use when the website has a dedicated mobile theme or AMP.

• Off: suitable for most modern responsive websites.

Mobile User Agents List (Default):List of browser/device names recognized as Mobile to apply separate caching if Cache Mobile is enabled.
Keep defaults if there are no special requirements.

Privately Cached URLs (Leave empty):This feature allows creating a private cache for each user if the path matches the specified strings.
However, for websites with many users logging in frequently, using private cache isunnecessary, because this group of users cares more about features and content rather than page load speed. Therefore, to avoid consuming unnecessary resources, it is recommended toleave blankthis section.

Force Cache URLs:Paths containing the specified string willforced into cacheeven if the website does not have caching enabled for those areas. This is a mandatory speed optimization for pages where you want to ensure caching is always active.

Force public cache URL:Paths containing the declared string willforced to be stored in the public cache, regardless of whether the website's global settings have caching disabled for that section. This approach helps optimize performance for pages that do not contain user-specific private content.

Drop Query String (Default):This option allows you to specify query parameters (query string) that willbypassed when generating cache. This limits creating too many identical cache versions caused by tracking parameters from ads or social media.

Via TTL field:TTL is the duration a page is stored in the cache. Values can range from30 seconds or more. If the TTL is too low, the page almostnot cached, because the retention period is too short.

Default cache time for the entire page (604800 seconds):This is the cache duration for most pages on the website. Default is1 week.
You can adjust according to your needs:

• 1 hour: 3600 seconds

• 1 day: 86400 seconds

• 2 weeks: 1209600 seconds

Since website content usually does not change constantly, a long TTL increases efficiency and reduces server load.

Default TTL for private cache (1800 seconds):This setting applies to pages displayed only to specific users (private cache). Default TTL is30 minutes.

Default homepage TTL (604800 seconds):The homepage is frequently visited, but changes rarely. A one-week TTL optimizes loading speed and reduces queries to the server.

Default TTL for Feed – 604800 seconds:This TTL setting applies to RSS/Atom Feeds. Feeds are frequently accessed by automated readers; if not cached, they consume significant resources. The cache will be automatically refreshed whenever there are new posts or comments.

Default TTL for REST API (604800 seconds):Control cache TTL for WordPress REST API requests. Caching reduces server-side API processing overhead.

TTL for pages by HTTP status code:Set TTL for pages returning error codes like404, 403, 500, or other status codes.

• 404 – Not Found:If the website receives many visits to invalid paths, temporarily caching 404 pages helps reduce load.

• 403 – Forbidden:This is typically a static page, so a long TTL can be set to increase efficiency.

• 500 – Server Error:Caching 500 error pages is not recommended as it may mask system errors and complicate troubleshooting.

Under cleanup options:Purge All on Upgrade (On): Automatically purges the cache of all pages when updating Themes, Plugins, or the WordPress version. This feature should be enabled because it is impossible to know what changes will occur between versions after an update.

Automatically purge cache on post publish/update (Default):

• Default: This feature should be kept default for websites of Dear customer because the website of Dear customer will also regularly update or post.

• All pages: if your website uses widgets that automatically link to posts on pages other than the front page or homepage, you should select All pages.

Old service (Off): If ON, the old copy of the cached page will be displayed to visitors until a new cached copy is available. This reduces server load for subsequent visits. If OFF, the page will be generated dynamically while visitors wait.

URLs pruned on schedule: Enter the URLs that need automatic cache purging at a specific time of day.

Scheduled cleanup: Select the cache clearing time for the URLs specified above.

Clean up all hooks (Default):The clean all action is only executed when WordPress runs hooks. Additionally, you can add hooks from plugins currently in use on your website or explore more hook code from WordPress.

Next is the exclusions section:
Do not cache URLs:Enter the URLs you want to exclude from the cache. Added URLs will always be dynamically generated and will not be cached.

Do not cache query strings: Dear customer can exclude URLs with certain query strings from the cache.

Do not cache categories: Enter the category path to exclude from the cache.

Do not cache tags: Enter keywords to exclude from the cache.

Do not cache Cookies:Enter the names of Cookies to exclude from the cache.
Useful for websites with user-customized features such as shopping carts, loyalty programs, or cookie-based custom content display.

Do Not Cache User Agents:Enter User Agents (devices or browsers) to exclude from caching.

Do Not Cache Roles (Administrator):Select user roles you do not want to cache. Typically, Administrator will be excluded, because when you update content or configurations, the system needs to display the new content immediately without going through cache.

Enable ESI (Off): Enable to cache public pages for logged-in users and serve the Admin Bar and Comment Form via ESI blocks. These two blocks will be unlocked unless enabled below.

Admin Bar Cache (On): Cache built-in Admin Bar ESI blocks.

Comment Box Cache (On): Cache built-in Comment Form ESI blocks.

ESI Nonces: List nonces one per line that will automatically be converted to ESI blocks. Wildcards are supported.

Browser Cache TTL (Off)Should be disabled by default; if Dear customer make sure that the Hosting in use utilizes Memcached or Redis and that the website of Dear customer has a lot of dynamic content or many data queries (Database), leave it turned on.

Method (Redis): Depending on the partner that Dear customer if you want to cache, suitable methods are Memcached or Redis.

Host (localhost): Server name or IP address of Memcached/LSMCD/Redis.

Port (6379): Default port for Memcached is 11211. Default port for Redis is 6379.

Default object discard time (360): Configure default Time to Live (TTL) for cached objects.

Username: Only available when SASL is installed.

Password: Specify the password used when connecting.

Redis database ID: Database to be used.

General group (Default): Network-level storage group, Dear customer can be added if you clearly understand this part. 

Do not cache group (Default):Default configuration, Dear customer can be added if you clearly understand this part. 

Persistent Connection (ON): Use keep-alive connections to increase cache performance speed.

WP-Admin Cache (On):If enabled, the WordPress administration will be accelerated, but there is occasionally a risk of retrieving stale data.

Temporary storage (Enabled): Temporarily stored in the database when WP-Admin Cache is OFF.

Browser Cache (On):When activated, the user's browser automatically caches static website resources (such as images, CSS, and JS). Consequently, subsequent visits will not need to redownload these files, speeding up website display.

Browser cache storage time (31557600 seconds):This is the duration for which the browser retains cached files before automatically refreshing them. During this period, users will experience faster page loads because old data does not need to be refetched.

Login cookie:This option is used to set up a dedicated login cookie, particularly useful when multiple web applications on the same virtual server have the LSCache plugin installed. Thanks to separate cookies, the system avoids login session conflicts between applications.

Improve HTTP/HTTPS compatibility (Currently disabled):If your website operates simultaneously on both HTTP and HTTPS protocols and experiences errors or unstable caching behavior, you can enable this option to improve synchronization between both versions.

Instant Click (Off):When enabled, any link that a user hovers over will be preloaded, enabling near-instantaneous access upon clicking. However, this preloading consumes extra server resources for pages the user might not actually click.

CDN

Cloudflare API (Disabled):Cloudflare works differently from regular CDNs. You do not need to enable CDN Mapping for Cloudflare. However, you can still manage Cloudflare cache directly within the plugin via the API.

Purge Cloudflare cache

• ON→ When you “Purge All” cache in LSCache, it also deletescache Cloudflare

• OFF→ LSCache only purges cache on the server, it DOES NOT purge cache on Cloudflare

Use CDN Mapping (Off):Enable this option if you want to configure a third-party CDN yourself.
Note:If you are usingCloudflare or QUIC.cloud, pleasedisablethis option.

HTML attributes to replace:Select the HTML attributes that CDN Mapping will replace with CDN URLs. Only listed attributes will be applied.

Original URL:Website URL—used by the plugin to determine which content should be offloaded to the CDN.

Includes directories:Specify which directories on the website will be processed and delivered by the CDN.

Exclude paths:Enter paths you do not want to serve through the CDN.

Image optimization

Send optimization request:Click to send the image optimization request. You can continue performing other actions while the LiteSpeed server processes it.
Note: Each send allows a maximum of200 images.

Optimization status:Clean up unfinished images when some images get stuck or never complete the optimization process. After cleaning up, you can resend the optimization request to reprocess those images.

Memory optimization: Sau khi Dear customer optimized their images, there may be three copies of each image stored on disk: the newly optimized version, the WebP version, and a backup of the original unoptimized version.

Image information:Rescan New Thumbnails is used when you have edited images in the library, preventing LSCache from detecting changes. This option rescans the image library to update all changes.

Optimization tools:Use original files to allow reusing unoptimized original images.

Use optimized files:Allows activating optimized images if you were previously using original images.

Destroy all optimization data:This feature will revert all images to their original state, removing all optimized images and related data.

Automated Cron Requirement (On):This feature automatically sends image optimization requests whenever you upload new images to the website.

Optimize Original Images (On):When enabled, the system backs up the original image, then optimizes and overwrites the image displayed on the website.

Delete original backup (Off):This option willpermanently deleteoriginal image after optimization completes.
Recommendation:should be disabled to keep backups in case original images need to be restored.

Losslessly Optimize (On):Compress images using a method that does not reduce image quality. Quality remains unchanged, but file size reduction is less than with the Lossy method.

Preserve EXIF/XMP data (On): This feature helps record photo metadata such as the camera device, capture date and time, image copyright, etc.

WebP format for Extra srcset (Enable):If the website uses the attributesrcset, this option will convert all images in srcset to the WebP format.

Control WordPress Image Quality (82):Configure WordPress image compression level. Value82means the compressed image retains a quality level of82%compared to the original image (100%).

Page optimization

CSS Minification (On):Enable this option to minify CSS files on the website, removing whitespace, comments, and unnecessary characters. This helps reduce file sizes and improve loading speed.

Combine CSS (ON):Combine all individual CSS files intoa single file, helps reduce the number of requests and improve page performance.

Generate UCSS (Off):Use QUIC.cloud service to generate UCSS (Unique CSS) to help eliminate unused CSS.
Disabled by default to avoid consuming service resources unnecessarily.

Inline UCSS (Off):Inline UCSS to reduce the number of files to load.
Note: This option is not automatically enabled for pages inGuest Mode.

Combine CSS and Inline CSS (ON):Combine both external and inline CSS into a single file when Combine CSS is enabled. This option helps maintain correct CSS specificity order, thereby minimizing styling issues during CSS combination.

Load CSS Asynchronously (On):Optimize CSS loading asynchronously to help pages display faster. This usually improves PageSpeed scores and user experience.

CCSS Per URL (Off):When disabled, CCSS is generated per Post Type rather than per URL. This significantly saves CCSS quota, but may cause styling issues if the website uses a Page Builder.

Inline asynchronous CSS library:Inline asynchronous CSS libraries to prevent blocking page rendering during load.

Font Display Optimization (Default):Add propertyfont-displayinto every rule@font-facebefore CSS is cached. This controls how fonts are displayed while downloading, helping reduce rendering delays or font flickering.

JS Minification (On):Enable this option to minify JavaScript files, removing whitespace, comments, and unnecessary characters. This reduces file size and increases page load speed.

Combine JS (ON):Combine all individual JS files into a single file, helping reduce the number of HTTP requests and improve website performance.

JS Combine External and Inline (On):When enabled, both external JS and inline JS will be combined. This option preservesJavaScript execution priority order, reducing UI or functional errors that may occur when enabling the “Combine JS” feature.

Defer JS Loading (Defer):This feature defers JavaScript loading until HTML has finished loading. Deferring JS increases initial load speed and improves PageSpeed scores. However, you should test carefully, as some website functions may not work properly if the page relies heavily on early-loaded JS.

HTML Minification (On):Enable this feature to minify HTML code on the website by removing whitespace, comments, and unnecessary characters. This reduces HTML file size and improves page load speed.

DNS prefetch:This option helps prefetch external domains. DNS prefetching reduces latency when visitors load resources from external links, thereby improving load speed.

Control DNS Prefetch (Enabled):This feature enables DNS prefetching for all URLs on the page, including images, CSS, JavaScript… As a result, resource loading times decrease and page performance improves.

Drop query strings (Off):This feature removes query strings (?v=123) from static resources like images, CSS, JS. This helps resources get cached more easily by browsers or proxy servers. However, to prevent display glitches when CSS/JS changes, this option is usually default todisable.

Load Google Fonts Asynchronously (Off):Allows loading Google Fonts asynchronously to prevent render-blocking and improve above-the-fold load speeds.

Remove Google Fonts (Off):This option will completely remove Google Fonts from the website. Suitable when you want to use system fonts or self-hosted fonts to reduce external requests.

Remove WordPress Emoji (On):Remove default WordPress Emoji scripts – originally used to support emojis on legacy browsers. Disabling this eliminates one JS request and slightly improves page load speed.

Remove Noscript tag (Off):This option will remove all tags

Lazy Load Images (ON):When enabled, images are downloaded only when the user scrolls to their position on the screen, reducing page load times and saving bandwidth.

Basic placeholder image:Allows using a base64-encoded image as a temporary placeholder while the main image loads, replacing the default gray background.

Responsive Placeholder (On):Create a placeholder sized correspondingly to the actual image based on width and height attributes, thereby reducing layout shifts while images are loading.

Placeholder response SVG:Allows specifying an SVG file as a local placeholder; this file is automatically converted to base64 format for direct embedding on the page.

Response placeholder color (#cfd4db):Set SVG colors as placeholders to match the color palette of the website interface.

Cloud LQIP Generator (Off):The QUIC.cloud service generates Low-Quality Image Placeholders (LQIP)—downscaled, blurred versions of original images—to enhance page load experience.

LQIP quality (4):Adjust the LQIP placeholder image quality; the larger the number, the sharper the placeholder image, but it also increases the file size.

LQIP Minimum Dimensions (150×150):An LQIP placeholder is only generated when both image width and height are greater than or equal to this value.

Generate LQIP in background (On):Automatically generate LQIP placeholder images in the background via cron, and use SVG images as placeholders if configured.

Lazy Load Iframes (ON):Only load iframes when users scroll to their location, helping reduce initial payload and improve page loading speed.

Add Missing Sizes (Enable):Automatically add width and height attributes to images, minimizing layout shifts during loading and improving CLS scores.

Viewport images:This feature helps fully load all images on the webpage when using Lazy Load. When enabled, it loads images completely without lagging, avoiding delayed image display or black placeholders during scrolling. This service also automatically detects images in the above-the-fold viewport and prioritizes loading them while bypassing offscreen images to optimize page speed.

Viewport images cron:When enabled, the system automatically runs a cron job to generate viewport images on a set schedule, automating image processing and reducing manual effort for administrators.

Do not apply Lazy Load to images:List of images exempt from lazy loading, typically site logos. You only need to enter paths here.

Exclude images by class from Lazy Load:Images containing these class names will not be lazy-loaded.

Lazy Load Image Parent Class Name Excludes:Images whose parent elements bear these class names will not trigger lazy loading.

Lazy Load Iframe Class Name Excludes:Iframes containing these class names will not use lazy loading.

Lazy Load Iframe Parent Class Name Excludes:Iframes whose parent elements contain these class names will not use lazy loading.

Lazy Load URI Excludes:Images and iframes on pages with URIs listed here will not use lazy loading. Enter each URI on a separate line.

Do not apply LQIP:The listed images will not be included in the Low-Quality Image Placeholder (LQIP) generation process.

Gravatar Cache (On):Allows caching Gravatar images on the server to boost loading speeds.

Gravatar cache refresh cron (Enabled):Automatically update and refresh Gravatar cache via scheduled cron.

Gravatar cache storage time (TTL – 604800):Set the duration (in seconds) that Gravatar images will be kept in cache before being refreshed.

JS Deferred Includes:List of files or inline JS code that will always have deferred loading applied. Enter each file name or URL on a separate line.

JS Excludes:JS files or code snippets listed here will not be minified or combined. Each line corresponds to a filename.

Defer JS / Defer Exclude:JS files in this list will not be deferred. Used for scripts that need to execute immediately to avoid UI or functionality issues.

Guest Mode JS Excludes:JS files entered here will not be affected by optimization when the page is running in Guest Mode.

URI Excludes:Paths added to this section will not be optimized or cached. Enter one URI per line.

Only optimize for visitors:When enabled, optimization applies only to non-logged-in guests. When disabled, optimization applies to all users.

Excluded Roles:Select user roles to exempt from any optimizations, typically Administrator to prevent issues while editing content.

CSS Excludes:CSS files or inline CSS code listed here will not be minified or combined. Each line is a filename or URL.

UCSS Inline Excluded Files:Entered CSS files or inline CSS snippets will not be processed by UCSS (UnCSS).

UCSS selector allowlist:List critical CSS selectors you wish to keep and prevent UCSS from purging during scanning. Enter one selector per line.

UCSS URI Excludes:Pages/paths listed here will not have UCSS generated. Add one URI per line.

Separate CCSS Cache for post types:Enter post type so that each item of that type has a separate critical CSS (CCSS) generated.

Separate CCSS Cache URIs:Add page paths with specific structures or CSS layouts so the system can generate dedicated CCSS, preventing display errors.

LiteSpeed Cache database optimization

Clear all:This option cleans all listed content — except for CSS/JS optimization and optimization tables. In other words, it cleans up almost all junk data at once.

Delete auto-drafts:Delete automatic draft saves (auto-drafts) created by WordPress, which are usually unnecessary.

Empty trashed posts/pages:Clean up all deleted posts or pages — permanently removing them from the database.

Delete comments marked as spam:Remove all comments marked as spam to keep comment data clean.

Empty trashed comments:Clean up all comments in the trash after they have been deleted or removed.

Delete trackbacks/pingbacks:If you do not need responses from other blogs/websites (trackbacks/pingbacks), select this to delete them and avoid redundant data.

Purge expired Transients:Transients are temporary cache data in the database. This option removes expired transients to keep the database clean and lightweight.

Purge all Transients:Purge all transients, whether expired or not — useful for completely cleaning internal cache. (Some transients will be recreated when revisiting pages, which is normal.)

Database table optimization:Use this option to restructure and optimize tables in the database, helping reduce fragmentation and improve query performance.

Maximum number of revisions (0): Specify the number of most recent revisions to keep when cleaning up revisions.

Revisions Max Age (0): Revisions newer than this number of days will be retained when pruning revisions.

LiteSpeed Cache Crawler

View the progress of various crawlers enabled for the website. Dear customer can track the progress of each crawler through the colored shapes in the Status column

Use the Reset Position button to restart the crawler from the beginning.

Use the Manual Run button to start the crawler without waiting for the cron job.

Status by color:

• Gray color: crawling pending: page is in the queue to be crawled.

• Green color: cache hit; the page was already stored in cache, so the crawler skipped it.

• Blue color: the page has not been cached, so the crawler cached it.

• Red: blacklist, unable to crawl page

Dear customer must submit a sitemap to refresh the map and crawl information.

This section displays URLs currently on the blacklist. From here, Dear customer can manually remove URLs from the blacklist using the button next to each entry.

Crawler (Off): Enabling this option will allow cron crawling. This feature requires high server resources so Dear customer should consider using this feature, as it may affect the website of Customer.

Information gathering interval (302400): Specify the interval when the crawler begins re-crawling the entire sitemap.

Server load limit (1): This setting serves as a way to prevent crawlers from consuming system resources. Once this limit is reached, the crawler will terminate instead of continuing to impact server performance.

Image optimization

Purge front page cache: This option helps Dear customer only purge homepage cache.

Clean up pages: This option helps Dear customer clear cache for pages on the website.

Purge All – LSCache: This option will clear all cache items associated with the current WordPress installation.

Purge All – CSS/JS Cache: This action will only purge all minified and combined CSS/JS entries.

Purge All – Opcode Cache: Clears opcode cache, not to be confused with LSCache; this is a separate cache. Opcode cache stores compiled PHP code, not full pages.

Purge all cache: Clears all cached entries related to this website, including other web applications. This action should only be used if everything is cached incorrectly.

Deleted by...: Select the options below and purge cache by: Category, Post ID, Tag, URL.

Export settings: This action will export all current LiteSpeed Cache settings and save them as a file.

Import settings: This action will import settings from a file and overwrite all current LiteSpeed Cache settings.

Reset all settings: This action will reset all settings to defaults.

Heartbeat: Should disable these features to reduce server resource load of Customer, when the server resources of Dear customer insufficient resources can lead to slower website performance. 

Control Frontend Heartbeat (Disabled):This option allows managing Heartbeat activity on the WordPress user interface.

Heartbeat Frontend TTL (0):Set the interval (seconds) between Heartbeat cycles on the frontend. WordPress allows 15–120 seconds. Set to 0 to completely disable Heartbeat in this area.

Control Backend Heartbeat (Disabled):Enable this option to adjust Heartbeat frequency in the WordPress admin area.

Heartbeat Backend TTL (0):Specify the number of seconds between each backend Heartbeat execution. The valid range is 15–120 seconds; set to 0 to disable.

Control Editor Heartbeat (Disabled):Allows controlling Heartbeat activity within the WordPress content editor.

Heartbeat Editor TTL (15):Set the interval (seconds) for Heartbeat in the editor. WordPress allows 15–120 seconds; set to 0 to disable completely.

Passwordless link: To grant wp-admin access to the LiteSpeed Support team, please generate a passwordless login link for the current logged-in user to be sent with the report.

Disable all features (Off):Enable this option when debugging the website in a state unaffected by caching or optimization features. Once testing is complete, disable this option again.

Debug Log (Off):Only enable when logging information is required for debugging. If the website has high traffic, you should also use the “Admin IP Address” option to prevent logs from bloating excessively.

Admin IP Address:Enter the administrator's IP address. This feature limits logging to only the admin's IP for easier tracking during debugging.

Drop Query String (Off):Shorten long query strings in logs to make them easier to read and track.

Debug URI includes:Only log the URLs listed here. URLs are matched against the server's REQUEST_URI variable.

Debug URI excludes:Do not log URLs in the exclusion list. Matching is also based on the REQUEST_URI variable.

After enabling the logging feature (Debug Log), Dear customer can view logs here in this tab. If the log contains too many old records, click the Clear Log button to remove all except the most recent group of entries.

This feature allows Dear customer opportunity to try out pre-release versions of LSCWP.

Use latest GitHub Master commit: this version is a beta release.

Use the latest WordPress version: to stop beta testing and revert to the current release from the WordPress Plugin directory.

CONCLUSION

Plugin LiteSpeed Cacheis one of the most powerful and comprehensive speed optimization tools for WordPress, helping improve website performance through intelligent caching, CSS/JS optimization, image handling, database cleanup, and numerous advanced features. When configured properly, your website will achieve faster load speeds, reduced server load, and an enhanced user experience.

In the guide above,CompanyVPTSdetailed each configuration section and clearly explained each option so that you can configure, control, and optimize your website most effectively. We always aim to deliver visual, easy-to-understand, and practical documentation to assist customers in running stable, fast, and secure websites.

If you encounter any difficulties while working with the LiteSpeed Cache plugin,VPTS Companyalways ready to support, advise, and accompany you to ensure optimal system performance.

VPTS – Comprehensive Digital Infrastructure Solutions Provider

VPTS Team Contact Information