LiteCache - LiteSpeed LScache for Enterprise eCommerce
LiteSpeed LScache based Page Cache for Magento 2
Replacement for LiteSpeed LiteMage and Varnish
Kitt Cache Crawler for Cache Warmup integrated
No Need for separate front Proxy
Unlimited and completely free Cache Hits
GUI Installer
60 seconds Installation without any additional Requirements
Extremely customizable
Free Updates and Support
Note: LiteCache for Magento is not a Magento Extension. LiteCache is a standalone Application that runs parallel to Magento, so don't try to install it as an Extension in Magento. This will fail! Download the .zip File, unzip it locally and read the install notes carefully.
What is LiteCache? LiteCache is neither an extension like LiteSpeed LiteMage nor is it a new type of page cache. Like LiteMage, LiteCache uses the LScache cache engine from the LiteSpeed web server. LiteCache is a standalone application that runs parallel to Magento 2. Despite functioning independently of Magento, LiteCache for Magento was programmed specifically for Magento 2 and only works with this version of Magento. Although LiteMage and LiteCache use the same LSWS cache engine, there are no other similarities.
Rather, LiteCache stands out from LiteMage in almost all respects and claims to be the better LScache solution. Consequently, LiteCache does not shy away from comparison to Varnish.
What is Kitt The Cache Crawler? Kitt, as the name suggests, is a cache warm-up crawler. Like LiteCache, Kitt for Magento 2 was specifically programmed for LScache, Magento 2 and LiteCache. Kitt and LiteCache together form the dream team for the LiteSpeed web server, LScache and of course for Magento 2. Kitt is also a standalone application, but for Magento 2 Kitt and LiteCache are an inseparable unit that have their home in one common control panel.
While Kitt offers numerous configuration options, LiteCache is the boss of both. This means that Kitt automatically adapts the configuration of LiteCache, which significantly simplifies administration, so that even inexperienced Magento users should not be overwhelmed.
When it comes to LiteSpeed and LScache, Kitt is the fastest cache warmer with the lowest resource consumption.
Magento 2 HTTP/2 Performance - Powered by LiteCache®
LiteSpeedLScache + LiteCache®
9273.2
NginxVarnish
3337.1
ApacheVarnish
2429.7
Request Per Second (10 Users)
LiteCache & Kitt Cache Crawler Requirements
LiteSpeed Enterprise (LSWS) or OpenLiteSpeed (OLS)
Magento 2 >= 2.64
PHP Version >= PHP 7.4 and < PHP 8.2
cURL
ionCube Loader (Version >11)
/proc/stat must be readable
/proc/cpuinfo must be readable.
sys_getloadavg()
Note: All listed requirements are mandatory. However, these are not special, but are usually present as standard.
Enable or Disable is not just a ON/OFF switch. If LiteCache is enabled or disabled all settings and modifications at certain files are either added or removed, so you can be shure that each modification is either shurely added or removed.
Default Public Cache TTL
Default Public Cache TTL determines the lifetime of the public cache. Public cache means the cache of users who are not logged in. If the cache has expired, the relevant cache files are automatically deleted in idle mode of the web server. There is therefore no need to manually delete the expired cache files.
Default Private Cache TTL
The Private Cache TTL behaves like the Public Cache TTL, but this setting refers to the cache of logged in users. Private cache means that every logged in customer has their own cache. The provision of the cache function is unique to LiteCache and is not supported by anyone, including LiteSpeed LiteMage
Default Frontpage TTL
The content of a homepage is updated very often. That's why the homepage needs a way to control the cache lifetime separately from other TTL settings.
Default Search Result TTL
As the first and so far only LiteSpeed LScache solution, LiteCache also enables the caching of search results, making repeated search queries available in a few milliseconds. This significantly puts the use of Elasticsearch into perspective, as LiteCache can deliver repeated searches up to 10 times faster. It therefore seems logical that the lifetime of the cache for search queries can be set separately.
Cache Mobile
If the content of your Magento shop differs when using different devices, i.e. desktop and mobile, then different cache aries are required. However, only if different code is delivered through PHP identification of the device. If this is the case, LiteCache provides the necessary Cache Vary.
GeoIP Cache Vary
If the LiteSpeed GeoIP Cache module is installed, the cache can be controlled individually depending on the user's location. This creates a separate cache copy depending on the location, so that it is also possible to provide location-dependent content with a page cache.
Accept Language Cache Vary
Many Magento shops are multilingual and provide language-dependent content via the detected browser language. In order for this detection to also work with a page cache, a cache variable is required for each supported language. LiteCache also provides the right solution for this requirement.
Cookie Cache Vary
Depending on the programming, cookies can influence the content displayed. If the content differs for a particular cookie but the URL is unchanged, a separate cache copy is also required for this, otherwise the changed content will not be displayed. With Cookie Cache Vary, the original dynamic content generation is retained, so that it is also possible to provide dynamically generated content with a page cache.
Freestyle Cache Vary
On the basis that LiteSpeed LScache is a so-called HTTP cache and the cache engine is provided via the LiteSpeed web server, this type of page cache allows a wide range of cache varieties as is known from the classic modRewrite rules. With the Freestyle Cache Vary setting, different cache rules can be defined almost endlessly.
Drop Query Strings
LiteSpeed LScache is known to be an HTTP or URL based page cache. This means that a cache copy is created for every URL. This also applies to URLs with GET parameters. If the content of a page does not change as a result of a GET parameter, then the additional cache copy is unnecessary. This is especially true for URLs requested from external sources such as Google Ads. With the setting "Drop Query Strings" the respective GET parameter is ignored and the cache copy of the URL without GET parameter is used.
Force Cache URIs
The "Force Cache URIs" function forces a URL to be cached, even though caching is disabled for a URL with the same name. This setting acts as an exception so that a URL is cached even though parts of the URL are defined as no-cache.
Excludes
Do not cache URI
A page cache has many advantages, but sometimes it is necessary to exclude certain URLs from caching. With one of the several exclude functions, LiteCache allows you to individually exclude the cache functions for specific URLs.
Do not cache Query Strings
As well as URI, GET parameters can also be excluded from caching. With this feature, LiteCache can be adapted even more to individual cache needs.
Do not cache Cookies
In certain cases it is also possible to exclude cookies from caching.
Do not cache User-Agent
For example, if you want to exclude certain bots or other user agents from the cache, then use this exclude function.
Do not cache IP Address
If you would like to exclude a single IP or even an entire Class C network from caching for certain reasons, the corresponding exclude function is also available for this purpose.
Delay
Kitt requests the URLs to be crawled not in series, i.e. serially, but in parallel, i.e. in multi-threaded mode. This means that even a very large number of URLs can be crawled or the cache warmed up in a very short time. For an optimal cache result, a short delay between the individual requests is required, which is set in microseconds. (1s = 1000000µs)
Threads
The number of simultaneous threads largely determines the crawl speed. However, this number also has a decisive influence on the server load. Even with a powerful dedicated server, a high number of threads does not mean fast crawling speed, as the quality of the cache result does not directly depend on the web server, but on PHP and MySQL. A smaller number of threads can end up being faster and the cache quality better.
Max Server Load
The Kitt Cache Crawler has dynamic load control management. This means that Kitt not only monitors the server load during crawling, but also regulates it if necessary, so that if the limit is exceeded, the number of simultaneous threads is reduced and the pause between threads is also increased until the limit is exceeded again. Kitt is currently the only cache crawler with this dynamic load control.
Limit
The number of URLs to crawl can be limited if necessary. This limitation can also be combined with the offset function if necessary.
Offset
See Limit setting.
Server IP Address
To warm up the cache, Kitt simulates conventional user requests. Therefore, Kitt is subject to the same network conditions as normal user requests. However, Kitt requires direct access to the host, bypassing a CDN node. It is therefore necessary to enter the public IP address of the origin host.
Logging
In order to obtain information about the crawl result, Kitt provides the cache inventory. However, the logging required for this must be activated.
cURL Debugging
Kitt uses cURL to warm up the cache. If it ever becomes necessary to debug the individual requests, this can be activated with cURL debugging.
Crawl Output
If Kitt is run manually in the console, the output for it can be activated if necessary. This will display the currently requested URLs, the transfer time and the current server load for each URL. However, activating the output function should not generally be activated as this can have a negative impact on the crawl speed.
Crawler Mode
If necessary, Kitt can be configured to purge the cache before warmup.
Cache Mode
The Cache Mode setting represents an undocumented feature of the LiteSpeed web server. This function influences the lifetime of the cache, so that when cache mode is activated, the TTL is extended by the set time. If cache mode is deactivated, the TTL expires according to the setting. In order to use this function, the LiteSpeed web server must be configured accordingly.
Follow Redirection
By default, Kitt does not follow any redirects. If there are redirects, it means that the sitemap contains incorrect URLs. If it is still necessary for Kitt to follow redirects, then this must be activated, but this will dramatically worsen the crawl speed.
Compression
LiteSpeed LScache stores the cache in individual static (text) files and are moderately compressed by default. However, this compression is not just about saving storage space. The type of compression corresponds to the same compression as is used for HTTP compression (gzip, deflate, brotli). If compression is activated, the data intended for transmission does not have to be compressed again and separately. On the one hand, this results in a reduction in the server load for the otherwise typical compression, but also in time savings, so that the loading time is improved. If compression is disabled, the LSWS creates an additional cache copy when a user uses accept encoding, which is usually the default. The compression function should therefore always be activated.
Most Wanted
The URLs Most Wanted (UMW) feature is a unique feature that is only available with the Kitt Cache Crawler. The UMW function is an alternative to the sitemap, which usually provides the basis for the URLs to be crawled. As the name of the UMW function suggests, this function records the URLs requested by natural users. The unique advantage in this feature is that it also records the URLs that are not normally included in the sitemap and therefore cannot warm up the cache for these URLs. The further advantage is that up to 70% of the total existing URLs do not have to be crawled, because up to 70% of all URLs in the site size are either never or only very rarely requested. So why waste resources crawling URLs if no one gets any use out of it?
Cache Mobile Vary
If the Cache Mobile Vary function is activated in the LiteCache settings, then this will be displayed in the Kitt settings. With the exception of the Cache Mobile Vary, the cache warmup for this Vary cannot be deactivated depending on the device.
Accept Language Cache Vary
As a mirror image of the LiteCache setting, the Kitt settings show the Accept Language Cache Vary, if activated. Depending on the language defined, you can determine whether the cache should be warmed up for each language if necessary. By default, warming up the cache is activated.
Cookie Cache Vary
The Cookie Cache Vary is displayed in the Kitt settings in accordance with the LiteCache settings. If a Cookie Cache Vary is defined in the LiteCache settings, then it is possible to control the cache warmup behavior in the Kitt settings.
Freestyle Cache Vary
The Freestyle Cache Vary behaves in the Kitt settings in the same way as all other Vary settings, so that the cache warmup behavior can be controlled depending on this.
Sitemaps
By default, the sitemap serves as the basis for the URLs to be crawled. It doesn't matter to Kitt whether the sitemap was created by Magento or it is a custom sitemap. As long as the sitemap is valid, any sitemap can be used.
Cache Inventory
The cache inventory shows the crawl result if logging is activated. This inventory shows exactly the cache status for each URL and also the cache status when using cache varieties. If necessary, the cache of individual URLs can be purged using the cache inventory. It is also possible to blacklist certain URLs so that the relevant URLs are excluded from crawling during the next crawl process.
URLs Most Wanted
If the URLs Most Wanted function is activated, the recorded URLs are displayed in detail in the UMW overview. In this overview, individual URLs can not only be deleted, but also blacklisted so that the relevant URLs are not crawled when using the UMW function.
This is why LiteCache and Kitt are unique
LiteCache - The one and only Page Cache Solution for MagentoLiteCache is currently the only LScache-based page cache solution for Magento 2 that can be adapted almost unlimitedly to individual needs. Even LiteSpeed doesn't even come close to offering the same range of functions as LiteMage.
No additional costs due to cache hits.When using LiteCache, there are no additional costs that would otherwise be due to the number of cache hits. Although LiteCache is oriented towards enterprise eCommerce platforms, a one-time payment makes it possible for smaller eBusiness projects to also benefit from the fastest page cache for Magento 2.
Replacement for Varnish and LiteMageLiteCache is not only a replacement for Varnish and LiteMage, but also outperforms both cache solutions in performance and functionality. In particular, the comparison to Varnish makes the use of Varnish unnecessary.
LiteCache saves MoneyLiteCache's requirements are so low that LiteCache and Magento can even be used on shared hosting. LiteCache does not require a front proxy or any other special hosting features. The only requirement is the LiteSpeed web server, although it can also be OpenLiteSpeed.
Easy InstallationSince LiteCache is a standalone application, the installation is separate and independent of Magento. This means that the otherwise typical and not always easy installation of extensions is no longer necessary. The installation can be carried out by inexperienced users in less than 60 seconds using its own graphical user interface.
Kitt crawls up to 200,000 URLs within 1 hourDepending on current Cache Status Kitt is able to warmup up to 200,000 URLs within 1 hour without heavy Load, even on Shared Hosting.
Dynamic Load ControlDon't care about the Load of your Server while Crawling. Kitt has a intelligent Load Control that dynamically reduces the Crawling Speed if the Load goes too high and encreases the Speed if the Load goes under the Limit.
Auto-Adjust ConfigurationKitt Cache Crawler comes with pre-configured Settings, that fits in most cases. So you don't have to learn which settings are the best. Each setting is also provided with recommendations that give you even more security when making any changes.
Available as Desktop Version and Version for Command Line Interface (Cron)Kitt contains 2 Versions. You can run Kitt either via the Control Panel or scheduled and regularly via a Cron Job
Tune-up SettingsKitt Cache Crawler is extremely flexible, so you can make numerous Fine-Tuning and Tuning Settings depending on the System Resources.
Cache InventoryThe Cache Inventory gives you detailed Information about the current Status of the Cache, which is automatically generated after each Crawling Session.
Crawling without TimeoutKitt is able to remove the known Limitations on the maximum Execution Time of Scripts without having to make any Changes to the Server Configuration. This also applies to Shared Hosting! If you use Control Panel Version, this Feature ensures that Kitt can complete his Job successfully.
URLs Most WantedURLs Most Wanted reduces cache warmup time and resources by up to 70% and dramatically offloads the cache warmup server.
Private Cache for Logged in UsersLiteCache is the only LScache based page cache for Magento 2 that enables the cache function in the form of a private cache for logged in users.
Still Questions?
We try very hard to give you as much information as possible. If you can't find the information you need or if you don't understand something, don't hesitate to ask us.