[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fu2JIkSGN9ti-cshM4Qrker4QyxPDXFIE9tKfNAwvVwc":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":142,"fingerprints":218},"next-page-caching","Next Page Caching","0.1","Benjamin Intal","https:\u002F\u002Fprofiles.wordpress.org\u002Fbfintal\u002F","\u003Cp>Your website visitors usually jump from page to page, or read your blog posts one after the other. Current caching plugins perform caching on the current page you are on. This plugin caches the next page your visitor will go to. This means your visitors can navigate your website faster.\u003C\u002Fp>\n\u003Ch4>How Does This Work?\u003C\u002Fh4>\n\u003Cp>Next Page Caching implements awesome “next page” caching to your site – this is different from your typical caching plugins like WP Rocket and W3 Total Cache.\u003C\u002Fp>\n\u003Cp>Instead of only trying to serve the current page faster to your visitors, this plugin lets your browser load parts of the next page while the visitor is busy reading the current page he\u002Fshe is on.\u003C\u002Fp>\n\u003Cp>It does this with your help. We ask you two things in every post\u002Fpage: First is what you think the next webpage your visitor will most likely go to afterwards, and second is a short list of critical files that you think should be loaded first in your page to make the top part of the page become visible quickly.\u003C\u002Fp>\n\u003Cp>With those two items, the plugin can now preload the important parts of the next page he’ll go to. The plugin also prioritizes the loading of the chosen critical files to ensure that the next page is visible as soon as possible.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>For example, if you find that a majority of your visitors in your front page check out the pricing page, then pick your pricing page as the “next page”. The visitors who navigate from your front page to your pricing page should see some speed benefits.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Cp>\u003Cstrong>This is not meant to replace your current caching plugin, but instead, this is meant to be used alongside it.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>What Caching Does This Do?\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>The plugin prefetches the main HTML of the chosen next page, as well as the critical files specified.\u003C\u002Fli>\n\u003Cli>Prefetches the first post when viewing a blog list or archive page.\u003C\u002Fli>\n\u003Cli>Preloads the post’s chosen critical files to prioritize them.\u003C\u002Fli>\n\u003Cli>Preloads the theme stylesheet so that it gets loaded first.\u003C\u002Fli>\n\u003Cli>Preloads the featured image of a blog post or page when needed (and if it’s large) so that it shows up faster.\u003C\u002Fli>\n\u003Cli>Preconnects to the Google Fonts domain for faster font downloading when needed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Important Notice\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Do not replace your current caching plugin with this one, use this one together with your existing one.\u003C\u002Fli>\n\u003Cli>This plugin does not predict \u002F analyze where your visitors will go next\u003C\u002Fli>\n\u003Cli>This plugin only has benefits in Modern Browsers\u003C\u002Fli>\n\u003C\u002Ful>\n","Speed up the loading of the NEXT page your visitors will go to.",10,1508,100,1,"2018-03-30T05:08:00.000Z","4.9.29","4.8","5.3",[20,21,22,23,24],"cache","caching","optimize","performance","super-cache","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnext-page-caching","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnext-page-caching.0.1.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":33,"display_name":7,"profile_url":8,"plugin_count":11,"total_installs":34,"avg_security_score":35,"avg_patch_time_days":36,"trust_score":37,"computed_at":38},"bfintal",110410,89,21,86,"2026-04-04T15:34:05.802Z",[40,62,82,102,123],{"slug":41,"name":42,"version":43,"author":44,"author_profile":45,"description":46,"short_description":47,"active_installs":48,"downloaded":49,"rating":37,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":54,"tags":55,"homepage":57,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":28,"last_vuln_date":61,"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,56,41],"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":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":72,"num_ratings":73,"last_updated":74,"tested_up_to":75,"requires_at_least":76,"requires_php":77,"tags":78,"homepage":80,"download_link":81,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"cachify","Cachify","2.4.2","pluginkollektiv","https:\u002F\u002Fprofiles.wordpress.org\u002Fpluginkollektiv\u002F","\u003Cp>\u003Cem>Cachify\u003C\u002Fem> optimizes your page loads by caching posts, pages and custom post types as static content. You can choose between caching via database, on the web server’s hard drive (HDD), Memcached (only on Nginx) or Redis. Whenever a page or post is loaded, it can be pulled directly from the cache. The amount of database queries and PHP requests will dramatically decrease towards zero, depending on the caching method you chose.\u003C\u002Fp>\n\u003Ch3>Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Works with custom post types.\u003C\u002Fli>\n\u003Cli>Caching methods: DB, HDD, Redis and Memcached.\u003C\u002Fli>\n\u003Cli>“Flush Cache” button in the WordPress toolbar.\u003C\u002Fli>\n\u003Cli>Ready for WordPress Multisite.\u003C\u002Fli>\n\u003Cli>Optional compression of HTML markup.\u003C\u002Fli>\n\u003Cli>White lists for posts and user agents.\u003C\u002Fli>\n\u003Cli>Manual and automatic cache reset.\u003C\u002Fli>\n\u003Cli>Automatic cache management.\u003C\u002Fli>\n\u003Cli>Dashboard widget for cached objects.\u003C\u002Fli>\n\u003Cli>Settings for Apache and Nginx servers.\u003C\u002Fli>\n\u003Cli>Extendability via hooks\u002Ffilters.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Support\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Community support via the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fcachify\u002F\" rel=\"ugc\">support forums on wordpress.org\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>We don’t handle support via e-mail, Twitter, GitHub issues etc.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Contribute\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Active development of this plugin is handled \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fpluginkollektiv\u002Fcachify\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Pull requests for documented bugs are highly appreciated.\u003C\u002Fli>\n\u003Cli>If you think you’ve found a bug (e.g. you’re experiencing unexpected behavior), please post at the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fcachify\u002F\" rel=\"ugc\">support forums\u003C\u002Fa> first.\u003C\u002Fli>\n\u003Cli>If you want to help us translate this plugin you can do so \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fcachify\u002F\" rel=\"nofollow ugc\">on WordPress Translate\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Credits\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Author: \u003Ca href=\"https:\u002F\u002Fsergejmueller.github.io\" rel=\"nofollow ugc\">Sergej Müller\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Maintainers: \u003Ca href=\"https:\u002F\u002Fpluginkollektiv.org\" rel=\"nofollow ugc\">pluginkollektiv\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Smart, efficient cache solution for WordPress. Use DB, HDD, Redis or Memcached for storing your blog pages. Make WordPress faster!",10000,364490,94,47,"2025-06-20T15:13:00.000Z","6.8.5","4.7","5.6",[20,21,22,23,79],"speed","https:\u002F\u002Fcachify.pluginkollektiv.org","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcachify.2.4.2.zip",{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":92,"num_ratings":93,"last_updated":94,"tested_up_to":52,"requires_at_least":95,"requires_php":96,"tags":97,"homepage":100,"download_link":101,"security_score":13,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wp-super-cache-clear-cache-menu","Clear All Cache for WP Super Cache","2.4","apasionados","https:\u002F\u002Fprofiles.wordpress.org\u002Fapasionados\u002F","\u003Cp>The plugin clears completely the cache from WP Super Cache, directly from the admin menu.\u003C\u002Fp>\n\u003Cp>We created this plugin, in order to be able to clear the cache completely  from the admin menu and not having to navigate to CONTENTS tab in WP Super Cache Settings.\u003C\u002Fp>\n\u003Cp>In some configuration WP Super Cache shows a menu entry to empty the cache in the menu, but it only empties the cache from the current page. See: \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002Fplugin-wp-super-cache-menu-delete-cache-doesnt-work-but-on-contents-page-it-does\" rel=\"ugc\">The “Delete Cache” button on the admin menu only deletes the cache for the current page.\u003C\u002Fa>\u003Cbr \u002F>\nNevertheless in the majority of the sites that have WP Super Cache installed it doesn’t display this menu entry.\u003C\u002Fp>\n\u003Cp>Please note that this menu option is only visible for WordPress ADMINISTRATORS.\u003C\u002Fp>\n\u003Cblockquote>\n\u003Cp>\u003Cstrong>This is an add-on to WP SUPER CACHE:\u003C\u002Fstrong>\u003Cbr \u002F>\n  Please keep in mind that this plugin is an add-on to the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F\" rel=\"ugc\">WP SUPER CACHE\u003C\u002Fa> plugin. You need to install and activate WP SUPER CACHE so that this add-on works.\u003C\u002Fp>\n\u003Cp>If you are having trouble with this plugin, feel free to use the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-super-cache-clear-cache-menu\" rel=\"ugc\">Clear All Cache for WP Super Cache Support\u003C\u002Fa>. If you are having problems with the WP SUPER CACHE plugin, you should ask for support at \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Fwp-super-cache\" rel=\"ugc\">WP Super Cache Support\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fblockquote>\n\u003Ch4>What can I do with this plugin?\u003C\u002Fh4>\n\u003Cp>The plugin clears completely the cache from WP Super Cache, directly from the admin menu.\u003C\u002Fp>\n\u003Ch4>Clear All Cache for WP Super Cache Plugin in your Language!\u003C\u002Fh4>\n\u003Cp>This first release is avaliable in English and Spanish. In the languages folder we have included the necessarry files to translate this plugin.\u003C\u002Fp>\n\u003Cp>If you would like the plugin in your language and you’re good at translating, please drop us a line at \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-wp-super-cache-clear-cache-menu-home\" rel=\"nofollow ugc\">Contact us\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Further Reading\u003C\u002Fh4>\n\u003Cp>You can access the description of the plugin in Spanish at: \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fblog\u002Fvaciar-cache-wp-super-cache-plugin-wordpress-1933\u002F\" rel=\"nofollow ugc\">Clear All Cache for WP Super Cache Plugin en castellano\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Contact\u003C\u002Fh3>\n\u003Cp>For further information please send us an \u003Ca href=\"http:\u002F\u002Fapasionados.es\u002Fcontacto\u002Findex.php?desde=wordpress-org-wp-super-cache-clear-cache-menu-contact\" rel=\"nofollow ugc\">email\u003C\u002Fa>.\u003C\u002Fp>\n","Clear all cache for WP Super Cache adds a menu entry to the admin menu to clear the cache completely .",7000,279587,62,11,"2026-02-01T14:44:00.000Z","3.0.1","",[20,21,98,99,23],"empty-cache","emtpy-wp-super-cache","https:\u002F\u002Fapasionados.es\u002Fblog\u002Fvaciar-cache-wp-super-cache-plugin-wordpress-1933\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache-clear-cache-menu.2.4.zip",{"slug":103,"name":104,"version":105,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":110,"downloaded":111,"rating":112,"num_ratings":113,"last_updated":114,"tested_up_to":52,"requires_at_least":18,"requires_php":54,"tags":115,"homepage":118,"download_link":119,"security_score":120,"vuln_count":121,"unpatched_count":28,"last_vuln_date":122,"fetched_at":30},"litespeed-cache","LiteSpeed Cache","7.8","LiteSpeed Technologies","https:\u002F\u002Fprofiles.wordpress.org\u002Flitespeedtech\u002F","\u003Cp>LiteSpeed Cache for WordPress (LSCWP) is an all-in-one site acceleration plugin, featuring an exclusive server-level cache and a collection of optimization features.\u003C\u002Fp>\n\u003Cp>LSCWP supports WordPress Multisite and is compatible with most popular plugins, including WooCommerce, bbPress, and Yoast SEO.\u003C\u002Fp>\n\u003Cp>LiteSpeed Cache for WordPress is compatible with ClassicPress.\u003C\u002Fp>\n\u003Ch3>Requirements\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>General Features\u003C\u002Fstrong> may be used by anyone with any web server (LiteSpeed, Apache, NGINX, etc.).\u003C\u002Fp>\n\u003Cp>\u003Cstrong>LiteSpeed Exclusive Features\u003C\u002Fstrong> require one of the following: OpenLiteSpeed, commercial LiteSpeed products, LiteSpeed-powered hosting, or QUIC.cloud CDN. \u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002Ffaq\u002F#why-do-the-cache-features-require-a-litespeed-server\" rel=\"nofollow ugc\">Why?\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Plugin Features\u003C\u002Fh3>\n\u003Ch4>General Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Free QUIC.cloud CDN Cache\u003C\u002Fli>\n\u003Cli>Object Cache (Memcached\u002FLSMCD\u002FRedis) Support+\u003C\u002Fli>\n\u003Cli>Image Optimization (Lossless\u002FLossy)\u003C\u002Fli>\n\u003Cli>Minify CSS, JavaScript, and HTML\u003C\u002Fli>\n\u003Cli>Minify inline & external CSS\u002FJS\u003C\u002Fli>\n\u003Cli>Combine CSS\u002FJS\u003C\u002Fli>\n\u003Cli>Automatically generate Critical CSS\u003C\u002Fli>\n\u003Cli>Lazy-load images\u002Fiframes\u003C\u002Fli>\n\u003Cli>Responsive Image Placeholders\u003C\u002Fli>\n\u003Cli>Multiple CDN Support+\u003C\u002Fli>\n\u003Cli>Load CSS Asynchronously\u003C\u002Fli>\n\u003Cli>Defer\u002Fdelay JS loading\u003C\u002Fli>\n\u003Cli>Browser Cache Support+\u003C\u002Fli>\n\u003Cli>Database Cleaner and Optimizer\u003C\u002Fli>\n\u003Cli>PageSpeed score (including Core Web Vitals) optimization\u003C\u002Fli>\n\u003Cli>OPcode Cache Support+\u003C\u002Fli>\n\u003Cli>HTTP\u002F2 Push for CSS\u002FJS (on web servers that support it)\u003C\u002Fli>\n\u003Cli>DNS Prefetch\u003C\u002Fli>\n\u003Cli>Cloudflare API\u003C\u002Fli>\n\u003Cli>Single Site and Multisite (Network) support\u003C\u002Fli>\n\u003Cli>Import\u002FExport settings\u003C\u002Fli>\n\u003Cli>Attractive, easy-to-understand interface\u003C\u002Fli>\n\u003Cli>AVIF\u002FWebP image format support\u003C\u002Fli>\n\u003Cli>Heartbeat control\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>+ This service is not provided by the LSCache plugin, nor is it guaranteed to be installed by your service provider. However, the plugin is compatible with the service if it is in use on your site.\u003C\u002Fp>\n\u003Ch4>LiteSpeed Exclusive Features\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Automatic page caching to greatly improve site performance\u003C\u002Fli>\n\u003Cli>Automatic purge of related pages based on certain events\u003C\u002Fli>\n\u003Cli>Private cache for logged-in users\u003C\u002Fli>\n\u003Cli>Caching of WordPress REST API calls\u003C\u002Fli>\n\u003Cli>Separate caching of desktop and mobile views\u003C\u002Fli>\n\u003Cli>Ability to schedule purge for specified URLs\u003C\u002Fli>\n\u003Cli>WooCommerce and bbPress support\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002Fcli\u002F\" rel=\"nofollow ugc\">WordPress CLI\u003C\u002Fa> commands\u003C\u002Fli>\n\u003Cli>API system for easy cache integration\u003C\u002Fli>\n\u003Cli>Exclude from cache by URI, Category, Tag, Cookie, User Agent\u003C\u002Fli>\n\u003Cli>Smart preload crawler with support for SEO-friendly sitemap\u003C\u002Fli>\n\u003Cli>Multiple crawlers for cache varies\u003C\u002Fli>\n\u003Cli>HTTP\u002F2 support\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwww.litespeedtech.com\u002Fhttp3-faq\" rel=\"nofollow ugc\">HTTP\u002F3 & QUIC\u003C\u002Fa> support\u003C\u002Fli>\n\u003Cli>ESI (Edge Side Includes) support*\u003C\u002Fli>\n\u003Cli>Widgets and Shortcodes as ESI blocks* (requires Classic Widgets plugin for WP 5.8+)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>* Feature not available in OpenLiteSpeed\u003C\u002Fp>\n\u003Ch3>LSCWP Resources\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Flitespeedtech.com\u002Fslack\" rel=\"nofollow ugc\">Join our Slack community\u003C\u002Fa> to connect with other LiteSpeed users.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Fplugin\u002Flitespeed-cache\u002F\" rel=\"ugc\">Ask a question on our support forum\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002F\" rel=\"nofollow ugc\">View detailed documentation\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fblog.litespeedtech.com\u002Ftag\u002Fwordpress\u002F\" rel=\"nofollow ugc\">Read about LSCWP and WordPress on our blog\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Flitespeed-cache\u002F\" rel=\"nofollow ugc\">Help translate LSCWP\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002Flitespeedtech\u002Flscache_wp\" rel=\"nofollow ugc\">Contribute to the LSCWP GitHub repo\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Third Party Compatibility\u003C\u002Fh3>\n\u003Cp>The vast majority of plugins and themes are compatible with LSCache. \u003Ca href=\"https:\u002F\u002Fdocs.litespeedtech.com\u002Flscache\u002Flscwp\u002Fapi\u002F\" rel=\"nofollow ugc\">Our API\u003C\u002Fa> is available for those that are not. Use the API to customize smart purging, customize cache rules, create cache varies, and make WP nonce cacheable, among other things.\u003C\u002Fp>\n\u003Ch3>Privacy\u003C\u002Fh3>\n\u003Cp>This plugin includes some suggested text that you can add to your site’s Privacy Policy via the Guide in the WordPress Privacy settings.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>For your own information:\u003C\u002Fstrong> LiteSpeed Cache for WordPress potentially stores a duplicate copy of every web page on display on your site. The pages are stored locally on the system where LiteSpeed server software is installed and are not transferred to or accessed by LiteSpeed employees in any way, except as necessary in providing routine technical support if you request it. All cache files are temporary, and may easily be purged before their natural expiration, if necessary, via a Purge All command. It is up to individual site administrators to come up with their own cache expiration rules.\u003C\u002Fp>\n\u003Cp>In addition to caching, our WordPress plugin has online features provided by QUIC.cloud for Image Optimization and Page Optimization services. When one of these optimizations is requested, data is transmitted to a remote QUIC.cloud server, processed, and then transmitted back for use on your site. QUIC.cloud keeps copies of that data for up to 7 days and then permanently deletes it. Similarly, the WordPress plugin has a Reporting feature whereby a site owner can transmit an environment report to LiteSpeed so that we may better provide technical support. None of these features collects any visitor data. Only server and site data are involved.\u003C\u002Fp>\n\u003Cp>QUIC.cloud CDN, if enabled, uses LSCache technology to access your site, and serve your content from remote global nodes. Your data is not accessed by QUIC.cloud employees in any way, except as necessary in providing maintenance or technical support.\u003C\u002Fp>\n\u003Cp>Please see the \u003Ca href=\"https:\u002F\u002Fquic.cloud\u002Fprivacy-policy\u002F\" rel=\"nofollow ugc\">QUIC.cloud Privacy Policy\u003C\u002Fa> for our complete Privacy\u002FGDPR statement.\u003C\u002Fp>\n","All-in-one unbeatable acceleration & PageSpeed improvement: caching, image\u002FCSS\u002FJS optimization...",7000000,126174082,96,2718,"2026-03-03T18:24:00.000Z",[21,22,116,23,117],"pagespeed","seo","https:\u002F\u002Fwww.litespeedtech.com\u002Fproducts\u002Fcache-plugins\u002Fwordpress-acceleration","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flitespeed-cache.7.8.zip",82,18,"2025-10-28 00:00:00",{"slug":124,"name":125,"version":126,"author":127,"author_profile":128,"description":129,"short_description":130,"active_installs":48,"downloaded":131,"rating":132,"num_ratings":133,"last_updated":134,"tested_up_to":52,"requires_at_least":18,"requires_php":96,"tags":135,"homepage":137,"download_link":138,"security_score":139,"vuln_count":140,"unpatched_count":28,"last_vuln_date":141,"fetched_at":30},"wp-fastest-cache","WP Fastest Cache – WordPress Cache Plugin","1.4.6","Emre Vona","https:\u002F\u002Fprofiles.wordpress.org\u002Femrevona\u002F","\u003Ch4>Official Website\u003C\u002Fh4>\n\u003Cp>You can find more information on our website (\u003Ca href=\"https:\u002F\u002Fwww.wpfastestcache.com\u002F\" rel=\"nofollow ugc\">wpfastestcache.com\u003C\u002Fa>)\u003C\u002Fp>\n\u003Cp>Welcome to the page of the WP Fastest Cache plugin, a WordPress cache plugin developed to speed up WordPress sites.\u003C\u002Fp>\n\u003Cp>In today’s world where every second counts, optimizing your website’s performance is very important. Meet WP Fastest Cache, your caching plugin that you can use to speed up WordPress websites. \u003C\u002Fp>\n\u003Cp>Optimize the performance of your website with WP Fastest Cache. Improve Google PageSpeed, Core Web Vitals, GTmetrix and Pingdom score with our wp cache plugin.\u003C\u002Fp>\n\u003Cp>In addition, page speed is a ranking factor in Google’s search algorithm. Therefore, using cache plugins helps improve your SEO ranking. Our WordPress optimization plugin not only accelerates your site but also boosts SEO rankings.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Mod_Rewrite which is the fastest method is used in this plugin\u003C\u002Fli>\n\u003Cli>All cache files are deleted when a post or page is published\u003C\u002Fli>\n\u003Cli>Admin can delete all cached files from the options page\u003C\u002Fli>\n\u003Cli>Admin can delete minified css and js files from the options page\u003C\u002Fli>\n\u003Cli>Block cache for specific page or post with Short Code\u003C\u002Fli>\n\u003Cli>Cache Timeout – All cached files are deleted at the determinated time\u003C\u002Fli>\n\u003Cli>Cache Timeout for specific pages\u003C\u002Fli>\n\u003Cli>Enable\u002FDisable cache option for mobile devices\u003C\u002Fli>\n\u003Cli>Enable\u002FDisable cache option for logged-in users\u003C\u002Fli>\n\u003Cli>SSL support\u003C\u002Fli>\n\u003Cli>CDN support – Effortlessly enhance website speed and performance with seamless CDN integration, supporting Bunny CDN, Cloudflare, and various other leading CDN providers. CDN integration modifies the URLs of static resources, enabling these assets to be served from your CDN service provider\u003C\u002Fli>\n\u003Cli>Cloudflare support – Cloudflare integration triggers the clearing of the cache on Cloudflare through API when a cache purge is initiated. As a result, WP Fastest Cache and Cloudflare operate seamlessly in tandem\u003C\u002Fli>\n\u003Cli>Preload Cache – Create the cache of all the site automatically\u003C\u002Fli>\n\u003Cli>Exclude pages and user-agents\u003C\u002Fli>\n\u003Cli>WP-CLI cache clearing\u003C\u002Fli>\n\u003Cli>Proxy Cache – Varnish Cache Integration to clear proxy cached content automatically when the cache created by WP Fastest Cache is cleared\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Performance Optimization\u003C\u002Fh4>\n\u003Cp>WP Fastest Cache is not only a wp cache plugin but also a speed optimization wordpress cache plugin. There are many features such as Minify Html, Minify Css, Enable Gzip Compression, Leverage Browser Caching, Add Expires Headers, Combine CSS, Combine JS, Disable Emoji.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Page Caching – Page caching feature generates and store static HTML files from your dynamic WordPress blog to reduce initial server response time, and improving page load time. Page cache and caching play a critical role in improving website speed and overall web performance. By storing frequently accessed data, effective caching reduces server workload and significantly improves cache performance, allowing pages to be delivered faster to users. This optimization directly lowers load time and enhances page speed, resulting in a smoother user experience and better SEO.\u003C\u002Fli>\n\u003Cli>Minify Html – Using an HTML minifier is an effective way to reduce HTML size and optimize HTML by removing unnecessary spaces, comments, and line breaks. A smaller HTML file helps reduce page size, which directly improves page speed and leads to a faster website experience for users. By focusing on web performance optimization, optimized HTML allows browsers to load and render pages more efficiently, helping to improve website speed, lower bandwidth usage, and deliver better overall performance across all devices\u003C\u002Fli>\n\u003Cli>Minify Css – CSS minify techniques play a crucial role in modern web development by reducing unnecessary characters through a reliable css minifier. With effective css compression, developers can compress CSS files and apply proper css minification to optimize CSS for production environments. This approach helps reduce CSS file size, which directly contributes to improve website speed and overall css performance optimization. As part of a broader page speed optimization strategy, these practices significantly enhance website performance optimization and lead to better website loading performance, especially on mobile and low-bandwidth connections\u003C\u002Fli>\n\u003Cli>Enable Gzip Compression – Reduce the size of files sent from your server to increase the speed to which they are transferred to the browser\u003C\u002Fli>\n\u003Cli>Leverage browser caching – Browser cache plays a critical role in how efficiently a web browser cache stores static resources like images, stylesheets, and scripts, directly impacting page load speed. By allowing returning visitors to load files from their local browser cache instead of downloading them again, websites can significantly reduce server requests and improve website speed. Properly configured browser caching not only creates a faster and smoother user experience but also helps lower bandwidth usage and enhance overall site performance\u003C\u002Fli>\n\u003Cli>Combine CSS – Reduce number of HTTP round-trips by combining multiple CSS resources into one\u003C\u002Fli>\n\u003Cli>Combine JS – Combining JavaScript files is a core technique in javascript optimization and js optimization, especially when the goal is to reduce requests and improve page load speed. By combine js assets or combine javascript files into a single bundle, developers can streamline how scripts are delivered to the browser. Whether you call it js combine or javascript combine, the idea is the same: fewer HTTP requests mean faster performance. Similarly, approaches that merge js or merge javascript—also known as js merge or javascript merge—help eliminate overhead caused by loading multiple separate files. When done correctly, combining and merging scripts leads to cleaner delivery, better caching, and noticeably faster websites\u003C\u002Fli>\n\u003Cli>Disable Emoji – You can remove the emoji inline css and wp-emoji-release.min.js\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Premium Performance Optimization\u003C\u002Fh4>\n\u003Cp>The free version is enough to speed up your site but in the premium version there are extra features such as Mobile Cache, Widget Cache, Minify HTML Plus, Minify CSS Plus, Minify JS, Combine JS Plus, Defer Javascript, Optimize Images, Convert WebP, Database Cleanup, Google Fonts Async, Lazy Load and Delay JS for super fast load times.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Mobile Cache\u003C\u002Fli>\n\u003Cli>Widget Cache\u003C\u002Fli>\n\u003Cli>Minify HTML Plus\u003C\u002Fli>\n\u003Cli>Minify CSS Plus\u003C\u002Fli>\n\u003Cli>Minify Javascript – Minify JS is a core step in web performance optimization because js minify techniques remove unnecessary characters, comments, and whitespace, making files smaller and faster to load. Through proper javascript minification, developers can compress JavaScript assets and significantly reduce transfer size, which directly supports effective js optimization and overall javascript optimization strategies. When combined with caching and code splitting, minified scripts help improve website speed, lower bandwidth usage, and enhance user experience. As a result, page speed optimization becomes easier to achieve, leading to faster render times and better search engine rankings.\u003C\u002Fli>\n\u003Cli>Combine JS Plus\u003C\u002Fli>\n\u003Cli>Defer Javascript – Eliminate render-blocking JavaScript resources. Consider delivering critical JS inline and deferring all non-critical JS\u003C\u002Fli>\n\u003Cli>Optimize Images – Optimized images load faster and consume less cellular data. Looking for an easy image compressor? Our tool lets you compress images instantly, including Compress JPEG and Compress PNG options. Enjoy fast image compression to reduce image size without losing quality. Perfect for quick image optimization with a smart image optimizer designed for all your needs.\u003C\u002Fli>\n\u003Cli>Convert WebP – Serve images in next-gen formats. Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. A fast and reliable WebP converter helps you convert to WebP in seconds. Whether you need a WebP convert tool, a JPG to WEBP Converter, PNG to WEBP Converter, or a simple image to WebP option, you can easily optimize your images. Quickly handle JPG to WEBP, PNG to WEBP, jpg convert to webp, and png convert to webp tasks to reduce file size and improve web performance.\u003C\u002Fli>\n\u003Cli>Database Cleanup – To keep your system running smoothly, it’s important to clean database structures regularly and ensure you clean DB records that are no longer needed. A database cleaner is essential for effective database cleaning and long-term database optimization. By removing unused entries and organizing data efficiently, you can significantly improve database performance and speed up database operations. Modern db cleaner tools automate the entire db cleaning process, helping developers maintain fast, reliable, and scalable systems. The Database Cleanup feature clears out all of the garbage datas such as post revisions, trashed posts & pages, comments from trash & spam, trackbacks and pingbacks, transient options, orphaned post meta, comment meta, user meta, term meta, and term relationship etc.\u003C\u002Fli>\n\u003Cli>Google Fonts Async\u003C\u002Fli>\n\u003Cli>Lazy Load – Lazy loading technique improve page speed and overall website loading time by loading content only when it is needed. Using lazy load images, lazy loading images, lazy load videos, and lazy load iframe helps reduce initial load size, enhances web performance, and delivers a smoother user experience. When implemented correctly, these methods make it easier to optimize website performance, lower bandwidth usage, and ensure faster, more efficient page delivery for both users and search engines.\u003C\u002Fli>\n\u003Cli>Delay JS – The Delay JavaScript feature helps reduce the ‘Reduce unused JavaScript’ warning in the Google PageSpeed Insights tool\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Information\u003C\u002Fh4>\n\u003Cp>It is very inconvenient to use multiple caching plugins at the same time. That’s why you need to disable plugins such as LiteSpeed Cache, WP-Optimize, W3 Total Cache, WP Super Cache, SiteGround Optimizer, Breeze while using WP Fastest Cache.\u003C\u002Fp>\n\u003Cp>WP Fastest Cache is compatible with most popular plugins such as Contact Form 7, Yoast SEO, Elementor Website Builder, Classic Editor, Akismet Spam Protection, WooCommerce, Contact Form by WPForms, Really Simple SSL, All-in-One WP Migration, Yoast Duplicate Post, Wordfence Security – Firewall & Malware Scan, WordPress Importer, UpdraftPlus WordPress Backup Plugin, MonsterInsights, All in One SEO, WP Mail SMTP by WPForms.\u003C\u002Fp>\n\u003Ch4>Supported Languages\u003C\u002Fh4>\n\u003Cp>Although there are over 7000 languages spoken in the world today, we feel very lucky to support 30 languages for now.\u003C\u002Fp>\n\u003Cp>However, localizing or adapting a plugin to another language or culture is time consuming and a demanding task. That’s where the amazing Translation Contributors team of WordPress comes into play. These selfless people spent their precious time without expecting anything in return so that other people can use the add-ons more easily. We sincerely thank all of them.\u003C\u002Fp>\n\u003Cp>Chinese Simplified (China), Chinese Traditional (Taiwan), Czech, Dutch (Belgium), Dutch (Netherlands), English (South Africa), English (UK), Finnish, French (France), Galician, German (Germany), Hungarian, Indonesian, Italian, Japanese, Korean (Korea), Persian, Russian, Slovak (Slovakia), Slovenian, Spanish (Argentina), Spanish (Chile), Spanish (Colombia), Spanish (Ecuador), Spanish (Mexico), Spanish (Spain), Spanish (Venezuela), Swedish, Turkish, Ukrainian\u003C\u002Fp>\n","The simplest and fastest WP Cache system",63353783,98,4207,"2026-02-10T14:26:00.000Z",[20,136,22,116,23],"core-web-vitals","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-fastest-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-fastest-cache.1.4.6.zip",76,35,"2025-11-26 21:34:28",{"attackSurface":143,"codeSignals":195,"taintFlows":208,"riskAssessment":209,"analyzedAt":217},{"hooks":144,"ajaxHandlers":191,"restRoutes":192,"shortcodes":193,"cronEvents":194,"entryPointCount":28,"unprotectedCount":28},[145,151,155,159,162,167,171,175,180,182,185,188],{"type":146,"name":147,"callback":148,"file":149,"line":150},"action","add_meta_boxes","add_metabox","class-admin-metabox.php",14,{"type":146,"name":152,"callback":153,"priority":11,"file":149,"line":154},"save_post","save_metabox",15,{"type":146,"name":156,"callback":157,"file":158,"line":150},"admin_menu","create_admin_menu","class-admin-welcome.php",{"type":146,"name":160,"callback":161,"file":158,"line":154},"activated_plugin","redirect_to_welcome_page",{"type":146,"name":163,"callback":164,"priority":165,"file":166,"line":140},"wp_head","add_head_links",99999,"class-browser-hints.php",{"type":146,"name":168,"callback":169,"priority":165,"file":166,"line":170},"wp_footer","add_footer_links",36,{"type":146,"name":163,"callback":172,"file":173,"line":174},"add_theme_preload","class-cacher.php",16,{"type":176,"name":177,"callback":178,"priority":11,"file":173,"line":179},"filter","wp_get_attachment_image_src","add_featured_image_preload",17,{"type":146,"name":163,"callback":181,"file":173,"line":121},"add_google_fonts_preconnect",{"type":146,"name":163,"callback":183,"file":173,"line":184},"add_next_page_prefetch",19,{"type":146,"name":163,"callback":186,"file":173,"line":187},"add_critical_preloaders",20,{"type":176,"name":189,"callback":190,"priority":11,"file":173,"line":36},"the_posts","add_first_archive_entry_prefetch",[],[],[],[],{"dangerousFunctions":196,"sqlUsage":197,"outputEscaping":199,"fileOperations":28,"externalRequests":28,"nonceChecks":14,"capabilityChecks":14,"bundledLibraries":207},[],{"prepared":28,"raw":28,"locations":198},[],{"escaped":154,"rawEcho":200,"locations":201},2,[202,205],{"file":166,"line":203,"context":204},43,"raw output",{"file":166,"line":206,"context":204},49,[],[],{"summary":210,"deductions":211},"The \"next-page-caching\" v0.1 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of an attack surface through AJAX handlers, REST API routes, shortcodes, and cron events is a significant strength, indicating that the plugin has limited direct entry points for external manipulation.  Furthermore, the code signals show good practices, with all SQL queries utilizing prepared statements, a substantial majority of output being properly escaped, and the presence of nonce and capability checks. The lack of any recorded vulnerabilities or CVEs in its history also suggests a stable and well-maintained codebase.\n\nHowever, it's important to note that the taint analysis reported zero flows analyzed. While this could mean no vulnerabilities were found, it also implies a potential limitation in the analysis itself. A lack of file operations and external HTTP requests further contributes to a low-risk profile, as these are common vectors for exploitation. The plugin appears to prioritize secure coding practices, but the limited scope of the taint analysis warrants a cautious approach. Overall, the plugin is assessed as low risk, with its primary strengths being its minimal attack surface and adherence to secure coding principles regarding database interactions and authentication.\n\nDespite the positive findings, the absence of any reported taint flows is a point of consideration. It's possible that the plugin's limited functionality inherently prevents complex taint scenarios, or it could indicate a gap in the analysis's ability to detect potential issues in this specific context. While there are no direct vulnerabilities flagged by the static analysis or historical data, the potential for undiscovered issues in complex interaction scenarios or edge cases remains. The plugin is considered secure for its current version based on the data, but continuous monitoring and updated analysis are always recommended for any software.",[212,215],{"reason":213,"points":214},"Taint analysis not performed",5,{"reason":216,"points":200},"Output escaping not 100%","2026-03-17T05:40:47.152Z",{"wat":219,"direct":229},{"assetPaths":220,"generatorPatterns":223,"scriptPaths":224,"versionParams":226},[221,222],"\u002Fwp-content\u002Fplugins\u002Fnext-page-caching\u002Fdist\u002Fnpc.min.js","\u002Fwp-content\u002Fplugins\u002Fnext-page-caching\u002Fsrc\u002Fnpc.css",[],[225],"dist\u002Fnpc.min.js",[227,228],"next-page-caching\u002Fdist\u002Fnpc.min.js?ver=","next-page-caching\u002Fsrc\u002Fnpc.css?ver=",{"cssClasses":230,"htmlComments":234,"htmlAttributes":235,"restEndpoints":237,"jsGlobals":238,"shortcodeOutput":239},[231,232,233],"npc-meta","npc_title","npc_next_url_area",[],[236],"data-permalink",[],[],[]]