WP-Cache caching will also cache visits by unknown users if supercaching is disabled. It’s the most flexible caching method and slightly slower. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. This is mainly used to cache pages for known users, URLs with parameters and feeds. You can keep portions of your page dynamic in this caching mode. htaccess file doesn’t need to be changed. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. Supercached static files can be served by PHP and this is the recommended way of using the plugin. htaccess file which is risky and may take down your site if modified incorrectly. This does require the Apache mod_rewrite module (which is probably installed if you have custom s) and a modification of your. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This completely bypasses PHP and is extremely quick. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files.

The plugin serves cached files in 3 ways (ranked by speed): If they are logged in, or have left comments those details will be displayed and cached for them. Other visitors will be served custom cached files tailored to their visit. One cached file can be served thousands of times. Or users who have not viewed a password protected post.ĩ9% of your visitors will be served static html files.Users who have not left a comment on your blog.The static html files will be served to the vast majority of your users: After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.

This plugin generates static html files from your dynamic WordPress blog.

Super fast copier