Kentico CMS 7.0 Context Help



Previous topic Next topic Mail us feedback on this topic!  


Previous topic Next topic JavaScript is required for the print function Mail us feedback on this topic!  


Allow GZip compression

Enables GZip compression of the output code of all pages rendered by Kentico CMS. The same result can be achieved by adding the following key to the appSettings section of the web.config file: <add key="CMSAllowGZip" value="true" />.

Server content caching

Cache page info (minutes)

Sets the number of minutes for which the system caches page information. This option caches page properties and metadata. Kentico CMS retrieves page information many times during the processing of a single page, so always set this value to at least 10 minutes!


When a page is modified, the system automatically clears the corresponding part of the page info cache, so the website will not display outdated information.

Cache content (minutes)

Sets the number of minutes for which all web parts/controls cache the content that they retrieve from the Kentico CMS database.


You can override this value for specific web part instances by setting their Cache minutes property. Using 0 as the value disables content caching for the given web part instance.


It is recommended to cache all possible content that is not modified often. The drawback of this option is that if content is modified, the changes appear on the live site only after the old version expires in the cache.

Use progressive caching

If checked, the system optimizes access to uncached data so that concurrent threads only use a single data access operation and share the results. This leads to better performance if the website is under a heavy load, without the drawback of not having the latest data available.

Server file caching

Cache images (minutes)

Sets the number of minutes for which the system caches image files on the server.


It is recommended to always use image caching. Kentico CMS automatically removes images from the cache if they are modified, so image caching cannot cause the website to display outdated content.

Maximum file size to cache

Specifies the maximum file size in kilobytes that is allowed to be cached.

Redirect files to disk

If checked, file requests are redirected to the corresponding physical file (if the requested file is stored in the file system).

File client caching

Client cache (minutes)

Sets the number of minutes for which client browsers are allowed to cache files.


If the value is 0, client caching for files is disabled.

Client cache must revalidate

If enabled, client browsers need to revalidate cached content by calling the server. If disabled, browsers do not perform server requests if the requested content is already cached.

Output caching

Enable output caching

If checked, the system allows output caching. Output cache stores the full HTML source of pages. If unchecked, output caching is disabled on the whole website.


To enable output caching for pages, configure the Output cache properties of individual documents in CMS Desk on the Properties -> General tab. Both the main website setting and document settings must be enabled to use output caching.

Cache output in file system (minutes)

Specifies the number of minutes for which the system stores output cache in the file system. This provides persistent cache storage in case of application restarts.


If not set, only the standard caching mechanism (in memory) is used. If you enter a value, the system checks both types of cache.


To enable output caching in the file system for pages, configure the Allow file system cache property of individual documents in CMS Desk on the Properties -> General tab.

Enable partial caching

If checked, the system allows partial caching of web parts and controls. The partial cache stores the HTML output of individual web part or control instances. If unchecked, partial caching is disabled on the whole website for all web parts.


By default, web parts do not use partial caching and you need to enable it for individual instances using their Partial cache minutes property.

Resources (global settings only)

Allow resource compression

If enabled, the system compresses JavaScript and CSS stylesheet web resources before sending them to the client browser. This reduces the amount of data that must be loaded. Uncompressed versions remain available for browsers that cannot process compressed data.


Minification of the given resource type must be enabled (via the Allow JavaScript/CSS minification settings) in order for compression to be applied.

Allow JavaScript minification

Indicates if JavaScript resources should be minified before they are served to the client browser. Minified code has a reduced size, which saves bandwidth and decreases response times, but may not be suitable for debugging.

Allow CSS minification

Indicates if CSS stylesheet resources should be minified before they are served to the client browser.

CSS Styles (global settings only)

Resolve macros in CSS

If checked, it will be possible to use macros in CSS stylesheets to dynamically insert the content of other stylesheets.


To insert this type of macro, add an expression into the code of a stylesheet according to the following format: {%CSS["<stylesheetname>"]%}


Warning: If you wish to disable this setting, it is first necessary to remove all occurrences of macros from your stylesheets. Unresolved macro expressions are not valid CSS code and as a result, the given stylesheets will not be processed correctly by browsers.

Allow CSS from components

If enabled, CSS styles defined for individual page components (e.g. web parts, page templates etc.) will automatically be requested by the page where they are placed. Otherwise it is necessary to either have all styles defined directly in the website's stylesheets, or to link the styles of the required components into the stylesheets via CSS macros.

Combine CSS from components

If enabled, pages will load the CSS styles of all contained components via a single request. Otherwise different types of components will each generate a separate request. The styles of multiple components of the same type (e.g. several web parts) are always retrieved by a single request.


Combining the CSS requests into one may improve the load time of individual pages and is recommended in most cases.


More resources can be found in:


Developer's Guide -> Development -> Caching and performance

Developer's Guide -> Development -> CSS stylesheets and design