[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f4y36W9wy2qw08csVo6cHEz5pfgMtlHFO5RSMzN6Sz8w":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":13,"last_updated":14,"tested_up_to":15,"requires_at_least":16,"requires_php":17,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28,"vulnerabilities":29,"developer":30,"crawl_stats":27,"alternatives":38,"analysis":143,"fingerprints":176},"simple-cache-killer","Simple Cache Killer","1.0.2","John Cummings","https:\u002F\u002Fprofiles.wordpress.org\u002Fjcummings1974\u002F","\u003Cp>** For Multisite\u002FNetwork Users **\u003C\u002Fp>\n\u003Cp>I wrote this plugin because of several situations I’ve run in to running a multisite network where I’ll want to include\u003Cbr \u002F>\ncaching for WordPress sites in most cases, but might need to exclude one of the sites on the network from that caching.\u003C\u002Fp>\n\u003Cp>By activating this plugin and checking the different caching options, requests to that sites pages\u002Fposts can be instructed\u003Cbr \u002F>\nnot to cache site content without disrupting the caching strategy in place for other sites.\u003C\u002Fp>\n\u003Cp>** For single site installations **\u003C\u002Fp>\n\u003Cp>This plugin will still be useful for single site installations where the site administrator may not have access to the web server\u003Cbr \u002F>\nto specify the types of HTTP caching headers that are returned on each request.  By allowing you to specify and rewrite the HTTP caching\u003Cbr \u002F>\nheaders at the site level, you’ll no longer need access to the web server in order to make sure visitors are always served fresh\u003Cbr \u002F>\ncontent.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Bug Reports or Feature Requests\u003C\u002Fstrong>\u003Cbr \u002F>\nhttps:\u002F\u002Ftrello.com\u002Fb\u002FzLViVgjx\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Follow me on Twitter\u003C\u002Fstrong>\u003Cbr \u002F>\nhttps:\u002F\u002Ftwitter.com\u002Fjcummings1974\u003C\u002Fp>\n","Allows users to specify that requests to their content not be cached in any way, easily from within the Wordpress admin.",10,2200,0,"2014-09-08T16:51:00.000Z","4.0.38","3.0.1","",[19,20,21,22,23],"cache","cache-control","caching","meta-http-equiv","pragma-no-cache","http:\u002F\u002Fwww.jcummings.net","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsimple-cache-killer.zip",85,null,"2026-03-15T15:16:48.613Z",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},"jcummings1974",3,120,90,30,87,"2026-04-04T10:44:52.446Z",[39,58,79,103,123],{"slug":20,"name":40,"version":41,"author":42,"author_profile":43,"description":44,"short_description":45,"active_installs":46,"downloaded":47,"rating":48,"num_ratings":49,"last_updated":50,"tested_up_to":51,"requires_at_least":52,"requires_php":17,"tags":53,"homepage":56,"download_link":57,"security_score":26,"vuln_count":13,"unpatched_count":13,"last_vuln_date":27,"fetched_at":28},"Cache-Control","2.2.5","Dan","https:\u002F\u002Fprofiles.wordpress.org\u002Fgeekysoft\u002F","\u003Cp>Good caching policies is one of performance’s best friends, and it can be your new best friend too. Get friendly with intermediary and browser caches by taking control over your WordPress powered website’s HTTP \u003Ccode>Cache-Control\u003C\u002Fcode> headers.\u003C\u002Fp>\n\u003Cp>This is not a caching plugin in itself, but will enable you to leverage existing standard compliant caching systems better. You can set different policies for different kinds of pages to suite your website’s needs. The Cache-Control for WordPress plugin allows you to set different policies for shared\u002Fintermediary and private caches. The plugin sets some sensible defaults for a medium traffic blog that publishes an update or two per week.\u003C\u002Fp>\n\u003Cp>You can safely set long \u003Ccode>Cache-Control\u003C\u002Fcode> times as the \u003Ccode>max-age\u003C\u002Fcode> values is lowered automatically before a scheduled post is about to be published.\u003C\u002Fp>\n\u003Cp>Private pages (logged in users, the admin interface, etc.) will not be cached.\u003C\u002Fp>\n\u003Cp>The plugin has \u003Ca href=\"https:\u002F\u002Fwww.ctrl.blog\u002Fentry\u002Fwp-cache-control-documentation.html\" rel=\"nofollow ugc\">extensive documentation\u003C\u002Fa>.\u003C\u002Fp>\n","Configurable HTTP Cache-Control response headers for webpages generated by WordPress.",1000,98695,100,6,"2019-08-30T11:50:00.000Z","5.2.24","4.4.1",[20,21,54,55],"http","performance","https:\u002F\u002Fwww.ctrl.blog\u002Fentry\u002Fwordpress-cache-control-plugin.html","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-control.2.2.5.zip",{"slug":59,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":13,"num_ratings":13,"last_updated":68,"tested_up_to":69,"requires_at_least":70,"requires_php":71,"tags":72,"homepage":17,"download_link":75,"security_score":76,"vuln_count":77,"unpatched_count":77,"last_vuln_date":78,"fetched_at":28},"cache-control-by-cacholong","Cache control by Cacholong","5.4.1","Preliot","https:\u002F\u002Fprofiles.wordpress.org\u002Fpreliot\u002F","\u003Cp>“Cache control by Cacholong” plugin automates purging of Nginx Pagespeed cache and Nginx FastCGI cache on your Nginx server(s). It is a backend plugin that is able to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Purge Nginx Pagespeed cache and\u002For Nginx FastCGI cache.\u003C\u002Fli>\n\u003Cli>Purge cache automatically, manually, with WordPress cronjobs and WP-CLI.\u003C\u002Fli>\n\u003Cli>Purge caches on one or more servers (See hosts.json section for more details).\u003C\u002Fli>\n\u003Cli>Use commandline (WP-CLI) to purge caches or reset to factory settings.\u003C\u002Fli>\n\u003Cli>Remove id tag from stylesheet link tags, in order to allow Nginx Pagespeed to combine stylesheets.\u003C\u002Fli>\n\u003Cli>Allow purging of other cached items (see Settings > Cache control).\u003C\u002Fli>\n\u003Cli>Inform user of purge status.\u003C\u002Fli>\n\u003Cli>Support for single site and network sites\u003C\u002Fli>\n\u003Cli>Support for WP-CLI\u003C\u002Fli>\n\u003Cli>Support for WPML (including language negotiation type domain)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>When will it purge?\u003C\u002Fh4>\n\u003Cp>This plugin will work with default and custom post types. It will purge on a save, regular update, quick edit update, slug change, delete and undelete. The user is informed with one or more messages.\u003Cbr \u002F>\nThere are a few caveats:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>When a user is using the Gutenberg editor, purge messages will not be displayed.\u003C\u002Fli>\n\u003Cli>When the user uses “Quick edit” and “Updates” the post, no messages will be displayed, because there’s no page refresh. Those messages will be shown on the next request. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>It is possible to purge with WordPress cronjobs. Adjust the ‘Cronjob settings’ to perform a daily purge of caches.\u003C\u002Fp>\n\u003Cp>You can also purge items manually. Go to the WordPress dashboard and navigate to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Settings > Cache control > purge single item\u003C\u002Fli>\n\u003Cli>Settings > Cache control > purge all caches\u003C\u002Fli>\n\u003Cli>Admin Toolbar > purge all caches\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>File with hosts (JSON):                 File with information about one or more hosts for this WordPress installation. See hosts.json section for more details. \u003C\u002Fli>\n\u003Cli>Pagespeed optimized CSS:                Remove ID tag from all WordPress stylesheet link tags to improve Nginx Pagespeed caching. Will only work on frontend.\u003C\u002Fli>\n\u003Cli>Purge settings default post types:      Select one or more options when purging a default post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.\u003C\u002Fli>\n\u003Cli>Purge settings default custom type(s):  Select one or more options when purging a custom post type. Possible to purge post url (default), home page, all connected WordPress categories or all caches.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Cronjob Settings\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Cronjob purging:                        Enable or disable cronjob purging. \u003C\u002Fli>\n\u003Cli>Cronjob time of each day:               Enter HH:MM in 24 hour notation for cronjob time of day. Will fallback to 00:00 when wrong format is given.\u003C\u002Fli>\n\u003Cli>Purge caches                            Select caches to purge on given cronjob time. \u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>hosts.json\u003C\u002Fh4>\n\u003Cp>Hosts.json is a JSON file with information about one or more servers for this WordPress installation. Remember that this file must contain information about all servers, including the\u003Cbr \u002F>\none with this plugin. Default path is: wp-content\u002Fuploads\u002Fcacholong-cache-control\u002Fhosts.json.\u003C\u002Fp>\n\u003Cp>Here is an example of a hosts.json file:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"servers\":\n    [\n        {\"name\": \"server1\", \"ip\": \"127.0.0.1\", \"pagespeed\": true, \"fastcgi\": false},\n        {\"name\": \"server2\", \"ip\": \"127.0.0.2\", \"pagespeed\": false, \"fastcgi\": true},\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Each line contains information about one server. Parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>name (string)\u003Cbr \u002F>\nName of host, something to identify this server.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>ip (string)\u003Cbr \u002F>\nIP address of server or full url. Format: scheme:\u002F\u002Fhost:port\u002Fpath\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>pagespeed (bool)\u003Cbr \u002F>\nServer uses Nginx Pagespeed (true) or not (false)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>fastcgi (bool)\u003Cbr \u002F>\nServer user Nginx FastCGI (true) or not (false)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>When there is no hosts.json or the path is invalid, this plugin assumes the following:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>{\"servers\":\n    [\n        {\"name\": \"localhost\", \"ip\": \"127.0.0.1\", \"pagespeed\": true, \"fastcgi\": true}\n    ]\n}\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>How does it work\u003C\u002Fh4>\n\u003Cp>“Cache control by Cacholong” empties partial or full cache for Nginx Pagespeed and FastCGI cache. WordPress HTTP API is used to make (post) request to\u003Cbr \u002F>\nspecific urls to trigger purges. Based on the http header responses this plugin determines if a purge is successful or not. The user is informed with messages, which are loaded after a purge and page refresh.\u003C\u002Fp>\n\u003Cp>There are several settings to tweak purging, see Settings > Cache control.\u003C\u002Fp>\n\u003Ch4>WP-CLI\u003C\u002Fh4>\n\u003Cp>There are several commands available for the commandline with wp-cli. Commands generate text output which can be suppressed with –quiet. When an error occurs, text will always be displayed.\u003C\u002Fp>\n\u003Ch4>WP-CLI exit codes\u003C\u002Fh4>\n\u003Cp>Exit codes are 0 (no errors) or 1 (generic error).\u003C\u002Fp>\n\u003Ch4>WP-CLI examples\u003C\u002Fh4>\n\u003Cp>Purge command with all arguments:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge [--cache=\u003Ccache>] [--ips=\u003Cips>]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx FastCGI:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=fastcgi\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx Pagespeed:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=pagespeed\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge all caches:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=all\nwp cacholong_cc purge\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge Nginx Pagespeed cache for ip address 127.0.0.1 and 127.0.0.2:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --cache=pagespeed --ips=127.0.0.1,127.0.0.2\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Purge all caches for ip address 127.0.0.1 and 127.0.0.2:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc purge --ips=127.0.0.1,127.0.0.2\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Factory reset options for given site_id or current blog if no site_id is given:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp cacholong_cc factory_reset [--site_id=site_id]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Debug\u003C\u002Fh4>\n\u003Cp>Plugin will log basic purge information when WP_DEBUG is true (can be set in wp-config.php). Logs information in file wp-content\u002Fcacholong-cache-control.log.\u003Cbr \u002F>\nPlugin will log wp_remote_request details when CACHOLONG_CACHE_DEBUG_HTTP_API_REQUEST is true (can be set in wp-config.php). Logs information in file wp-content\u002Fcacholong-cache-control.log.\u003C\u002Fp>\n","“Cache control by Cacholong” is a cache control plugin for one or more Nginx servers.",500,6645,"2021-07-20T12:01:00.000Z","5.7.15","4.3.1","5.6",[19,20,21,73,74],"cacholong","pagespeed","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcache-control-by-cacholong.zip",43,2,"2025-04-01 00:00:00",{"slug":80,"name":81,"version":82,"author":83,"author_profile":84,"description":85,"short_description":86,"active_installs":87,"downloaded":88,"rating":89,"num_ratings":90,"last_updated":91,"tested_up_to":92,"requires_at_least":93,"requires_php":94,"tags":95,"homepage":99,"download_link":100,"security_score":101,"vuln_count":32,"unpatched_count":13,"last_vuln_date":102,"fetched_at":28},"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.",1000000,54516561,96,2561,"2026-02-11T11:20:00.000Z","6.9.4","4.9","7.2",[19,21,96,97,98],"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",{"slug":104,"name":105,"version":106,"author":107,"author_profile":108,"description":109,"short_description":110,"active_installs":87,"downloaded":111,"rating":112,"num_ratings":113,"last_updated":114,"tested_up_to":92,"requires_at_least":115,"requires_php":94,"tags":116,"homepage":118,"download_link":119,"security_score":120,"vuln_count":121,"unpatched_count":13,"last_vuln_date":122,"fetched_at":28},"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.",62208732,86,1341,"2025-11-11T16:21:00.000Z","6.7",[19,21,55,117,104],"wp-cache","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.0.3.zip",95,12,"2022-10-03 00:00:00",{"slug":124,"name":125,"version":126,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":131,"downloaded":132,"rating":133,"num_ratings":134,"last_updated":135,"tested_up_to":92,"requires_at_least":136,"requires_php":137,"tags":138,"homepage":17,"download_link":140,"security_score":120,"vuln_count":141,"unpatched_count":13,"last_vuln_date":142,"fetched_at":28},"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",[19,21,139,55,117],"cdn","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fbreeze.2.4.1.zip",8,"2026-02-18 15:43:14",{"attackSurface":144,"codeSignals":164,"taintFlows":171,"riskAssessment":172,"analyzedAt":175},{"hooks":145,"ajaxHandlers":160,"restRoutes":161,"shortcodes":162,"cronEvents":163,"entryPointCount":13,"unprotectedCount":13},[146,151,154],{"type":147,"name":148,"callback":149,"file":150,"line":77},"action","admin_init","sck_options_init","sck-options.php",{"type":147,"name":152,"callback":153,"file":150,"line":32},"admin_menu","sck_options_add_page",{"type":155,"name":156,"callback":157,"file":158,"line":159},"filter","wp_head","stop_the_cache_madness","simple-cache-killer.php",47,[],[],[],[],{"dangerousFunctions":165,"sqlUsage":166,"outputEscaping":168,"fileOperations":13,"externalRequests":13,"nonceChecks":13,"capabilityChecks":13,"bundledLibraries":170},[],{"prepared":13,"raw":13,"locations":167},[],{"escaped":13,"rawEcho":13,"locations":169},[],[],[],{"summary":173,"deductions":174},"The 'simple-cache-killer' plugin version 1.0.2 exhibits an exceptionally strong security posture based on the provided static analysis and vulnerability history. The absence of any identified attack surface entry points (AJAX handlers, REST API routes, shortcodes, cron events), dangerous functions, raw SQL queries, file operations, or external HTTP requests significantly reduces the potential for exploitation. Furthermore, the complete lack of unsanitized taint flows, along with 100% output escaping and prepared statement usage, demonstrates a high level of developer diligence in preventing common web vulnerabilities. The plugin's vulnerability history is also pristine, with no recorded CVEs of any severity. This suggests a mature and well-maintained codebase that has likely undergone thorough security reviews or has been developed with security as a primary concern from its inception.  While the lack of explicit capability and nonce checks on the zero identified entry points might seem like a minor oversight, in this context, it does not pose a practical risk due to the absence of those entry points in the first place.  Therefore, this plugin appears to be highly secure.",[],"2026-03-16T23:57:51.115Z",{"wat":177,"direct":182},{"assetPaths":178,"generatorPatterns":179,"scriptPaths":180,"versionParams":181},[],[],[],[],{"cssClasses":183,"htmlComments":184,"htmlAttributes":185,"restEndpoints":191,"jsGlobals":192,"shortcodeOutput":193},[],[],[186,187,188,189,190],"name=\"sck[meta_cache_control]\"","name=\"sck[pragma_cache_control]\"","name=\"sck[cache_must_revalidate]\"","name=\"sck[send_pragma_nocache]\"","name=\"sck[send_cache_expires]\"",[],[],[194,195],"\u003CMETA HTTP-EQUIV=\"CACHE-CONTROL\" CONTENT=\"NO-CACHE\">","\u003CMETA HTTP-EQUIV=\"PRAGMA\" CONTENT=\"NO-CACHE\">"]