No, your website dashboard pages are not cached. The cache functionality is only meant to cache frontend pages.

You can generate a separate cache by selecting ”Generate separate files for mobile devices” in the page cache settings. This cache setting is only necessary if you use a specific theme for mobile devices, or for certain AMP plugins.

There is no limit to the number of pages you can cache. The only limit is the space on your server and the maximum number of subdirectories allowed by your server, as caching will write files in subdirectories following the permalink structure.

If you were to reach a caching limit, it probably means that your server is not fit for the size of your website and caching needs.

The cached page is sent to the user before most of your website is loaded. The add-on aren’t loaded yet, making it impossible for them to change the cached content at every request.

No, caching will actually reduce the load on your server, by reducing the amount of PHP and mysql used. You might see a peak in resource usage when using the cache preloader, as this functionality will create the cache files for all your pages in a short amount of time. But once this is done, performance should increase and the load on your server will decrease. Every single major site uses caching to serve cached pages faster by using fewer resources.

To prevent a page from being cached, you can add the URL to the field “URLs to exclude from cache” in the cache “Advanced settings” tab. If you are developing a plugin and want to prevent a page from being cached, you can define the “DONOTCACHEPAGE” constant on the pages you need. Any request where “DONOTCACHEPAGE” is defined will not be cached.

Add /.+ to the cache option “URLs to exclude from cache” on the advanced settings tab.

Choosing a frequency for the cache preloading schedule will depend on factors such as the frequency at which the website content is updated, the number of pages in the cache, the resources of the server and more.

For example a site with hundreds of pages will require more resources to preload its cache. So choosing a high frequency will mean that the cache will be recreated often, and the resource usage will be higher.

On a website where updates aren’t as frequent, you can even disable the cache preloading schedule, or set a high cache lifespan and set the cache preloading schedule to follow it.

Usually, a page is cached when a user visits it. So the first user visiting won’t be served a cached version of the page, and will wait longer than the next users. The cache preloading functionality will go through all your pages and posts, and simulate a visit by a user, allowing  Syspro Website Optimize to cache the pages before anyone visits them. Your first visitor will thus be served a cached version of the page, increasing its performance.

Yes, when using our website’s commenting system, your users will still be able to post comments. Every time a comment is approved, the cache for that page or post will be cleared, allowing the next visitor to see an up to date list of comments.

No, if your website works properly, Syspro Website Optimize will be able to cache your pages and posts.

If cache is enabled, and in order to see if your page is cached, use the “View Source” function in your web browser to view the page source. However, note that if you are using a further service that minifies HTML (e.g. Cloudflare). Also note that if you do not preload the cache, a page or post will have to be visited once for the cache file to be generated.

You think your site is fast without caching? A caching add-on will make your website even faster. A faster cached website will increase SEO, it will improve your visitors experience. Caching will also save your server’s resources.

“Caching”, from Wikipedia: “In computing, a cache is a hardware or software component that stores data so that future requests for that data can be served faster; the data stored in a cache might be the result of an earlier computation or a copy of data stored elsewhere. A cache hit occurs when the requested data can be found in a cache, while a cache miss occurs when it cannot.” — Syspro Website Optimize cache does this by saving the page computed by your website on the disk. When a user visits a page, Syspro Website Optimize will serve the cached page before your website is loaded. If the page wasn’t cached before, it will be computed by your website, and Syspro Website Optimize will then save the result to the cache.

This depends on your setup (theme, number and quality of add-on used, etc…), but generally, caching will make the biggest visible difference to your website’s performance.

Not unless you have an existing backup. Please ensure that you make a backup of your entire database before using Syspro Website Optimize for the first time, and when you upgrade to a major new version of it.

Yes; optimizing does not involve any “tricks” or poking around in dangerous ways. It involves running routine clean-up operations using well-defined, common MySQL commands. Nevertheless, we always recommend backups, which cover every possibility; not just database malfunctions, but hackers, human errors, etc.

This is a “how long is string?” sort of question. It depends completely on your site – how big it is, how many users interact on it, how long it has been running, and when you last optimised it. However, the savings and speed-ups can be substantial; it is always worth making sure that your database is optimised.

Our caching tests and feedback from real-world users show that the caching feature alone can make your site faster than any other cache add-on or optimization. See these speed test results.