[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fUfyAslXh2xdt-8UFayzQPLE19joCWPJGNWmo03SDx64":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":38,"analysis":141,"fingerprints":189},"kagg-pagespeed-module","PageSpeed Module","2.2.0","kaggdesign","https:\u002F\u002Fprofiles.wordpress.org\u002Fkaggdesign\u002F","\u003Cp>PageSpeed Module is an open-source module for Apache and Nginx created by Google to help Make the Web Faster by rewriting web pages to reduce latency and bandwidth.\u003C\u002Fp>\n\u003Cp>The plugin allows purge caches created by Apache or Nginx Module and turn on development mode for WordPress site, bypassing PageSpeed cache.\u003C\u002Fp>\n\u003Cp>The plugin requires PageSpeed Module to be installed with your Apache or Nginx web server. If PageSpeed Module is not installed, the plugin does nothing.\u003C\u002Fp>\n","PageSpeed Module plugin supports WordPress installation under Apache or Nginx with PageSpeed Module.",200,17013,90,4,"2026-03-03T18:25:00.000Z","6.9.4","6.0","7.4",[20,21,22,23,24],"apache","cache","mod_pagespeed","nginx","pagespeed-module","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fkagg-pagespeed-module\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fkagg-pagespeed-module.2.2.0.zip",100,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":14,"total_installs":33,"avg_security_score":34,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},2230,98,30,93,"2026-04-04T15:10:08.515Z",[39,62,83,102,122],{"slug":40,"name":41,"version":42,"author":43,"author_profile":44,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":50,"last_updated":51,"tested_up_to":52,"requires_at_least":53,"requires_php":54,"tags":55,"homepage":60,"download_link":61,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"nginx-helper","Nginx Helper","2.3.5","rtCamp","https:\u002F\u002Fprofiles.wordpress.org\u002Frtcamp\u002F","\u003Col>\n\u003Cli>Removes \u003Ccode>index.php\u003C\u002Fcode> from permalinks when using WordPress with nginx.\u003C\u002Fli>\n\u003Cli>Adds support for purging redis-cache when used as full-page cache created using \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fopenresty\u002Fsrcache-nginx-module#caching-with-redis\" rel=\"nofollow ugc\">nginx-srcache-module\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Adds support for nginx fastcgi_cache_purge & proxy_cache_purge directive from \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FFRiCKLE\u002Fngx_cache_purge\" title=\"ngx_cache_purge module\" rel=\"nofollow ugc\">module\u003C\u002Fa>. Provides settings so you can customize purging rules.\u003C\u002Fli>\n\u003Cli>Adds support for nginx \u003Ccode>map{..}\u003C\u002Fcode> on a WordPress-multisite network installation. Using it, Nginx can serve PHP file uploads even if PHP\u002FMySQL crashes. Please check the tutorial list below for related Nginx configurations.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Tutorials\u003C\u002Fh4>\n\u003Cp>You will need to follow one or more tutorials below to get desired functionality:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fmultisite\u002Fstatic-files-handling\u002F\" rel=\"nofollow ugc\">Nginx Map + WordPress-Multisite + Static Files Handling\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fsingle-site\u002Ffastcgi-cache-with-purging\u002F\" rel=\"nofollow ugc\">Nginx + WordPress + fastcgi_purge_cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fmultisite\u002Fsubdirectories\u002Ffastcgi-cache-with-purging\u002F\" rel=\"nofollow ugc\">Nginx + WordPress-Multisite (Subdirectories) + fastcgi_purge_cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002Fmultisite\u002Fsubdomains\u002Ffastcgi-cache-with-purging\u002F\" rel=\"nofollow ugc\">Nginx + WordPress-Multisite (Subdomains\u002Fdomain-mapping) + fastcgi_purge_cache\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Feasyengine.io\u002Fwordpress-nginx\u002Ftutorials\u002F\" rel=\"nofollow ugc\">Other WordPress-Nginx Tutorials\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Cleans nginx's fastcgi\u002Fproxy cache or redis-cache whenever a post is edited\u002Fpublished. Also does a few more things.",100000,6119694,88,31,"2025-08-21T06:49:00.000Z","6.8.5","3.0","",[56,57,23,58,59],"cache-purge","fastcgi","permalinks","redis-cache","https:\u002F\u002Frtcamp.com\u002Fnginx-helper\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-helper.2.3.5.zip",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":49,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":76,"tags":77,"homepage":81,"download_link":82,"security_score":27,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"varnish-http-purge","Proxy Cache Purge","5.7.0","Danila Vershinin","https:\u002F\u002Fprofiles.wordpress.org\u002Fdvershinin\u002F","\u003Cp>\u003Cstrong>This plugin \u003Cem>does not\u003C\u002Fem> install nor configure a cache proxy. It acts as an interface with such services.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>One common method of caching content for websites is via the use of reverse proxy caching. Common examples of this are \u003Ca href=\"https:\u002F\u002Fwww.varnish-cache.org\u002F\" rel=\"nofollow ugc\">Varnish\u003C\u002Fa> and \u003Ca href=\"https:\u002F\u002Fwww.nginx.org\u002F\" rel=\"nofollow ugc\">NGINX\u003C\u002Fa>. These systems allow a website to update content and have the visitor’s experience cached without the need for complex plugins storing the files locally and using up a user’s disk space.\u003C\u002Fp>\n\u003Cp>A reverse proxy cache is installed in front of a server and reviews requests. If the page being requested is already cached, it delivers the cached content. Otherwise it generates the page and the cache on demand.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The Proxy Cache Purge plugin sends a request to delete (aka flush) the cached data of a page or post every time it’s modified.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Cp>When content on a site is updated by WordPress, the plugin reaches out to the proxy cache service with the URL of the page, requesting the cache be deleted.\u003C\u002Fp>\n\u003Cp>Not all pages are deleted from the cache on every change. For example, when a post, page, or custom post type is edited, or a new comment is added, \u003Cem>only\u003C\u002Fem> the following pages will purge:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The front page\u003C\u002Fli>\n\u003Cli>The post\u002Fpage edited\u003C\u002Fli>\n\u003Cli>Any categories, tags, and\u002For custom taxonomies associated with the page\u003C\u002Fli>\n\u003Cli>Related feeds\u003C\u002Fli>\n\u003Cli>Associated JSON API pages\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>In addition, your \u003Cem>entire\u003C\u002Fem> cache will be deleted on the following actions:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Changing themes\u003C\u002Fli>\n\u003Cli>Pressing the \u003Cstrong>Empty Cache\u003C\u002Fstrong> button on the toolbar\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Plugins can hook into the purge actions as well, to filter their own events to trigger a purge.\u003C\u002Fp>\n\u003Cp>On a multisite network using subfolders, only \u003Cstrong>network admins\u003C\u002Fstrong> can purge the main site.\u003C\u002Fp>\n\u003Ch4>Development Mode\u003C\u002Fh4>\n\u003Cp>If you’re working on a site and need to turn off caching in one of two ways:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Add \u003Ccode>define( 'VHP_DEVMODE', true );\u003C\u002Fcode> to your \u003Ccode>wp-config.php\u003C\u002Fcode> file\u003C\u002Fli>\n\u003Cli>Go to Proxy Cache -> Settings and enable Debug Mode for 24 hours at a time\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>That will break cache on page loads. It is \u003Cem>not\u003C\u002Fem> recommended for production!\u003C\u002Fp>\n\u003Ch4>Cache Tags (BETA)\u003C\u002Fh4>\n\u003Cp>As of version 5.4.0, Proxy Cache Purge includes an \u003Cstrong>optional Cache Tags \u002F Surrogate Keys purge mode\u003C\u002Fstrong>. This feature is marked as \u003Cstrong>BETA\u003C\u002Fstrong> and is disabled by default.\u003C\u002Fp>\n\u003Cp>When enabled, the plugin:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Adds cache-tag headers to WordPress responses (for example, tagging pages by post ID, post type, taxonomy terms, author, and archives).\u003C\u002Fli>\n\u003Cli>Uses tag-based purges instead of individual URL purges when content is updated, which can reduce purge traffic and improve consistency on complex sites.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Requirements:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A proxy cache that supports Cache Tags \u002F Surrogate Keys and advertises this via standard \u003Ccode>Surrogate-Capability\u003C\u002Fcode> headers (for example, \u003Ccode>Surrogate-Capability: vhp=\"Surrogate\u002F1.0 tags\u002F1\"\u003C\u002Fcode>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>How to enable:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Go to \u003Cstrong>Proxy Cache \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Settings \u003Cspan aria-hidden=\"true\" class=\"wp-exclude-emoji\">→\u003C\u002Fspan> Purge Method\u003C\u002Fstrong> and check \u003Cstrong>“Use Cache Tags (Surrogate Keys)”\u003C\u002Fstrong>. The checkbox is only enabled when your cache tells WordPress it supports tags (or when you explicitly enable it via a define).\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Alternatively, you can force-enable or force-disable detection via \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cp>define( ‘VHP_VARNISH_TAGS’, true );  \u002F\u002F Force treat cache as tag-capable\u003Cbr \u002F>\ndefine( ‘VHP_VARNISH_TAGS’, false ); \u002F\u002F Force treat cache as not tag-capable\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Because this feature depends on your cache configuration, it is recommended that you test it carefully in staging before enabling it on production.\u003C\u002Fp>\n\u003Ch4>Background Purging with WP-Cron\u003C\u002Fh4>\n\u003Cp>On busy sites, sending many PURGE requests directly from admin requests can slow things down. When you define \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> as \u003Ccode>true\u003C\u002Fcode> in \u003Ccode>wp-config.php\u003C\u002Fcode> (because you are running a real system cron that calls \u003Ccode>wp-cron.php\u003C\u002Fcode>), Proxy Cache Purge automatically switches to an asynchronous mode:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Purge requests (both URL-based and tag-based, when Cache Tags are enabled) are collected into a small per-site queue.\u003C\u002Fli>\n\u003Cli>The queue is processed by WP-Cron in the background, keeping your admin and content-editing actions responsive even when many URLs or tags must be invalidated.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Object-cache purges (the “Purge Database Cache” option) remain synchronous and are not affected by this behaviour. The Proxy Cache settings page and Site Health integration expose basic queue status so you can verify that background purging is healthy; if the queue appears large or very old, check that your system cron is correctly invoking WordPress cron.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Important: Cron Frequency and Cache Freshness\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When using background purging, the frequency of your system cron determines how quickly cache invalidations are processed. The longer the interval between cron runs, the longer visitors may see stale content after updates.\u003C\u002Fp>\n\u003Cp>For minimal stale content, run your system cron every minute:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>* * * * * \u002Fusr\u002Fbin\u002Fphp \u002Fvar\u002Fwww\u002Fhtml\u002Fwp-cron.php\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If you can tolerate slightly longer delays, every 2-5 minutes is also acceptable. However, running cron less frequently (e.g., every 15 minutes) means cache purges may be delayed by that amount after content changes.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Note:\u003C\u002Fstrong> Scheduled posts are handled specially. When a scheduled post is published via WP-Cron, the cache is purged synchronously within the same cron run, ensuring immediate cache invalidation without waiting for the next cron execution.\u003C\u002Fp>\n\u003Cp>For detailed instructions on setting up a proper Linux-based WordPress cron, see: \u003Ca href=\"https:\u002F\u002Fwww.getpagespeed.com\u002Fweb-apps\u002Fwordpress\u002Fwordpress-cron-optimization\" rel=\"nofollow ugc\">WordPress Cron Optimization\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Disabling Background Purging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>If you have \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> defined but do not want background purging (for example, on low-traffic sites where immediate purges are preferred), you can force-disable cron-based purging by adding this to your \u003Ccode>wp-config.php\u003C\u002Fcode>:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'VHP_DISABLE_CRON_PURGING', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>With this constant set, all cache purges will execute immediately during the request, regardless of the \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> setting.\u003C\u002Fp>\n\u003Ch3>WP-CLI\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Purge\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Purge commands let you empty the cache.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish purge\u003C\u002Fcode> – Flush the entire site cache (equivalent to clicking “Empty Cache” in admin)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --all\u003C\u002Fcode> – Explicitly flush the entire site cache\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge \u003Curl>\u003C\u002Fcode> – Flush cache for a specific URL and all content below it (wildcard)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge \u003Curl> --url-only\u003C\u002Fcode> – Flush cache for only the exact URL specified (no wildcard)\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=\u003Ctag>\u003C\u002Fcode> – Flush cache by tag (requires Cache Tags mode to be enabled)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Examples:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish purge\u003C\u002Fcode> – Purge entire site\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --all\u003C\u002Fcode> – Same as above, more explicit\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fhello-world\u002F\u003C\u002Fcode> – Purge this URL and everything below it\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fhello-world\u002F --url-only\u003C\u002Fcode> – Purge only this exact URL\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge https:\u002F\u002Fexample.com\u002Fwp-content\u002Fthemes\u002F --wildcard\u003C\u002Fcode> – Purge all theme files\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=p-123\u003C\u002Fcode> – Purge all pages tagged with post ID 123\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish purge --tag=pt-post\u003C\u002Fcode> – Purge all cached pages of post type “post”\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Debug\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Debugging can help you figure out why your cache isn’t working as well as it could. The default is for your home page, but you can pass any URL on your domain.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish debug [\u003Curl>]\u003C\u002Fcode>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Available parameters:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>[--include-headers]\u003C\u002Fcode> —  Include headers in debug check output\u003C\u002Fli>\n\u003Cli>\u003Ccode>[--include-grep]\u003C\u002Fcode> — Grep active theme and plugin directories for common issues\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>DevMode\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Development mode allows you to disable the cache, temporarily.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish devmode [\u003Cactivate|deactivate|toggle>]\u003C\u002Fcode> – Change development mode state\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Async purge queue (cron-mode)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you define \u003Ccode>DISABLE_WP_CRON\u003C\u002Fcode> as \u003Ccode>true\u003C\u002Fcode> and run a real system cron for WordPress, Proxy Cache Purge can move heavy purge work into a small background queue that is processed by WP‑Cron.\u003C\u002Fp>\n\u003Cp>You can inspect and manage that queue via WP‑CLI:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ccode>wp varnish queue status\u003C\u002Fcode> – show whether cron-mode is active, if a full purge is queued, counts of queued URLs\u002Ftags, and the last queue run time.\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish queue process\u003C\u002Fcode> – process any items currently in the queue (useful to run after deploys or cache‑sensitive operations).\u003C\u002Fli>\n\u003Cli>\u003Ccode>wp varnish queue clear\u003C\u002Fcode> – clear the queue without sending any PURGE requests.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>These commands do not replace your normal WordPress cron (you still need a cron entry that calls \u003Ccode>wp cron event run --due-now\u003C\u002Fcode> or hits \u003Ccode>wp-cron.php\u003C\u002Fcode>), but they give you a simple operational handle when using cron‑mode.\u003C\u002Fp>\n\u003Ch4>Understanding Purge Behavior\u003C\u002Fh4>\n\u003Cp>There are different types of cache purges, and they behave differently:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Manual Purges (Admin Bar)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>“Purge Cache (All Pages)”\u003C\u002Fstrong> – Sends a single regex purge request to invalidate the entire cache. Always executes immediately.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>“Purge Cache (this page)”\u003C\u002Fstrong> – Purges only the exact URL you’re viewing. Always executes immediately.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Manual purges are always immediate, even when background cron-mode is enabled. This is intentional: when you click a button, you expect immediate results.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Automatic Purges (Post Save\u002FUpdate)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>When you save or update a post, the plugin automatically purges:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The post’s URL\u003C\u002Fli>\n\u003Cli>The homepage\u003C\u002Fli>\n\u003Cli>Category archive pages\u003C\u002Fli>\n\u003Cli>Tag archive pages\u003C\u002Fli>\n\u003Cli>Author archive page\u003C\u002Fli>\n\u003Cli>Date-based archives\u003C\u002Fli>\n\u003Cli>RSS feeds\u003C\u002Fli>\n\u003Cli>Related REST API endpoints\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This can be 20-50+ URLs depending on your site structure. When cron-mode is enabled, these automatic purges are queued and processed in the background to avoid slowing down the post editor.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Key Difference\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>  Action\u003Cbr \u002F>\n  URLs Purged\u003Cbr \u002F>\n  Uses Cron Queue?\u003C\u002Fp>\n\u003Cp>  “Purge Cache (All Pages)”\u003Cbr \u002F>\n  1 (regex)\u003Cbr \u002F>\n  No – always immediate\u003C\u002Fp>\n\u003Cp>  “Purge Cache (this page)”\u003Cbr \u002F>\n  1\u003Cbr \u002F>\n  No – always immediate\u003C\u002Fp>\n\u003Cp>  Post save\u002Fupdate\u003Cbr \u002F>\n  20-50+\u003Cbr \u002F>\n  Yes (if cron-mode enabled)\u003C\u002Fp>\n\u003Cp>If you need to immediately purge all URLs related to a specific post (not just the post URL), save the post – the automatic purge will handle all related URLs.\u003C\u002Fp>\n","Automatically empty proxy cached content when your site is modified.",40000,2164070,26,"2026-03-13T00:00:00.000Z","6.3.8","5.0","5.6",[21,23,78,79,80],"proxy","purge","varnish","https:\u002F\u002Fgithub.com\u002Fdvershinin\u002Fvarnish-http-purge","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fvarnish-http-purge.5.7.0.zip",{"slug":84,"name":85,"version":86,"author":87,"author_profile":88,"description":89,"short_description":90,"active_installs":91,"downloaded":92,"rating":93,"num_ratings":94,"last_updated":95,"tested_up_to":96,"requires_at_least":97,"requires_php":54,"tags":98,"homepage":100,"download_link":101,"security_score":93,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"nginx-cache","Nginx Cache","1.0.7","Till Krüss","https:\u002F\u002Fprofiles.wordpress.org\u002Ftillkruess\u002F","\u003Cp>Purge the \u003Ca href=\"http:\u002F\u002Fnginx.org\" rel=\"nofollow ugc\">Nginx\u003C\u002Fa> cache (FastCGI, Proxy, uWSGI) automatically when content changes or manually within WordPress.\u003C\u002Fp>\n\u003Cp>Requirements:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>The \u003Ca href=\"https:\u002F\u002Fcodex.wordpress.org\u002FFilesystem_API\" rel=\"nofollow ugc\">Filesystem API\u003C\u002Fa> needs to function without asking for credentials.\u003C\u002Fli>\n\u003Cli>Nginx and PHP need to run under the same user, or PHP’s user needs write access to Nginx’s cache path.\u003C\u002Fli>\n\u003C\u002Ful>\n","Purge the Nginx cache (FastCGI, Proxy, uWSGI) automatically when content changes or manually within WordPress.",10000,307696,92,23,"2024-11-26T20:26:00.000Z","6.7.5","3.1",[21,57,99,23,79],"flush","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnginx-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fnginx-cache.1.0.7.zip",{"slug":103,"name":104,"version":105,"author":106,"author_profile":107,"description":108,"short_description":109,"active_installs":110,"downloaded":111,"rating":27,"num_ratings":112,"last_updated":113,"tested_up_to":52,"requires_at_least":75,"requires_php":114,"tags":115,"homepage":117,"download_link":118,"security_score":119,"vuln_count":120,"unpatched_count":28,"last_vuln_date":121,"fetched_at":30},"lwscache","LWSCache","2.9","Aurélien LWS","https:\u002F\u002Fprofiles.wordpress.org\u002Faurelienlws\u002F","\u003Cp>This plugin, created by \u003Ca href=\"https:\u002F\u002Fwww.lws.fr\" rel=\"nofollow ugc\">LWS\u003C\u002Fa> help to automatically \u003Cstrong>manage your LWSCache purge when you edit your pages, post, messages…\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>It provide a way to \u003Cstrong>purge all your LWSCache\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>This plugin works only on servers using the LWSCache system. This cache is pre-installed with Classic shared \u003Ca href=\"https:\u002F\u002Fwww.lws.fr\u002Fhebergement_web.php\" rel=\"nofollow ugc\">web hosting\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwww.lws.fr\u002Fhebergement_wordpress.php\" rel=\"nofollow ugc\">WordPress hosting\u003C\u002Fa> and soon \u003Ca href=\"https:\u002F\u002Fwww.lws.fr\u002Fhebergement-cpanel.php\" rel=\"nofollow ugc\">cPanel hosting\u003C\u002Fa> from LWS.\u003C\u002Fp>\n\u003Cp>The loading speed of your site is crucial to its success. The more visitors your site has, the more RAM and CPU memory the system uses. The page is loaded slowly. So you need a cache system to avoid reloading the page when it is not necessary.\u003C\u002Fp>\n\u003Cp>In addition, the site’s page load speed is used in Google’s ranking algorithm. So caching plugins that can improve load times will \u003Cstrong>improve your SEO ranking\u003C\u002Fstrong>.  Low rankings, and therefore insufficient exposure, often do not allow you to make a living from your website. The loading time of most websites is less than three seconds. Beyond that, many users have already left the page.\u003C\u002Fp>\n\u003Cp>The LWS Cache tool is a system designed and developed by LWS. It \u003Cstrong>optimize the loading performance of your website\u003C\u002Fstrong> through the use of advanced caching mechanisms, configured at the server level. The tool uses the technologies provided by NGINX.\u003C\u002Fp>\n\u003Ch4>Functioning\u003C\u002Fh4>\n\u003Cp>When LWS Cache is enabled, a cache server is introduced between the visitor and the web server.\u003Cbr \u002F>\nThe aim is to reduce the number of script executions required. For that it keeps the result of the execution in memory for future requests requiring the same response. This means that the same script is no longer executed several times to achieve the same result.\u003C\u002Fp>\n\u003Cp>Thus, we eliminate the waiting time of the script execution on the page loading time. At the same time, we save the resources used during the script execution.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>The visitor requests the page from the web server\u003C\u002Fstrong>. Example: index.php. LWS Cache checks if the page has already been generated and stored in the cache\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>If yes\u003C\u002Fstrong>, the page is returned directly to the visitor without the need to access the web service and without executing the script\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If not\u003C\u002Fstrong>, the page is requested to be generated on the web service as a result of the script execution (PHP, NodeJS, Perl, Ruby, …).\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Once the page is generated, \u003Cstrong>LWS Cache determines if the page can be cached\u003C\u002Fstrong> (via headers, URL, …)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>If yes\u003C\u002Fstrong>, the page is saved in the cache and returned to the visitor\u003C\u002Fp>\n\u003Cp>\u003Cstrong>If not\u003C\u002Fstrong>, the page is saved in the microcache (short-lived cache) and returned to the visitor\u003C\u002Fp>\n\u003Ch4>Managing LWS Cache with the plugin\u003C\u002Fh4>\n\u003Cp>The WordPress LWS Cache plugin allows you to \u003Cstrong>automatically purge the cache\u003C\u002Fstrong> of your pages when you modify them or when you add\u002Fapprove comments.\u003C\u002Fp>\n\u003Cp>To \u003Cstrong>manage the plugin\u003C\u002Fstrong>, once connected to your WordPress administration console, go to the “Settings” menu and then “LWS Cache”.\u003C\u002Fp>\n\u003Cp>From the settings page, you can enable\u002Fdisable automatic emptying. You can define when to automatically empty the LWS Cache and completely purge the cache.\u003C\u002Fp>\n\u003Cp>A button for emptying the entire cache can be found anywhere in the WordPress admin console (in the quick access bar at the top of the screen).\u003C\u002Fp>\n\u003Ch4>Key Features\u003C\u002Fh4>\n\u003Cp>Several settings are available to manage your LWS Cache, you can enable or disable these settings:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>Automatic purge\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Home Page Purge (when a post is modified or added, when a published post is trashed)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Purge Post\u002FPage\u002FCustom Post Type (when a post is published, when a comment is approved\u002Fpublished, when a comment is unapproved\u002Fdeleted)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Purge Archives (date, category, tag, author, custom taxonomies)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Purge all cache\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n","This plugin lets you manage and automatically purge your hosting's LWSCache whenever you edit your website's content",8000,149947,6,"2025-08-28T13:46:00.000Z","7.0",[21,116,23],"lws","https:\u002F\u002Fwww.lws.fr\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Flwscache.2.9.zip",99,1,"2025-08-28 00:00:00",{"slug":123,"name":124,"version":125,"author":126,"author_profile":127,"description":128,"short_description":129,"active_installs":130,"downloaded":131,"rating":27,"num_ratings":132,"last_updated":133,"tested_up_to":52,"requires_at_least":134,"requires_php":135,"tags":136,"homepage":138,"download_link":139,"security_score":119,"vuln_count":120,"unpatched_count":28,"last_vuln_date":140,"fetched_at":30},"hestia-nginx-cache","Hestia Nginx Cache","2.4.3","Juni","https:\u002F\u002Fprofiles.wordpress.org\u002Fjakobbouchard\u002F","\u003Cp>\u003Cstrong>Important\u003C\u002Fstrong>: Hestia 1.6.12 fixes an issue where purging the cache could make the website unavailable, resulting in a 502 error. If you aren’t using this version, please upgrade!\u003C\u002Fp>\n\u003Cp>This plugin automatically purges the Nginx cache after you make a website change such as updating a post or changing your theme.\u003C\u002Fp>\n\u003Cp>You also have the ability to manually purge the cache using a button in the WordPress admin bar.\u003C\u002Fp>\n","Purged the Nginx cache automatically after making website changes. Uses the new HestiaCP API, released in 1.6.0.",1000,14525,9,"2025-06-25T22:48:00.000Z","4.8","5.4",[21,99,137,23,79],"hestia","https:\u002F\u002Fgithub.com\u002Fimjuniper\u002Fhestia-nginx-cache","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhestia-nginx-cache.2.4.3.zip","2024-12-30 00:00:00",{"attackSurface":142,"codeSignals":170,"taintFlows":179,"riskAssessment":180,"analyzedAt":188},{"hooks":143,"ajaxHandlers":166,"restRoutes":167,"shortcodes":168,"cronEvents":169,"entryPointCount":28,"unprotectedCount":28},[144,150,154,158,161],{"type":145,"name":146,"callback":147,"file":148,"line":149},"action","admin_menu","add_settings_page","src\\php\\Main.php",57,{"type":145,"name":151,"callback":152,"file":148,"line":153},"admin_init","setup_fields",64,{"type":145,"name":155,"callback":156,"priority":27,"file":148,"line":157},"plugins_loaded","load_textdomain",65,{"type":145,"name":159,"callback":159,"file":148,"line":160},"admin_enqueue_scripts",66,{"type":145,"name":162,"callback":163,"priority":164,"file":148,"line":165},"parse_request","mod_pagespeed_arg",20,68,[],[],[],[],{"dangerousFunctions":171,"sqlUsage":172,"outputEscaping":174,"fileOperations":28,"externalRequests":177,"nonceChecks":120,"capabilityChecks":28,"bundledLibraries":178},[],{"prepared":28,"raw":28,"locations":173},[],{"escaped":175,"rawEcho":28,"locations":176},21,[],2,[],[],{"summary":181,"deductions":182},"The \"kagg-pagespeed-module\" v2.2.0 plugin demonstrates a strong security posture based on the provided static analysis. The absence of any identified dangerous functions, raw SQL queries, file operations, or unsanitized taint flows is highly encouraging. Furthermore, the plugin exhibits excellent output escaping practices and correctly uses prepared statements for its SQL queries. The presence of a nonce check, even with a limited attack surface, also suggests a basic level of security awareness in its development. \n\nHowever, there are a few areas that warrant attention. The plugin performs external HTTP requests, which can introduce risks if the target endpoints are compromised or if the requests are not properly validated or secured. The lack of capability checks on any potential entry points (though none were identified) is a concern; if new entry points were to be introduced in future versions, they might lack proper access control. The vulnerability history is clean, indicating a lack of known past issues, which is a positive sign, but it doesn't negate the potential for undiscovered vulnerabilities. \n\nOverall, the plugin appears to be developed with security in mind, especially regarding common web vulnerabilities like SQL injection and cross-site scripting. The primary concerns lie in the potential risks associated with external HTTP requests and the absence of explicit capability checks, which could be a weakness if the attack surface expands. Continued vigilance and code reviews are recommended.",[183,186],{"reason":184,"points":185},"External HTTP requests present potential risks",5,{"reason":187,"points":185},"Lack of capability checks on entry points","2026-03-16T20:18:43.106Z",{"wat":190,"direct":199},{"assetPaths":191,"generatorPatterns":194,"scriptPaths":195,"versionParams":196},[192,193],"\u002Fwp-content\u002Fplugins\u002Fkagg-pagespeed-module\u002Fassets\u002Fcss\u002Fadmin.css","\u002Fwp-content\u002Fplugins\u002Fkagg-pagespeed-module\u002Fassets\u002Fjs\u002Fadmin.js",[],[],[197,198],"kagg-pagespeed-module\u002Fassets\u002Fcss\u002Fadmin.css?ver=","kagg-pagespeed-module\u002Fassets\u002Fjs\u002Fadmin.js?ver=",{"cssClasses":200,"htmlComments":211,"htmlAttributes":212,"restEndpoints":221,"jsGlobals":222,"shortcodeOutput":224},[201,202,203,204,205,206,207,208,209,210],"ps-menu-image","ps-menu-title","ps-card","ps-card-section","ps-card-content","ps-card-title","ps-card-control","ps-btn","ps-toggle","ps-checkbox",[],[213,214,215,216,217,218,219,220],"id=\"dev_mode\"","class=\"ps-checkbox\"","id=\"ps-success\"","id=\"ps-error\"","id=\"purge_styles\"","id=\"purge_entire_cache\"","type=\"button\"","class=\"ps-btn\"",[],[223],"window.mod_pagespeed_ajax_object",[]]