[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fwdREYWRDFcbTkn9FAVYmSn_8AqlCTSVFun_790SrUFQ":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":25,"download_link":26,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30,"vulnerabilities":31,"developer":32,"crawl_stats":29,"alternatives":39,"analysis":137,"fingerprints":297},"db-cache-reloaded-fix","DB Cache Reloaded Fix","2.3","Ivan Kristianto","https:\u002F\u002Fprofiles.wordpress.org\u002Fivankristianto\u002F","\u003Cp>This plugin caches every database query with given lifetime. It is much faster than other html caching plugins and uses less disk space for caching. Now compatible with WordPress 3.1.\u003C\u002Fp>\n\u003Cp>This plugin is based on \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdb-cache-reloaded\u002F\" rel=\"ugc\">DB Cache Reloaded\u003C\u002Fa> by sirzooro. I patch it so it have WordPress 3.4 compatibility.\u003C\u002Fp>\n\u003Cp>I think you’ve heard of \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-cache\u002F\" rel=\"ugc\">WP-Cache\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fwp-super-cache\u002F\" rel=\"ugc\">WP Super Cache\u003C\u002Fa>, they are both top plugins for WordPress, which make your site faster and responsive. Forget about them – with DB Cache Reloaded your site will work much faster and will use less disk space for cached files. Your visitors will always get actual information in sidebars and server CPU loads will be as low as possible.\u003C\u002Fp>\n\u003Cp>This plugin is a fork of a \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdb-cache\u002F\" rel=\"ugc\">DB Cache\u003C\u002Fa> plugin. Because his author did not updated its plugin to WordPress 2.8, I finally (after almost three months since release of WP 2.8) took his plugin and updated it so now it works with newest WordPress version. Additionally I fixed few bugs, cleaned up the code and make it more secure.\u003C\u002Fp>\n\u003Cp>This plugin was tested with WordPress 2.8 and never. It may work with earlier versions too – I have not tested. If you perform such tests, let me know of the results.\u003C\u002Fp>\n\u003Cp>If you are using WordPress 2.9, please use DB Cache Reloaded version 2.0 or never – versions 1.x are not compatible with WordPress 2.9.\u003C\u002Fp>\n\u003Cp>If you are using WordPress 3.0, please use DB Cache Reloaded version 2.1 or never – earlier versions are not compatible with WordPress 3.0.\u003C\u002Fp>\n\u003Cp>For Web Developer:\u003C\u002Fp>\n\u003Cp>If you are a web developer fork me on [Github] (https:\u002F\u002Fgithub.com\u002Fivankristianto\u002FDB-Cache-Reloaded-Fix)\u003C\u002Fp>\n\u003Cp>Available translations:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>English\u003C\u002Fli>\n\u003Cli>French (fr_FR) – thanks \u003Ca href=\"http:\u002F\u002Fwww.inmotionhosting.com\u002F\" rel=\"nofollow ugc\">InMotion Hosting\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Polish (pl_PL)\u003C\u002Fli>\n\u003Cli>Italian (it_IT) – thanks \u003Ca href=\"http:\u002F\u002Fwww.iacchi.org\u002F\" rel=\"nofollow ugc\">Iacopo\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Portuguese Brazilian (pt_BR) – thanks Calebe Aires\u003C\u002Fli>\n\u003Cli>Belorussian (be_BY) – thanks FatCow\u003C\u002Fli>\n\u003Cli>Spanish (es_ES) – thanks Dasumo\u003C\u002Fli>\n\u003Cli>Dutch (nl_NL) – thanks Rene\u003C\u002Fli>\n\u003Cli>Turkish (tr_TR) – thanks wolkanca\u003C\u002Fli>\n\u003Cli>Japanese (jp) – thanks wokamoto\u003C\u002Fli>\n\u003Cli>German (de_DE) – thanks \u003Ca href=\"http:\u002F\u002Fgreatsolution.de\u002F\" rel=\"nofollow ugc\">Carsten Tauber\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Chinese (zh_CN and zh_TW) – thanks \u003Ca href=\"http:\u002F\u002Fneverweep.com\" rel=\"nofollow ugc\">企鹅君\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fdb-cache-reloaded-fix\u002Fchangelog\u002F\" rel=\"ugc\">Changelog\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"http:\u002F\u002Fgoo.gl\u002FUzwSf\" rel=\"nofollow ugc\">Blog Post\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>Other interesting stuff:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Check out the my other WordPress plugins or web development \u003Ca href=\"http:\u002F\u002Fgoo.gl\u002FOHQNc\" rel=\"nofollow ugc\">My Portfolio\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Want to optimize your WordPress blog? Check out the \u003Ca href=\"http:\u002F\u002Fgoo.gl\u002FQedtH\" rel=\"nofollow ugc\">WordPress Optimization Article\u003C\u002Fa> Guide!\u003C\u002Fli>\n\u003C\u002Ful>\n","The fastest cache engine for WordPress, that produces cache of database queries with easy configuration. Compatible with WordPress 3.4",2000,229802,86,12,"2017-11-28T08:10:00.000Z","3.4.2","3.0","",[20,21,22,23,24],"cache","caching","db-cache","performance","wp-cache","http:\u002F\u002Fwww.ivankristianto.com\u002Fweb-development\u002Fprogramming\u002Fdb-cache-reloaded-fix-for-wordpress-3-1\u002F1784\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdb-cache-reloaded-fix.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":34,"total_installs":35,"avg_security_score":36,"avg_patch_time_days":37,"trust_score":27,"computed_at":38},"ivankristianto",4,2510,87,30,"2026-04-03T21:31:40.836Z",[40,60,80,99,116],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":13,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":54,"tags":55,"homepage":56,"download_link":57,"security_score":58,"vuln_count":14,"unpatched_count":28,"last_vuln_date":59,"fetched_at":30},"wp-super-cache","WP Super Cache","3.0.3","Automattic","https:\u002F\u002Fprofiles.wordpress.org\u002Fautomattic\u002F","\u003Cp>This plugin generates static html files from your dynamic WordPress blog.  After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.\u003C\u002Fp>\n\u003Cp>The static html files will be served to the vast majority of your users:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Users who are not logged in.\u003C\u002Fli>\n\u003Cli>Users who have not left a comment on your blog.\u003C\u002Fli>\n\u003Cli>Or users who have not viewed a password protected post.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.\u003C\u002Fp>\n\u003Cp>The plugin serves cached files in 3 ways (ranked by speed):\u003C\u002Fp>\n\u003Col>\n\u003Cli>Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.\u003C\u002Fli>\n\u003Cli>Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.\u003C\u002Fli>\n\u003Cli>WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.\u003C\u002Fp>\n\u003Ch3>Recommended Settings\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Simple caching.\u003C\u002Fli>\n\u003Cli>Compress pages.\u003C\u002Fli>\n\u003Cli>Don’t cache pages for known users.\u003C\u002Fli>\n\u003Cli>Cache rebuild.\u003C\u002Fli>\n\u003Cli>CDN support.\u003C\u002Fli>\n\u003Cli>Extra homepage checks.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.\u003C\u002Fp>\n\u003Cp>Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.\u003C\u002Fp>\n\u003Cp>Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.\u003Cbr \u002F>\nEven with preload mode enabled cached files will still be deleted when posts are modified or comments made.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Active development of this plugin is handled \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Translation of the plugin into different languages is on the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-super-cache\" rel=\"nofollow ugc\">translation page\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>If you need more information than the following, you can have a look at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fwiki\" rel=\"nofollow ugc\">the wiki\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fwp-super-cache-developers\u002F\" rel=\"nofollow ugc\">Developer documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Preloading\u003C\u002Fh4>\n\u003Cp>You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.\u003Cbr \u002F>\nTo make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.\u003C\u002Fp>\n\u003Ch4>Garbage Collection\u003C\u002Fh4>\n\u003Cp>Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:\u003Cbr \u002F>\n1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.\u003Cbr \u002F>\n2. Scheduler. Setup how often garbage collection should be done.\u003Cbr \u002F>\n3. Notification emails. You can be informed on garbage collection job progress.\u003Cbr \u002F>\nThere’s no right or wrong settings for garbage collection. It depends on your own site.\u003Cbr \u002F>\nIf your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.\u003Cbr \u002F>\nIf your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.\u003C\u002Fp>\n\u003Cp>The cache directory, usually wp-content\u002Fcache\u002F is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.\u003C\u002Fp>\n\u003Ch4>CDN\u003C\u002Fh4>\n\u003Cp>A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fossdl-cdn-off-linker\u002F\" rel=\"ugc\">OSSDL CDN off-linker\u003C\u002Fa> has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support \u003Ca href=\"https:\u002F\u002Fwww.google.com\u002Fsearch?hl=en&q=%22origin+pull%22\" rel=\"nofollow ugc\">origin pull\u003C\u002Fa>. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.\u003C\u002Fp>\n\u003Cp>Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.\u003C\u002Fp>\n\u003Ch4>REST API\u003C\u002Fh4>\n\u003Cp>There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.\u003C\u002Fp>\n\u003Ch4>Custom Caching\u003C\u002Fh4>\n\u003Cp>It is now possible to hook into the caching process using the add_cacheaction() function.\u003C\u002Fp>\n\u003Cp>Three hooks are available:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.\u003C\u002Fli>\n\u003Cli>‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.\u003C\u002Fli>\n\u003Cli>‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>There is one regular WordPress filter too. Use the “do_createsupercache” filter\u003Cbr \u002F>\nto customize the checks made before caching. The filter accepts one parameter.\u003Cbr \u002F>\nThe output of WP-Cache’s wp_cache_get_cookies_values() function.\u003C\u002Fp>\n\u003Cp>WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>by putting your plugin in the wp-content\u002Fplugins\u002Fwp-super-cache-plugins directory, or\u003C\u002Fli>\n\u003Cli>by calling wpsc_add_plugin( $name ) where $name is the full filename and path to the plugin. You only need to call that function once to add it. Use wpsc_delete_plugin( $name ) to remove it from the list of loaded plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The cookies WP Super Cache uses to identify “known users” can be modified now by adding the names of those cookies to a list in the plugin configuration. Use wpsc_add_cookie( $name ) to add a new cookie, and wpsc_delete_cookie( $name ) to remove it. The cookie names also modify the mod_rewrite rules used by the plugin but I recommend using Simple mode caching to avoid complications with updating the .htaccess file.\u003Cbr \u002F>\nThe cookie name and value are used to differenciate users so you can have one cookie, but different values for each type of user on your site for example. They’ll be served different cache files.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fblob\u002F4cda5c0f2218e40e118232b5bf22d227fb3206b7\u002Fplugins\u002Fsearchengine.php\" rel=\"nofollow ugc\">plugins\u002Fsearchengine.php\u003C\u002Fa> as an example I use for my \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fno-adverts-for-friends\u002F\" rel=\"nofollow ugc\">No Adverts for Friends\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch3>Troubleshooting\u003C\u002Fh3>\n\u003Cp>If things don’t work when you installed the plugin here are a few things to check:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Is wp-content writable by the web server?\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fwp-cache-config.php ? If not, copy the file wp-super-cache\u002Fwp-cache-config-sample.php to wp-content\u002Fwp-cache-config.php and make sure WPCACHEHOME points at the right place.\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fadvanced-cache.php ? If not, then you must copy wp-super-cache\u002Fadvanced-cache.php into wp-content\u002F. You must edit the file and change the path so it points at the wp-super-cache folder.\u003C\u002Fli>\n\u003Cli>If pages are not cached at all, remove wp-content\u002Fadvanced-cache.php and recreate it, following the advice above.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Make sure the following line is in wp-config.php and it is ABOVE the “require_once(ABSPATH.’wp-settings.php’);” line:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_CACHE', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>Try the Settings->WP Super Cache page again and enable cache.\u003C\u002Fli>\n\u003Cli>Look in wp-content\u002Fcache\u002Fsupercache\u002F. Are there directories and files there?\u003C\u002Fli>\n\u003Cli>Anything in your php error_log?\u003C\u002Fli>\n\u003Cli>If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.\u003C\u002Fli>\n\u003Cli>The plugin does not work very well when PHP’s safe mode is active. This must be disabled by your administrator.\u003C\u002Fli>\n\u003Cli>If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the “www” prefix on the URL. You should choose one way and install the \u003Ca href=\"http:\u002F\u002Ftxfx.net\u002Fcode\u002Fwordpress\u002Fenforce-www-preference\u002F\" rel=\"nofollow ugc\">Enforce www preference\u003C\u002Fa> plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!)\u003C\u002Fli>\n\u003Cli>Private Server users at Dreamhost should edit wp-content\u002Fwp-cache-config.php and set the cache dir to “\u002Ftmp\u002F” if they are getting errors about increasing CPU usage. See this \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002F145895?replies=42\" rel=\"ugc\">discussion\u003C\u002Fa> for more.\u003C\u002Fli>\n\u003Cli>File locking errors such as “failed to acquire key 0x152b: Permission denied in…” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content\u002Fwp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.\u003C\u002Fli>\n\u003Cli>Make sure cache\u002Fwp_cache_mutex.lock is writable by the web server if using coarse file locking.\u003C\u002Fli>\n\u003Cli>The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it’s 404 or you don’t see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit \u002Fetc\u002Fhosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network\u002FInternet use. See http:\u002F\u002Fyoast.com\u002Fwp-cron-issues\u002F for more. A line like “127.0.0.1 localhost localhost.localdomain” is ok.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>127.0.0.1 example.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.\u003C\u002Fli>\n\u003Cli>The error message, “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content\u002Fadvanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content\u002Fadvanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content\u002Fplugins\u002Fwp-super-cache\u002F. If it is not correct the caching engine will not load.\u003C\u002Fli>\n\u003Cli>Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If supercache cache files are generated but not served, check the permissions on all your wp-content\u002Fcache\u002Fsupercache folders (and each of wp-content cache and supercache folders) and wp-content\u002Fcache\u002F.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>umask( 0022 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it’s “Off” or add this line to your .htaccess:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>php_flag zlib.output_compression off\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If that doesn’t work, add this line to your wp-config.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>ini_set('zlib.output_compression', 0);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>The “white screen of death” or a blank page  when you visit your site is almost always caused by a PHP error but \u003Ca href=\"http:\u002F\u002Fwww.johnberns.com\u002F2010\u002F03\u002F19\u002Fwp-super-cache-blank-page-problem-fixed\u002F\" rel=\"nofollow ugc\">it may also be caused by APC\u003C\u002Fa>. Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache.\u003C\u002Fli>\n\u003Cli>After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.\u003C\u002Fli>\n\u003Cli>If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?\u003C\u002Fli>\n\u003Cli>Your front  …\u003C\u002Fli>\n\u003C\u002Fol>\n","A very fast caching engine for WordPress that produces static html files.",1000000,62208732,1341,"2025-11-11T16:21:00.000Z","6.9.4","6.7","7.2",[20,21,23,24,41],"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.0.3.zip",95,"2022-10-03 00:00:00",{"slug":61,"name":62,"version":63,"author":64,"author_profile":65,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":70,"num_ratings":71,"last_updated":72,"tested_up_to":52,"requires_at_least":73,"requires_php":74,"tags":75,"homepage":18,"download_link":77,"security_score":58,"vuln_count":78,"unpatched_count":28,"last_vuln_date":79,"fetched_at":30},"breeze","Breeze Cache","2.4.1","Cloudways","https:\u002F\u002Fprofiles.wordpress.org\u002Fcloudways\u002F","\u003Cp>Breeze is a free, simple (yet powerful) and user-friendly caching plugin developed by the Cloudways team. It offers various options to optimize WordPress site performance at various levels. It works equally great with WordPress, WordPress with WooCommerce and WordPress Multisite.\u003C\u002Fp>\n\u003Cp>Breeze excels in the following areas:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Performance:\u003C\u002Fstrong> Breeze improves website speed and resource optimization. Other features include file level cache system, database cleanup, minification, support for Varnish cache and simplified CDN integration options.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Convenience:\u003C\u002Fstrong> Breeze is easy to install and configure directly from WordPress. Configuring Breeze is easy and most of the default options work well right out of the box. The recommended settings should work on all your WordPress websites seamlessly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Simplicity:\u003C\u002Fstrong> Breeze is designed to be simple for all users. Just install and activate the plugin and you’ll see the results instantaneously.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>What makes Breeze Cache Plugin awesome is that it comes with builtin support for Varnish. If Varnish is not installed on your servers, Breeze will utilize its internal cache mechanism to boost up your WordPress site performance.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>FEATURES\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Seamless integration with Varnish Cache for efficient content delivery. No manual adjustments needed – all settings come pre-configured for your convenience.\u003C\u002Fli>\n\u003Cli>Optimize performance using Cloudflare’s caching capabilities. No specific Breeze configurations are needed – it works out of the box.\u003C\u002Fli>\n\u003Cli>Effortlessly integrate your preferred Content Delivery Network (CDN) for global content distribution with Breeze instead of using the the CDN providers’ plugins.\u003C\u002Fli>\n\u003Cli>Trim WordPress database bloat effortlessly. Breeze’s Database Options optimize and declutter your database, boosting performance by removing unneeded data like post revisions and trashed content.\u003C\u002Fli>\n\u003Cli>Take command over caching exclusions. With Breeze, you have the power to prevent specific URLs, JS files, and CSS files from being cached.\u003C\u002Fli>\n\u003Cli>Achieve smaller page sizes and faster load times through HTML, CSS, and JavaScript minification, including inline CSS and JavaScript minification.\u003C\u002Fli>\n\u003Cli>Load images when they’re visible, not all at once, for faster webpage performance by implementing lazy loading for images.\u003C\u002Fli>\n\u003Cli>Load JS files with deferred loading, enhancing overall performance.\u003C\u002Fli>\n\u003Cli>Supercharge your site’s speed with Breeze’s advanced preloading features: load fonts early, quicken link clicks, and enhance DNS requests for a seamless user experience.\u003C\u002Fli>\n\u003Cli>Master real-time interactions with Breeze’s Heartbeat API management. Fine-tune notifications, sales data, autosaves, and more to optimize WordPress website performance by adjusting API call frequencies.\u003C\u002Fli>\n\u003Cli>Effortlessly manage Breeze settings using Import\u002FExport. Download your configurations as a .json file for backup, or effortlessly import existing settings to quickly fine-tune your optimization.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Support:\u003C\u002Fstrong> We love to provide support! Post your questions on the WordPress.org support forums, or if you are a Cloudways Customer you may ask questions on the \u003Ca href=\"https:\u002F\u002Fcommunity.cloudways.com\u002F\" rel=\"nofollow ugc\">Cloudways Community Forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cp>PHP 7.4, PHP 8 recommended for better performance, WordPress 6.0+\u003C\u002Fp>\n","Breeze is a caching plugin developed by Cloudways. Breeze uses advance caching systems to improve site loading times exponentially.",400000,13597399,72,125,"2026-03-03T09:14:00.000Z","6.0","7.4",[20,21,76,23,24],"cdn","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbreeze.2.4.1.zip",8,"2026-02-18 15:43:14",{"slug":81,"name":82,"version":83,"author":84,"author_profile":85,"description":86,"short_description":87,"active_installs":88,"downloaded":89,"rating":90,"num_ratings":91,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":74,"tags":95,"homepage":18,"download_link":97,"security_score":98,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"serve_static","Serve Static – Automatic WordPress Static Page generator","2.4","Rajin Sharwar","https:\u002F\u002Fprofiles.wordpress.org\u002Frajinsharwar\u002F","\u003Cp>Serve Static provides a very efficient, simple and fast way of implementing static page caching in WordPress.\u003Cbr \u002F>\nIt will generate static HTML copies of your webpages which will be then served using your server rewrite rules. This feature will bypass the whole PHP process and render only a simple HTML file without having to interect with the PHP, or MySQL for getting your page’s design or content.\u003C\u002Fp>\n\u003Cp>This plugin is really handy and helpful if your webpages are mainly static, like websites of Blogs, portfolios, company portfolios, service, and many more. This plugin doesn’t support any dynamic content caching, that means, all none of your dynamic content will be showing in the frontend, rather, a static version of that content will be showing.\u003C\u002Fp>\n\u003Cp>This plugin also comes with home-made HTML, CSS and JS minification features, which you can use to auto-minify the static files. This ensures more lightness of the HTML pages, and more boost to your page speed. Also, you can auto-warm the cache using the Warm feature, which will stimulate a visit on all your pages, to create the static files before they are served to your visitors.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>After activating the plugin, it will try to modify your .htaccess file. If this is not possible for some reason, make sure to enter the rules by yourself. NOTE: without these .htaccess rules, the static files won’t be served or created. Note that, this is only applicable if you are using a Apache\u002FLitespeed server.\u003C\u002Fp>\n\u003Cpre>\u003Ccode># BEGIN Serve Static Cache\nRewriteEngine On\nRewriteBase \u002F\nRewriteCond %{HTTP_COOKIE} !(^|;\\s*)wordpress_logged_in_.*$ [NC]\nRewriteCond %{REQUEST_URI} !^\u002F(elementor|vc_row|fl_builder|fl-theme-builder) [NC]\nRewriteCond %{REQUEST_URI} !^\u002Fwp-admin\u002F [NC]\nRewriteCond %{REQUEST_METHOD} GET\nRewriteCond %{QUERY_STRING} ^$ [NC]\nRewriteCond %{DOCUMENT_ROOT}\u002Fwp-content\u002Fserve-static-cache\u002F$1\u002Findex.html -f\nRewriteRule ^(.*)$ \u002Fwp-content\u002Fserve-static-cache\u002F$1\u002Findex.html [L]\n# END Serve Static Cache\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you the website installed on a sub-folder, like such that “https:\u002F\u002Ftest.com\u002Fdomain1”, is your main domain of your WordPress site, you need to use a different .htaccess code. The plugin will automatically do that for you, but incase you need to do it manually, below is the format you need to follow.\u003C\u002Fp>\n\u003Cpre>\u003Ccode># BEGIN Serve Static Cache\nRewriteEngine On\nRewriteBase \u002F\nRewriteCond %{HTTP_COOKIE} !(^|;\\s*)wordpress_logged_in_.*$ [NC]\nRewriteCond %{REQUEST_URI} !^\u002F(elementor|vc_row|fl_builder|fl-theme-builder) [NC]\nRewriteCond %{REQUEST_URI} !^\u002Fwp-admin\u002F [NC]\nRewriteCond %{REQUEST_METHOD} GET\nRewriteCond %{QUERY_STRING} ^$ [NC]\nRewriteCond \"WP_CONTENT_DIR\"\u002Fserve-static-cache\u002F\"sub-folder domain without slashes\"\u002F$1\u002Findex.html -f\nRewriteRule ^(.*)$ \u002F\"sub-folder domain without slashes\"\u002Fwp-content\u002Fserve-static-cache\u002F\"sub-folder domain without slashes\"\u002F$1\u002Findex.html [L]\n# END Serve Static Cache\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>The value of the WP_CONTENT_DIR should be something like: “\u002Fhome\u002Ftest.com\u002Fpublic_html\u002Fstaging\u002Fwp-content”\u003Cbr \u002F>\nThe value of the “sub-folder domain without slashes” should be your folder where WordPress is installed. So, if the WordPress is installed in “https:\u002F\u002Ftest.com\u002Fstaging”, you should enter “staging”.\u003C\u002Fp>\n\u003Cp>When using a nginx server, make sure to add the following rules:\u003C\u002Fp>\n\u003Cpre>\u003Ccode># BEGIN Serve Static Cache\nlocation \u002F {\n    if ($http_cookie !~* \"wordpress_logged_in_\") {\n        set $cache_uri $request_uri;\n\n        if ($request_uri ~* \"^\u002F(elementor|vc_row|fl_builder|fl-theme-builder)\") {\n            set $cache_uri \"null cache\";\n        }\n\n        if ($request_uri ~* \"^\u002Fwp-admin\u002F\") {\n            set $cache_uri \"null cache\";\n        }\n\n        if ($request_method = GET) {\n            set $cache_uri \"null cache\";\n        }\n\n        if (-f $document_root\u002Fwp-content\u002Fserve-static-cache$cache_uri\u002Findex.html) {\n            set $cache_file $document_root\u002Fwp-content\u002Fserve-static-cache$cache_uri\u002Findex.html;\n        }\n\n        if ($cache_file) {\n            rewrite ^ \u002Fwp-content\u002Fserve-static-cache$cache_uri\u002Findex.html break;\n        }\n    }\n}\n# END Serve Static Cache\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>This plugin creates static HTML versions of your pages\u002Fposts, or literally any custom post types, and serves them to your non-logged-in visitors. This is an awesome way to make your website blazing fast, and not even one request is made to PHP to request your pages.\u003C\u002Fp>\n\u003Cp>Anytime a Static page\u002Fpost\u002Fany custom post type is updated, the cache of that specific page is automatically cleared, and regenerated. So, you do not have to worry about regenerating the cache eac time after making changes to your content.\u003C\u002Fp>\n\u003Cp>This plugin is also well-integrated with frontend post rating plugins as well, so that when any rating is added, the cache gets regenerated automatically. If you are using any rating plugins that are not working with this plugin, kindly let me know in the support forum.\u003C\u002Fp>\n\u003Cp>This plugin heavily relies on CRON to process it’s functionalities. So please make sure either your server-level cron or WordPress Cron is running and working. If not, this plugin will show errors in the Admin Notices to help you direct to the problem. If there are still many issues, kindly share in the plugin support thread.\u003C\u002Fp>\n\u003Cp>By default, this plugin automatically works with Apache and Litespeed servers, and everywhere .htaccess rules is functional. But to make this plugin work with NGINX, you will be needing to add some rules to your nginx.conf or site.conf file. An appropiate admin notice will be shown to you accordingly, kindly follow those instructions.\u003C\u002Fp>\n\u003Cp>This plugin is supposed to work with all the form builder plugins like WP Forms, Ninja Forms. If you face any issues while using any form plugin, kindly let me know in the thread, and I will try to make it compitable.\u003C\u002Fp>\n\u003Ch4>Performance\u003C\u002Fh4>\n\u003Cp>Converting your website to a static webpage can drastically improve your performance and page speed. Serve Static eliminates all requests made to your database and ultimately reducing the first time to byte, total blocking time and many more.\u003C\u002Fp>\n\u003Cp>This is especially impactful for websites that have mainly static pages, and use long pages with a lot of graphs, sliders, and other load-heavy resources like animations.\u003C\u002Fp>\n\u003Ch4>Reduce hosting bandwidth\u003C\u002Fh4>\n\u003Cp>Using Serve Static to serve static HTML pages of your website really cuts a great cost in your bandwidth usage, as this doesn’t hit the MySQL server for your visitors, but instead serves delivers a cached, minified HTML copy. This releases much of your cost, alongside the page boost.\u003C\u002Fp>\n\u003Cp>We are working on features like “hosting your Static pages in a third party CDN, and serving those to your visitors”. If you are interested to see this feature in soon, let me know by opening a supprt thread!\u003C\u002Fp>\n\u003Ch3>NOTE\u003C\u002Fh3>\n\u003Cp>Caching is fully disabled for Administrators, or any logged-in users. Static Cache will only be served to logged-out visitors of your site.\u003C\u002Fp>\n\u003Cp>Note that, the Static Cache can only be regenerated by using the buttons in the admin toolbar, or in the Settings page. After the cache is Flushed, the cache is NOT regenerated when someone visits the pages. This is done so that none of the personalized content gets saved in the HTML caches.\u003C\u002Fp>\n\u003Cp>This plugin may not work as expected with a caching plugin like WP Rocket or W3 Total Cache. So make sure the URLs of the static pages are excluded from the specific plugins.\u003Cbr \u002F>\nFor example, when using WP Rocket, you need to navigate under Settings > WP Rocket > Advanced Rules > Never Cache URLs, and enter the URLs to the pages you want to serve as Static.\u003Cbr \u002F>\nWhen using W3 Total Cache, navigate under Performance > Page cache > Advanced > Never cache the following pages.\u003C\u002Fp>\n","Serve Static is a static HTML page generator WordPress plugin to create and serve static copies of your existing web pages to avoid PHP\u002FDB load.",100,5265,90,10,"2025-02-08T20:00:00.000Z","6.7.5","5.0",[20,21,23,96,24],"serve-static","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fserve_static.2.4.zip",92,{"slug":100,"name":101,"version":102,"author":103,"author_profile":104,"description":105,"short_description":106,"active_installs":88,"downloaded":107,"rating":88,"num_ratings":108,"last_updated":109,"tested_up_to":110,"requires_at_least":111,"requires_php":18,"tags":112,"homepage":114,"download_link":115,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-nav-menu-cache","WP Nav Menu Cache","2.2","Md Jahidul Islam","https:\u002F\u002Fprofiles.wordpress.org\u002Fonetarek\u002F","\u003Cp>“\u003Cstrong>\u003Ca href=\"http:\u002F\u002Fonetarek.com\u002Fmy-wordpress-plugins\u002Fwp-nav-menu-cache\u002F\" rel=\"nofollow ugc\">WP Nav Menu Cache\u003C\u002Fa>\u003C\u002Fstrong>” plugin help you to make your WordPress dynamic navigation menu to a static menu. For each page visit WordPress run some MySQL query and complex PHP codes to generate navigation menu that you are using on front-end. Your menu content is not being changed until you change that manually. So why do you need to use your server resource on every page visit to generate a menu? This plugin saves your dynamic menus into some separate static HTML files. When you add, edit or remove any menu item using dashboard then this plugin update its cached files. When a menu is called from website front-end then this plugin stops WordPress to generate that newly and serve from the previouly saved static file. This process reduces some MySQL query , saves your server resource and increases page speed.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Exclude any theme location from caching you don’t want to cache any menu of\u003C\u002Fli>\n\u003Cli>Exclude any menu you don’t want to cache\u003C\u002Fli>\n\u003Cli>Choose wheather this plugin will cache each menu individually for each post\u002Fpage or any visited url.\u003C\u002Fli>\n\u003C\u002Ful>\n","Create cache for dynamically generated navigation menu HTML and serve from a static file. It reduces some MySQL queries and increases page speed.",5353,3,"2023-01-18T13:49:00.000Z","6.1.10","3.8.0",[20,21,23,113,24],"web-performance-optimization","http:\u002F\u002Fonetarek.com\u002Fmy-wordpress-plugins\u002Fwp-nav-menu-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-nav-menu-cache.2.2.zip",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":48,"downloaded":124,"rating":125,"num_ratings":126,"last_updated":127,"tested_up_to":52,"requires_at_least":128,"requires_php":54,"tags":129,"homepage":133,"download_link":134,"security_score":135,"vuln_count":108,"unpatched_count":28,"last_vuln_date":136,"fetched_at":30},"wp-optimize","WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance","4.5.0","David Anderson \u002F Team Updraft","https:\u002F\u002Fprofiles.wordpress.org\u002Fdavidanderson\u002F","\u003Cp>MORE THAN A CACHING PLUGIN\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.teamupdraft.com\u002Fwp-optimize?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=wp_optimize&utm_creative_format=description\" rel=\"nofollow ugc\">WP-Optimize\u003C\u002Fa> is trusted by more than 1 million WordPress website\u003C\u002Fstrong> owners to \u003Cstrong>boost performance\u003C\u002Fstrong> and \u003Cstrong>reduce page load times\u003C\u002Fstrong> to improve your site’s \u003Cstrong>user experiences\u003C\u002Fstrong> and \u003Cstrong>SERP rankings in Google.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>It does this in four clever ways:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>1. It caches your site\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Caching is the process of storing a temporary HTML version of your site on the server so it can be retrieved more quickly for the user.\u003C\u002Fp>\n\u003Cp>It’s a sure-fire way to ensure web pages load at lightning-fast speed. Turn it on in just one click.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. It compresses images\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Large images can really impact page speed load times. WP-Optimize makes it easy to identify and compress images to your preferred lossy \u002F lossless settings in a couple of clicks.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. It cleans the database\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Your WordPress database stores everything that you need, plus some things that you don’t. WP-Optimize cleans and optimizes the database to speed up your site and save server resources.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. It minifies\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>On top of its three main features, WP-Optimize Cache also has the more advanced minification feature.\u003C\u002Fp>\n\u003Cp>Together with caching, minification dramatically improves performance and page speed load time.\u003C\u002Fp>\n\u003Ch3>1. CACHE YOUR SITE\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Turn on caching in just one click:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WP-Optimize automatically and optimally configures itself for your WordPress site. Turn it on in one-click or refine its settings if you prefer.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>More cache features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Cache preloading:\u003C\u002Fstrong> This feature emulates a visit to your site, meaning cached files are served straight away, speeding up your site from the very first visit.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>GZIP Compression:\u003C\u002Fstrong> When the server isn’t configured to do so, WP-Optimize delivers HTML, CSS and JS files  to the user’s browser as smaller, compressed files, reducing the size of pages and style sheets by up to 90%!\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Preload key requests:\u003C\u002Fstrong> Recommended by Google to improve page speed times. Critical resources (things like font files) get loaded first, so the page loads much faster \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Use cache settings to:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Serve cached content to logged in users:\u003C\u002Fstrong> Turn this on if content stays the same for logged in users (or turn on and exclude URLs where content does change e.g. my account areas).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Exclude content from cache:\u003C\u002Fstrong> Exclude by URL, conditional tags, browser agent strings or list cookies that should prevent caching when set (advanced user settings).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Deliver device-specific cache:\u003C\u002Fstrong> Serve separate cache files to desktop and mobile devices . This ensures that responsive features e.g. desktop and mobile menus are cached separately and served correctly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>User per role cache:\u003C\u002Fstrong> Useful if your website delivers different content to different user roles. e.g. an e-commerce site that displays different content to resellers or consumers \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>User specific cache:\u003C\u002Fstrong> Serves separate cache files to individual users. Useful for websites with personalised content e.g. Learning management systems \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Cache purging permissions:\u003C\u002Fstrong> Select which user roles are allowed to purge the cache e.g. admin only or perhaps a ‘teacher’ role in an LMS setting only \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>2. COMPRESS IMAGES\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Lossy or lossless compression options:\u003C\u002Fstrong> Choose between maximum space saving, best image quality or somewhere in-between.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>WebP conversion:\u003C\u002Fstrong> Recommended by Google, WebP can achieve up to 34% smaller file sizes compared to JPEG and up to 26% compared to PNG.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Auto-compress:\u003C\u002Fstrong> Check a box and every new image you upload will automatically be compressed to your preferred lossy \u002F lossless settings.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Bulk compression:\u003C\u002Fstrong> Compress every existing image on your site with the press of a button.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Restore original:\u003C\u002Fstrong> Gone too far? Revert images back to their original in one click.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Retain EXIF image data:\u003C\u002Fstrong> Check a box to retain EXIF image data during compression.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Lazy Load:\u003C\u002Fstrong> Webpages load much faster by loading web parts gradually, when they’re needed vs simultaneous loading of everything, all at once \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Delete orphaned images:\u003C\u002Fstrong> Identify and delete unused images from your WordPress website, saving disk space \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Delete unused image sizes:\u003C\u002Fstrong> WordPress creates multiple sizes for every uploaded image causing the uploads folder to become bloated. Scan for image sizes not in use and remove them to save further disk space \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3. CLEAN AND OPTIMIZE THE DATABASE\u003C\u002Fh3>\n\u003Cp>Cleans-up database tables, post revisions, auto draft posts, trashed posts, spam, trashed comments and more. Choose what to optimize or it’s one click to clean out the lot.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Schedule clean-ups:\u003C\u002Fstrong> So you can set and forget. Choose from daily, weekly, fortnightly or monthly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Flexible clean-up schedules:\u003C\u002Fstrong> You may wish to optimize database tables more frequently than you remove unapproved comments (for example). Choose the specific time and day when tasks should run \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Retain a set number of weeks’ data during clean-ups:\u003C\u002Fstrong> Just in case you need to retrieve something.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Back up before clean-ups:\u003C\u002Fstrong> If you delete something you shouldn’t, restore it in a couple of clicks with UpdraftPlus.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Power tweak – Turbo boost for WooCommerce:\u003C\u002Fstrong>  Unique to WP-Optimize, this power tweak boosts performance by replacing a slow query in WooCommerce with two much more efficient queries. E-commerce sites transacting high numbers of orders stand to gain here \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Power tweak – Boost performance by indexing the postmeta table:\u003C\u002Fstrong> This unique power tweak works by allowing the WordPress postmeta table to be indexed, improving performance \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>4. MINIFY AND COMBINE HTML, CSS AND JAVASCRIPT\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Minify in just one click:\u003C\u002Fstrong> Minifies HTML, JavaScript and CSS. Toggle on or off or customise each one under ‘settings’.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Customise minification:\u003C\u002Fstrong> Minify only (removing unnecessary code e.g line breaks and white spacing) or minify and merge. Apply the same or different settings to HTML, CSS and JavaScript.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Asynchronous loading:\u003C\u002Fstrong> Choose non-critical CSS and JavaScript files to load in the background and independently of other resources e.g. analytics or pixel scripts. Loading asynchronously eliminates render blocking and improves page speed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Exclude files from being minified:\u003C\u002Fstrong> Specify CSS and JavaScript files to exclude from minification.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Optimize fonts:\u003C\u002Fstrong> Optimize Font Awesome and Google Fonts. Inline the font files, inherit from CSS settings or load CSS \u002F Javascript asynchronously instead.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Preload assets:\u003C\u002Fstrong> WP-Optimize visits each web page on your site so the code is minified and preloaded for real life users, right from their very first visit.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Preload key requests:\u003C\u002Fstrong> Recommended by Google to improve page speed times. Critical resources (things like font files) get loaded first, so the page loads much faster.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>WHY WP-OPTIMIZE?\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>It’s brought to you by \u003Ca href=\"https:\u002F\u002Fwww.teamupdraft.com?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=teamupdraft&utm_creative_format=description\" rel=\"nofollow ugc\">TeamUpdraft\u003C\u002Fa>, the team behind the world’s most trusted backup, migration and restoration plugin.\u003C\u002Fli>\n\u003Cli>It’s easy to use.\u003C\u002Fli>\n\u003Cli>It packs a punch for a free plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>WP-Optimize brings the best cache and optimization technology together into one single, seamless plugin to make your WordPress site fast, lean and efficient.\u003C\u002Fp>\n\u003Ch3>PREMIUM FEATURES AT A GLANCE\u003C\u002Fh3>\n\u003Cp>Our free version of WP-Optimize Cache is great, but we also have an even more powerful \u003Ca href=\"https:\u002F\u002Fwww.teamupdraft.com\u002Fwp-optimize\u002Fpricing?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=premium_version&utm_creative_format=description\" rel=\"nofollow ugc\">Premium version\u003C\u002Fa> with extra features that offer the ultimate in freedom and flexibility:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Multisite Support:\u003C\u002Fstrong> extends database optimisations so they function for multiple WordPress sites at a time. If you manage more than one website, you will need WP-Optimize Cache Premium.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Flexibility and Control:\u003C\u002Fstrong> gives you the power to optimize select individual tables or a particular combination of tables on one or more WordPress websites, rather than having to optimize all database tables.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deleting unused and unwanted images:\u003C\u002Fstrong> removes orphaned images from your WordPress site, plus images of a certain, pre-defined size.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sophisticated Scheduling:\u003C\u002Fstrong> offers a wide range of options for scheduling automatic optimization. Specify an exact time and run clean-ups daily, weekly, fortnightly or monthly and perform any number of additional once off optimizations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Seamless Graphical User Interface:\u003C\u002Fstrong> for superb clarity in scheduling and managing of multi-site optimizations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP-CLI support:\u003C\u002Fstrong> provides a way to manage optimizations from command-line interface if you have lots of sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lazy Loading:\u003C\u002Fstrong> load only the images and part of a web-page when it is visible to the user so they can see something very quickly.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optimization Preview:\u003C\u002Fstrong> gives users the ability to preview, select and remove data and records available for optimization from the database.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Preload key requests:\u003C\u002Fstrong> preload assets such as web fonts and icon fonts, as recommended by Google PageSpeed Insights.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Premium support\u003C\u002Fstrong> – caching is one of the most complex things you can do for a website, so premium support offers you peace of mind there’s someone to talk quickly to if you need any technical answers or help configuring the optimizations of cache settings for your website.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>Translators are welcome to contribute to the plugin. Please use the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-optimize\" rel=\"nofollow ugc\">WordPress translation website\u003C\u002Fa>.\u003C\u002Fp>\n","Get caching and more with this powerful cache plugin. Cache, optimize images, clean your database and minify for maximum performance.",54516561,96,2561,"2026-02-11T11:20:00.000Z","4.9",[20,21,130,131,132],"image-cache","minify","performance-cache","https:\u002F\u002Fteamupdraft.com\u002Fwp-optimize","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-optimize.4.5.0.zip",97,"2025-05-12 00:00:00",{"attackSurface":138,"codeSignals":221,"taintFlows":285,"riskAssessment":286,"analyzedAt":296},{"hooks":139,"ajaxHandlers":215,"restRoutes":216,"shortcodes":217,"cronEvents":218,"entryPointCount":28,"unprotectedCount":28},[140,145,149,153,156,159,162,165,168,171,174,177,180,184,189,192,195,198,201,204,208,212],{"type":141,"name":142,"callback":142,"file":143,"line":144},"filter","query_vars","db-cache-reloaded.php",84,{"type":146,"name":147,"callback":147,"file":143,"line":148},"action","init",102,{"type":146,"name":150,"callback":151,"priority":28,"file":143,"line":152},"publish_post","dbcr_clear",106,{"type":146,"name":154,"callback":151,"priority":28,"file":143,"line":155},"edit_post",107,{"type":146,"name":157,"callback":151,"priority":28,"file":143,"line":158},"delete_post",108,{"type":146,"name":160,"callback":151,"priority":28,"file":143,"line":161},"trackback_post",110,{"type":146,"name":163,"callback":151,"priority":28,"file":143,"line":164},"pingback_post",111,{"type":146,"name":166,"callback":151,"priority":28,"file":143,"line":167},"comment_post",112,{"type":146,"name":169,"callback":151,"priority":28,"file":143,"line":170},"edit_comment",113,{"type":146,"name":172,"callback":151,"priority":28,"file":143,"line":173},"wp_set_comment_status",114,{"type":146,"name":175,"callback":151,"priority":28,"file":143,"line":176},"delete_comment",116,{"type":146,"name":178,"callback":151,"priority":28,"file":143,"line":179},"switch_theme",117,{"type":146,"name":181,"callback":182,"file":143,"line":183},"clean_cache_event","hourly_clean",119,{"type":146,"name":185,"callback":186,"priority":187,"file":143,"line":188},"wp_footer","loadstats",999999,122,{"type":146,"name":190,"callback":190,"file":143,"line":191},"admin_notices",126,{"type":146,"name":193,"callback":193,"file":143,"line":194},"admin_menu",132,{"type":146,"name":196,"callback":151,"priority":28,"file":143,"line":197},"added_option",137,{"type":146,"name":199,"callback":151,"priority":28,"file":143,"line":200},"updated_option",138,{"type":146,"name":202,"callback":151,"priority":28,"file":143,"line":203},"deleted_option",139,{"type":146,"name":205,"callback":206,"file":143,"line":207},"all","all_actions",142,{"type":146,"name":190,"callback":209,"file":210,"line":211},"_dbcr_admin_notice","db-module-wrapper.php",227,{"type":146,"name":190,"callback":209,"file":213,"line":214},"db-module.php",383,[],[],[],[219],{"hook":181,"callback":181,"file":143,"line":220},155,{"dangerousFunctions":222,"sqlUsage":242,"outputEscaping":245,"fileOperations":283,"externalRequests":28,"nonceChecks":108,"capabilityChecks":28,"bundledLibraries":284},[223,227,230,232,235,238,240],{"fn":224,"file":143,"line":225,"context":226},"unserialize",74,"$this->config = unserialize( @file_get_contents( WP_CONTENT_DIR.'\u002Fdb-config.ini' ) );",{"fn":224,"file":228,"line":155,"context":229},"db-functions.php","$result = unserialize( stream_get_contents( $f ) );",{"fn":224,"file":228,"line":170,"context":231},"$result = unserialize( $result );",{"fn":224,"file":210,"line":233,"context":234},103,"$this->dbcr_config = unserialize( @file_get_contents( WP_CONTENT_DIR.'\u002Fdb-config.ini' ) );",{"fn":224,"file":210,"line":236,"context":237},240,"$dbcr_cached = unserialize( $dbcr_cached );",{"fn":224,"file":213,"line":239,"context":234},212,{"fn":224,"file":213,"line":241,"context":237},396,{"prepared":243,"raw":28,"locations":244},2,[],{"escaped":34,"rawEcho":246,"locations":247},17,[248,251,253,255,257,259,261,263,265,267,269,271,273,275,277,279,281],{"file":143,"line":249,"context":250},427,"raw output",{"file":143,"line":252,"context":250},464,{"file":143,"line":254,"context":250},473,{"file":143,"line":256,"context":250},507,{"file":143,"line":258,"context":250},508,{"file":143,"line":260,"context":250},510,{"file":143,"line":262,"context":250},518,{"file":143,"line":264,"context":250},519,{"file":143,"line":266,"context":250},521,{"file":143,"line":268,"context":250},534,{"file":143,"line":270,"context":250},535,{"file":143,"line":272,"context":250},537,{"file":143,"line":274,"context":250},601,{"file":210,"line":276,"context":250},220,{"file":210,"line":278,"context":250},222,{"file":213,"line":280,"context":250},376,{"file":213,"line":282,"context":250},378,20,[],[],{"summary":287,"deductions":288},"The \"db-cache-reloaded-fix\" plugin v2.3 exhibits a generally strong security posture with no known vulnerabilities or CVEs in its history. The static analysis reveals good practices in SQL query handling, with all queries utilizing prepared statements. The plugin also demonstrates an awareness of potential security issues through the presence of nonce checks and a limited number of file operations.  The absence of external HTTP requests further reduces its attack surface. However, the analysis does flag the use of the `unserialize` function, which, if handled improperly, can lead to serious security vulnerabilities. While the taint analysis did not reveal any flows, the presence of `unserialize` is a point of concern that warrants careful code review.  The plugin's lack of recorded vulnerabilities is a positive indicator, but the identified use of `unserialize` without further context on its sanitization or usage within the plugin necessitates caution.",[289,291,294],{"reason":290,"points":78},"Use of unserialize function",{"reason":292,"points":293},"Low percentage of properly escaped output",5,{"reason":295,"points":293},"No capability checks","2026-03-16T18:29:12.086Z",{"wat":298,"direct":305},{"assetPaths":299,"generatorPatterns":302,"scriptPaths":303,"versionParams":304},[300,301],"\u002Fwp-content\u002Fplugins\u002Fdb-cache-reloaded-fix\u002Fdbcr.css","\u002Fwp-content\u002Fplugins\u002Fdb-cache-reloaded-fix\u002Fdbcr.js",[],[301],[],{"cssClasses":306,"htmlComments":307,"htmlAttributes":310,"restEndpoints":311,"jsGlobals":312,"shortcodeOutput":313},[],[308,309],"\u003C!-- BEGIN DB CACHE RELOADED STATS -->","\u003C!-- END DB CACHE RELOADED STATS -->",[],[],[],[]]