Performance
General |
|
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) |
Number of minutes the page information should be cached for. This option is used for caching of page content and metadata. Since Kentico CMS often retrieves page information many times during the processing of a single page, it's actually a must to always set this value to at least 10 minutes! Kentico CMS automatically removes the cached page when it's modified, so it doesn't cause outdated content to be displayed. |
Cache content (minutes) |
Number of minutes content should be cached for. This option specifies that all web parts/controls should cache the content that they retrieve from Kentico CMS. You can override this value by setting the Cache minutes property of web parts to 0, which disables caching for the given control, or generally to some different number of minutes. It's recommended that you cache all possible content that is not modified too often. The drawback of this option is that when you modify some content, the changes appear on the live site only after the old version expires in the cache. |
Server file caching |
|
Cache images (minutes) |
This option is used only for caching of images and sets the number of minutes that the images should be cached for. It's recommended that you always use it. Kentico CMS automatically removes a cached image when it's modified, so it doesn't cause displaying of outdated content. |
Maximum file size to cache |
Specifies the maximum size of a file in kilobytes that is allowed to be cached. |
Redirect files to disk |
If checked, file requests are redirected to the corresponding physical file in the file system if possible. |
Client caching |
|
Client cache (minutes) |
Number of minutes for which content can be cached in the client browser. If the value is set to 0, client caching is disabled. |
Client cache must revalidate |
If enabled, content that is cached in the client browser must be revalidated by calling the server. If disabled, the browser will not have to perform server requests if the requested content is already cached. |
Output caching |
|
Enable output caching |
If checked, the output caching is enabled. If unchecked, no output caching is allowed on the whole site. The document settings still apply, both this settings and document settings must be enabled to use output cache. |
Cache output in file system (minutes) |
Specifies the amount of time for which the output cache should be stored in the file system to provide persistent cache storage on application restart. If not set, standard caching mechanism in memory is used. If set, the system checks both caches. |
Enable partial caching |
If checked, the partial caching of web parts is enabled. If unchecked, no partial caching is allowed on the whole site. The web part settings still apply, both this settings and web part settings must be enabled to use partial cache. |
Resources (global settings only) |
|
Allow resource compression |
If enabled, JavaScript and CSS stylesheet web resources will be compressed before they are sent to the client browser, which reduces the amount of data that must be loaded. Uncompressed versions will 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: