[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f5vgUzus0udktx2pfVW8TtZdC3LK3vsn1rDT-POZu1rA":3,"$fST5W2Ija6sKeSi4PsRcZE-E-XIydMzZm_ieyBUWLU7Y":191,"$fqO9YABhG1GmryI-dp1GiVB3FPc47kKtBvB2u90Me8j0":196},{"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":18,"download_link":23,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":27,"discovery_status":28,"vulnerabilities":29,"developer":30,"crawl_stats":26,"alternatives":36,"analysis":143,"fingerprints":176},"dynamic-asset-versioning","Dynamic Asset Versioning","0.1.0","Steve Grunwell","https:\u002F\u002Fprofiles.wordpress.org\u002Fstevegrunwell\u002F","\u003Cp>WordPress asset versioning can be a double-edged sword: on one-hand, it’s extremely effective for cache-busting, ensuring you aren’t sharing stale scripts or styles to your visitors. On the other hand, having to manually increment a version number is a pain (even \u003Ca href=\"https:\u002F\u002F10up.github.io\u002FEngineering-Best-Practices\u002Fphp\u002F#asset-versioning\" rel=\"nofollow ugc\">as a constant\u003C\u002Fa>), often resulting in a version control history full of “bumping the version number” commits.\u003C\u002Fp>\n\u003Cp>Dynamic Asset Versioning aims to simplify this process: if an enqueued asset doesn’t have an explicit version number, the plugin will get the timestamp of the last time the file was changed and use that as the version number. It’s easy: you touch the file, the version number is updated automatically.\u003C\u002Fp>\n\u003Ch4>Usage\u003C\u002Fh4>\n\u003Cp>Once Dynamic Asset Versioning is active, it will automatically determine version numbers based on file modification time for any [non-core] files that have been enqueued using \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Ffunctions\u002Fwp_enqueue_style\u002F\" rel=\"nofollow ugc\">\u003Ccode>wp_enqueue_style()\u003C\u002Fcode>\u003C\u002Fa> or \u003Ca href=\"https:\u002F\u002Fdeveloper.wordpress.org\u002Freference\u002Ffunctions\u002Fwp_enqueue_style\u002F\" rel=\"nofollow ugc\">\u003Ccode>wp_enqueue_script()\u003C\u002Fcode>\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Example\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>wp_enqueue_style(\n    'my-theme-styles',\n    get_template_directory_uri() . '\u002Fassets\u002Fcss\u002Fmy-styles.css',\n    array( 'some-other-styles' ),\n    false, \u002F\u002F Don't worry about it, Dynamic Asset Versioning has you covered!\n    'screen'\n);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Ch4>Special thanks\u003C\u002Fh4>\n\u003Cp>A special thanks goes out to \u003Ca href=\"http:\u002F\u002F10up.com\" rel=\"nofollow ugc\">10up\u003C\u002Fa>, who helped inspire the original concept of this plugin.\u003C\u002Fp>\n","Dynamically set asset version numbers based on file modification times, preventing stale caches.",30,5315,100,1,"2016-12-14T20:30:00.000Z","4.7.33","4.7","",[20,21,22],"assets","cache","versioning","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdynamic-asset-versioning.0.2.0.zip",85,0,null,"2026-04-06T09:54:40.288Z","no_bundle",[],{"slug":31,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":33,"avg_security_score":24,"avg_patch_time_days":11,"trust_score":34,"computed_at":35},"stevegrunwell",7,2150,84,"2026-05-20T10:13:16.730Z",[37,59,73,97,122],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":47,"num_ratings":48,"last_updated":49,"tested_up_to":50,"requires_at_least":51,"requires_php":18,"tags":52,"homepage":18,"download_link":57,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":58},"prevent-browser-caching","Prevent Browser Caching","2.3.5","kostyatereshchuk","https:\u002F\u002Fprofiles.wordpress.org\u002Fkostyatereshchuk\u002F","\u003Cp>Are you a frontend developer? Do you want to clear browser cache for all users? Just activate this plugin and show your work!\u003C\u002Fp>\n\u003Cp>Prevent Browser Caching allows you to update the assets version of all CSS and JS files automatically or manually in one click.\u003C\u002Fp>\n\u003Cp>Now you can show the latest changes on the site without asking the client to clear the cache.\u003C\u002Fp>\n\u003Ch4>How it works?\u003C\u002Fh4>\n\u003Cp>Usually, WordPress loads assets using query param “ver” in the URL (e.g., style.css?ver=4.9.6). It allows browsers to cache these files until the parameter will not be updated.\u003C\u002Fp>\n\u003Cp>To prevent caching of CSS and JS files, this plugin adds a unique number (e.g., 1526905286) to the “ver” parameter (e.g., style.css?ver=4.9.6.1526905286) for all links, loaded using wp_enqueue_style and wp_enqueue_script functions.\u003C\u002Fp>\n\u003Ch4>For developers\u003C\u002Fh4>\n\u003Cp>By default, this plugin updates all assets files every time a user loads a page and adds options in the admin panel (Settings -> Prevent Browser Caching) which allows you to configure updating of these files.\u003C\u002Fp>\n\u003Cp>But you can also set the version of CSS and JS files programmatically.\u003C\u002Fp>\n\u003Cp>Just insert this code in functions.php file of your theme and change the value of assets_version when you need to update assets:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>prevent_browser_caching( array( \n    'assets_version' => '123' \n) );\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Updates the assets version of all CSS and JS files. Shows the latest changes on the site without asking the client to clear browser cache.",10000,110023,98,28,"2024-04-09T17:18:00.000Z","6.5.8","4.0",[20,53,54,55,56],"browser-cache","clear","development","frontend","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fprevent-browser-caching.2.3.5.zip","2026-04-16T10:56:18.058Z",{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":44,"active_installs":66,"downloaded":67,"rating":13,"num_ratings":68,"last_updated":69,"tested_up_to":70,"requires_at_least":51,"requires_php":18,"tags":71,"homepage":18,"download_link":72,"security_score":24,"vuln_count":25,"unpatched_count":25,"last_vuln_date":26,"fetched_at":58},"disable-version-caching","Disable Version Caching – Khanakia","1.0.1","mrkhanakia","https:\u002F\u002Fprofiles.wordpress.org\u002Fmrkhanakia\u002F","\u003Cp>Are you a frontend developer? Do you want to clear browser cache for all users? Just activate this plugin and show your work!\u003C\u002Fp>\n\u003Cp>Disable Version Caching allows you to update the assets version of all CSS and JS files automatically or manually in one click.\u003C\u002Fp>\n\u003Cp>Now you can show the latest changes on the site without asking the client to clear the cache.\u003C\u002Fp>\n\u003Ch4>How it works?\u003C\u002Fh4>\n\u003Cp>Usually, WordPress loads assets using query param “ver” in the URL (e.g., style.css?ver=4.9.6). It allows browsers to cache these files until the parameter will not be updated.\u003C\u002Fp>\n\u003Cp>To prevent caching of CSS and JS files, this plugin adds a unique number (e.g., 1526903434) to the “ver” parameter (e.g., style.css?ver=4.9.6.1526903434) for all links, loaded using wp_enqueue_style and wp_enqueue_script functions.\u003C\u002Fp>\n\u003Ch4>For developers\u003C\u002Fh4>\n\u003Cp>By default, this plugin updates all assets files every time a user loads a page and adds options in the admin panel (Settings -> Disable Version Caching) which allows you to configure updating of these files.\u003C\u002Fp>\n\u003Cp>But you can also set the version of CSS and JS files programmatically.\u003C\u002Fp>\n\u003Cp>Just insert this code in functions.php file of your theme and change the value of assets_version when you need to update assets:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>disable_version_caching( array( \n    'assets_version' => '123' \n) );\n\u003C\u002Fcode>\u003C\u002Fpre>\n",200,3683,3,"2020-11-30T06:45:00.000Z","5.5.18",[20,53,54,55,56],"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdisable-version-caching.zip",{"slug":74,"name":75,"version":76,"author":77,"author_profile":78,"description":79,"short_description":80,"active_installs":81,"downloaded":82,"rating":47,"num_ratings":83,"last_updated":84,"tested_up_to":85,"requires_at_least":86,"requires_php":18,"tags":87,"homepage":92,"download_link":93,"security_score":94,"vuln_count":95,"unpatched_count":25,"last_vuln_date":96,"fetched_at":58},"wp-fastest-cache","WP Fastest Cache – WordPress Cache Plugin","1.4.7","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",1000000,64008681,4210,"2026-04-07T18:56:00.000Z","6.9.4","5.7",[21,88,89,90,91],"core-web-vitals","optimize","pagespeed","performance","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-fastest-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-fastest-cache.1.4.7.zip",76,35,"2025-11-26 21:34:28",{"slug":98,"name":99,"version":100,"author":101,"author_profile":102,"description":103,"short_description":104,"active_installs":81,"downloaded":105,"rating":106,"num_ratings":107,"last_updated":108,"tested_up_to":109,"requires_at_least":110,"requires_php":111,"tags":112,"homepage":117,"download_link":118,"security_score":119,"vuln_count":120,"unpatched_count":25,"last_vuln_date":121,"fetched_at":58},"wp-optimize","WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance","4.5.1","David Anderson \u002F Team Updraft","https:\u002F\u002Fprofiles.wordpress.org\u002Fdavidanderson\u002F","\u003Cp>MORE THAN A CACHING PLUGIN\u003C\u002Fp>\n\u003Cp>\u003Cstrong>\u003Ca href=\"https:\u002F\u002Fwww.teamupdraft.com\u002Fwp-optimize?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=wp_optimize&utm_creative_format=description\" rel=\"nofollow ugc\">WP-Optimize\u003C\u002Fa> is trusted by more than 1 million WordPress website\u003C\u002Fstrong> owners to \u003Cstrong>boost performance\u003C\u002Fstrong> and \u003Cstrong>reduce page load times\u003C\u002Fstrong> to improve your site’s \u003Cstrong>user experiences\u003C\u002Fstrong> and \u003Cstrong>SERP rankings in Google.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>It does this in four clever ways:\u003C\u002Fp>\n\u003Cp>\u003Cstrong>1. It caches your site\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Caching is the process of storing a temporary HTML version of your site on the server so it can be retrieved more quickly for the user.\u003C\u002Fp>\n\u003Cp>It’s a sure-fire way to ensure web pages load at lightning-fast speed. Turn it on in just one click.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>2. It compresses images\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Large images can really impact page speed load times. WP-Optimize makes it easy to identify and compress images to your preferred lossy \u002F lossless settings in a couple of clicks.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>3. It cleans the database\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>Your WordPress database stores everything that you need, plus some things that you don’t. WP-Optimize cleans and optimizes the database to speed up your site and save server resources.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>4. It minifies\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>On top of its three main features, WP-Optimize Cache also has the more advanced minification feature.\u003C\u002Fp>\n\u003Cp>Together with caching, minification dramatically improves performance and page speed load time.\u003C\u002Fp>\n\u003Ch3>1. CACHE YOUR SITE\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Turn on caching in just one click:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>WP-Optimize automatically and optimally configures itself for your WordPress site. Turn it on in one-click or refine its settings if you prefer.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>More cache features:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Cache preloading:\u003C\u002Fstrong> This feature emulates a visit to your site, meaning cached files are served straight away, speeding up your site from the very first visit.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>GZIP Compression:\u003C\u002Fstrong> When the server isn’t configured to do so, WP-Optimize delivers HTML, CSS and JS files  to the user’s browser as smaller, compressed files, reducing the size of pages and style sheets by up to 90%!\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Preload key requests:\u003C\u002Fstrong> Recommended by Google to improve page speed times. Critical resources (things like font files) get loaded first, so the page loads much faster \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Use cache settings to:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Serve cached content to logged in users:\u003C\u002Fstrong> Turn this on if content stays the same for logged in users (or turn on and exclude URLs where content does change e.g. my account areas).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Exclude content from cache:\u003C\u002Fstrong> Exclude by URL, conditional tags, browser agent strings or list cookies that should prevent caching when set (advanced user settings).\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Deliver device-specific cache:\u003C\u002Fstrong> Serve separate cache files to desktop and mobile devices . This ensures that responsive features e.g. desktop and mobile menus are cached separately and served correctly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>User per role cache:\u003C\u002Fstrong> Useful if your website delivers different content to different user roles. e.g. an e-commerce site that displays different content to resellers or consumers \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>User specific cache:\u003C\u002Fstrong> Serves separate cache files to individual users. Useful for websites with personalised content e.g. Learning management systems \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Cache purging permissions:\u003C\u002Fstrong> Select which user roles are allowed to purge the cache e.g. admin only or perhaps a ‘teacher’ role in an LMS setting only \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>2. COMPRESS IMAGES\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Lossy or lossless compression options:\u003C\u002Fstrong> Choose between maximum space saving, best image quality or somewhere in-between.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>WebP conversion:\u003C\u002Fstrong> Recommended by Google, WebP can achieve up to 34% smaller file sizes compared to JPEG and up to 26% compared to PNG.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Auto-compress:\u003C\u002Fstrong> Check a box and every new image you upload will automatically be compressed to your preferred lossy \u002F lossless settings.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Bulk compression:\u003C\u002Fstrong> Compress every existing image on your site with the press of a button.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Restore original:\u003C\u002Fstrong> Gone too far? Revert images back to their original in one click.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Retain EXIF image data:\u003C\u002Fstrong> Check a box to retain EXIF image data during compression.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Lazy Load:\u003C\u002Fstrong> Webpages load much faster by loading web parts gradually, when they’re needed vs simultaneous loading of everything, all at once \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Delete orphaned images:\u003C\u002Fstrong> Identify and delete unused images from your WordPress website, saving disk space \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Delete unused image sizes:\u003C\u002Fstrong> WordPress creates multiple sizes for every uploaded image causing the uploads folder to become bloated. Scan for image sizes not in use and remove them to save further disk space \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3. CLEAN AND OPTIMIZE THE DATABASE\u003C\u002Fh3>\n\u003Cp>Cleans-up database tables, post revisions, auto draft posts, trashed posts, spam, trashed comments and more. Choose what to optimize or it’s one click to clean out the lot.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Schedule clean-ups:\u003C\u002Fstrong> So you can set and forget. Choose from daily, weekly, fortnightly or monthly.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Flexible clean-up schedules:\u003C\u002Fstrong> You may wish to optimize database tables more frequently than you remove unapproved comments (for example). Choose the specific time and day when tasks should run \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Retain a set number of weeks’ data during clean-ups:\u003C\u002Fstrong> Just in case you need to retrieve something.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Back up before clean-ups:\u003C\u002Fstrong> If you delete something you shouldn’t, restore it in a couple of clicks with UpdraftPlus.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Power tweak – Turbo boost for WooCommerce:\u003C\u002Fstrong>  Unique to WP-Optimize, this power tweak boosts performance by replacing a slow query in WooCommerce with two much more efficient queries. E-commerce sites transacting high numbers of orders stand to gain here \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Power tweak – Boost performance by indexing the postmeta table:\u003C\u002Fstrong> This unique power tweak works by allowing the WordPress postmeta table to be indexed, improving performance \u003Cstrong>[Premium]\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>4. MINIFY AND COMBINE HTML, CSS AND JAVASCRIPT\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Cstrong>Minify in just one click:\u003C\u002Fstrong> Minifies HTML, JavaScript and CSS. Toggle on or off or customise each one under ‘settings’.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Customise minification:\u003C\u002Fstrong> Minify only (removing unnecessary code e.g line breaks and white spacing) or minify and merge. Apply the same or different settings to HTML, CSS and JavaScript.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Asynchronous loading:\u003C\u002Fstrong> Choose non-critical CSS and JavaScript files to load in the background and independently of other resources e.g. analytics or pixel scripts. Loading asynchronously eliminates render blocking and improves page speed.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Exclude files from being minified:\u003C\u002Fstrong> Specify CSS and JavaScript files to exclude from minification.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Optimize fonts:\u003C\u002Fstrong> Optimize Font Awesome and Google Fonts. Inline the font files, inherit from CSS settings or load CSS \u002F Javascript asynchronously instead.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Preload assets:\u003C\u002Fstrong> WP-Optimize visits each web page on your site so the code is minified and preloaded for real life users, right from their very first visit.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cstrong>Preload key requests:\u003C\u002Fstrong> Recommended by Google to improve page speed times. Critical resources (things like font files) get loaded first, so the page loads much faster.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>WHY WP-OPTIMIZE?\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>It’s brought to you by \u003Ca href=\"https:\u002F\u002Fwww.teamupdraft.com?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=teamupdraft&utm_creative_format=description\" rel=\"nofollow ugc\">TeamUpdraft\u003C\u002Fa>, the team behind the world’s most trusted backup, migration and restoration plugin.\u003C\u002Fli>\n\u003Cli>It’s easy to use.\u003C\u002Fli>\n\u003Cli>It packs a punch for a free plugin.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>WP-Optimize brings the best cache and optimization technology together into one single, seamless plugin to make your WordPress site fast, lean and efficient.\u003C\u002Fp>\n\u003Ch3>PREMIUM FEATURES AT A GLANCE\u003C\u002Fh3>\n\u003Cp>Our free version of WP-Optimize Cache is great, but we also have an even more powerful \u003Ca href=\"https:\u002F\u002Fwww.teamupdraft.com\u002Fwp-optimize\u002Fpricing?utm_source=wpo-wp-dir&utm_medium=referral&utm_campaign=plugin-dir&utm_content=premium_version&utm_creative_format=description\" rel=\"nofollow ugc\">Premium version\u003C\u002Fa> with extra features that offer the ultimate in freedom and flexibility:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Multisite Support:\u003C\u002Fstrong> extends database optimisations so they function for multiple WordPress sites at a time. If you manage more than one website, you will need WP-Optimize Cache Premium.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Flexibility and Control:\u003C\u002Fstrong> gives you the power to optimize select individual tables or a particular combination of tables on one or more WordPress websites, rather than having to optimize all database tables.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Deleting unused and unwanted images:\u003C\u002Fstrong> removes orphaned images from your WordPress site, plus images of a certain, pre-defined size.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sophisticated Scheduling:\u003C\u002Fstrong> offers a wide range of options for scheduling automatic optimization. Specify an exact time and run clean-ups daily, weekly, fortnightly or monthly and perform any number of additional once off optimizations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Seamless Graphical User Interface:\u003C\u002Fstrong> for superb clarity in scheduling and managing of multi-site optimizations.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WP-CLI support:\u003C\u002Fstrong> provides a way to manage optimizations from command-line interface if you have lots of sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Lazy Loading:\u003C\u002Fstrong> load only the images and part of a web-page when it is visible to the user so they can see something very quickly.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Optimization Preview:\u003C\u002Fstrong> gives users the ability to preview, select and remove data and records available for optimization from the database.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Preload key requests:\u003C\u002Fstrong> preload assets such as web fonts and icon fonts, as recommended by Google PageSpeed Insights.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Premium support\u003C\u002Fstrong> – caching is one of the most complex things you can do for a website, so premium support offers you peace of mind there’s someone to talk quickly to if you need any technical answers or help configuring the optimizations of cache settings for your website.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Translations\u003C\u002Fh4>\n\u003Cp>Translators are welcome to contribute to the plugin. Please use the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-optimize\" rel=\"nofollow ugc\">WordPress translation website\u003C\u002Fa>.\u003C\u002Fp>\n","Get caching and more with this powerful cache plugin. Cache, optimize images, clean your database and minify for maximum performance.",55270328,96,2569,"2026-03-25T10:42:00.000Z","7.0","4.9","7.2",[21,113,114,115,116],"caching","image-cache","minify","performance-cache","https:\u002F\u002Fteamupdraft.com\u002Fwp-optimize","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-optimize.4.5.1.zip",92,5,"2026-05-06 15:34:39",{"slug":123,"name":124,"version":125,"author":126,"author_profile":127,"description":128,"short_description":129,"active_installs":81,"downloaded":130,"rating":131,"num_ratings":132,"last_updated":133,"tested_up_to":85,"requires_at_least":134,"requires_php":135,"tags":136,"homepage":138,"download_link":139,"security_score":140,"vuln_count":141,"unpatched_count":25,"last_vuln_date":142,"fetched_at":58},"wp-super-cache","WP Super Cache","3.1.0","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, loaded before most of WordPress. Add your own plugin either by putting it in the wp-content\u002Fplugins\u002Fwp-super-cache-plugins directory, or by calling wpsc_add_plugin( $name ) with the full path to the plugin.\u003C\u002Fp>\n\u003Cp>The cookies used to identify “known users” can be modified with wpsc_add_cookie( $name ) and wpsc_delete_cookie( $name ). 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.\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>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>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. Check your access_logs for wp-cron.php entries and that your hostname resolves to the external IP address other servers on the network\u002FInternet use.\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>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 page is ok but posts and pages give a 404? Go to Settings->permalinks and click “Save” once you’ve selected a custom permalink structure. You may need to manually update your .htaccess file.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If certain characters do not appear correctly on your website your server may not be configured correctly. You need to tell visitors what character set is used. Go to Settings->Reading and copy the ‘Encoding for pages and feeds’ value. Edit the .htaccess file with all your Supercache and WordPress rewrite rules and add this at the top, replacing CHARSET with the copied value. (for example, ‘UTF-8’)\u003C\u002Fp>\n\u003Cpre>\u003Ccode>AddDefaultCharset CHARSET\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>The error message, “WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory.” appears at the end of every page. You can delete wp-content\u002Fadvanced-cache.php and reload the plugin settings page or edit wp-config.php and look for WPCACHEHOME and make sure it points at the wp-super-cache folder. This will normally be wp-content\u002Fplugins\u002Fwp-super-cache\u002F but you’ll likely need the full path to that file (so it’s easier to let the settings page fix it). If it is not correct the caching engine will not load.\u003C\u002Fli>\n\u003Cli>If your server is running into trouble because of the number of semaphores used by the plugin it’s because your users are using file locking which is not recommended (but is needed by a small number of users). You can globally disable file locking by defining the constant WPSC_DISABLE_LOCKING, or defining the constant WPSC_REMOVE_SEMAPHORE so that sem_remove() is called after every page is cached but that seems to cause problems for other processes requesting the same semaphore. Best to disable it.\u003C\u002Fli>\n\u003Cli>Set the variable $htaccess_path in wp-config.php or wp-cache-config.php to the path of your global .htaccess if the plugin is looking for that file in the wrong directory. This might happen if you have WordPress installed in an unusual way.\u003C\u002Fli>\n\u003C\u002Fol>\n","A very fast caching engine for WordPress that produces static html files.",62825761,86,1341,"2026-04-14T15:49:00.000Z","6.8","7.4",[21,113,91,137,123],"wp-cache","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.1.0.zip",95,12,"2022-10-03 00:00:00",{"attackSurface":144,"codeSignals":160,"taintFlows":167,"riskAssessment":168,"analyzedAt":175},{"hooks":145,"ajaxHandlers":156,"restRoutes":157,"shortcodes":158,"cronEvents":159,"entryPointCount":25,"unprotectedCount":25},[146,153],{"type":147,"name":148,"callback":149,"priority":150,"file":151,"line":152},"filter","script_loader_src","anonymous",10,"dynamic-asset-versioning.php",72,{"type":147,"name":154,"callback":149,"priority":150,"file":151,"line":155},"style_loader_src",87,[],[],[],[],{"dangerousFunctions":161,"sqlUsage":162,"outputEscaping":164,"fileOperations":25,"externalRequests":25,"nonceChecks":25,"capabilityChecks":25,"bundledLibraries":166},[],{"prepared":25,"raw":25,"locations":163},[],{"escaped":25,"rawEcho":25,"locations":165},[],[],[],{"summary":169,"deductions":170},"The plugin \"dynamic-asset-versioning\" v0.1.0 exhibits a strong security posture based on the provided static analysis. The absence of any identified attack surface points, such as AJAX handlers, REST API routes, shortcodes, or cron events, significantly reduces the potential for external exploitation. Furthermore, the code demonstrates excellent practices with 100% of SQL queries using prepared statements and all output being properly escaped. The lack of dangerous functions, file operations, external HTTP requests, and the presence of non-existent nonce and capability checks also contribute to its secure design.\n\nHowever, the primary concern arises from the complete absence of any identified security checks (nonce and capability checks). While the attack surface is currently zero, this indicates a potential oversight that could become a critical vulnerability if new entry points are introduced without proper authentication or authorization mechanisms. The lack of any recorded vulnerabilities in its history is a positive sign, suggesting good development practices or simply a lack of prior scrutiny. In conclusion, the plugin is currently very secure due to its minimal attack surface and good coding hygiene, but the omission of basic security checks is a notable weakness that warrants attention for future development.",[171,173],{"reason":172,"points":120},"Missing nonce checks",{"reason":174,"points":120},"Missing capability checks","2026-04-16T11:17:04.591Z",{"wat":177,"direct":184},{"assetPaths":178,"generatorPatterns":180,"scriptPaths":181,"versionParams":182},[179],"\u002Fwp-content\u002Fplugins\u002Fdynamic-asset-versioning\u002F",[],[148],[183],"ver",{"cssClasses":185,"htmlComments":186,"htmlAttributes":187,"restEndpoints":188,"jsGlobals":189,"shortcodeOutput":190},[],[],[],[],[],[],{"error":192,"url":193,"statusCode":194,"statusMessage":195,"message":195},true,"http:\u002F\u002Flocalhost\u002Fapi\u002Fplugins\u002Fdynamic-asset-versioning\u002Fbundle",404,"no bundle for this plugin yet",{"slug":4,"current_version":6,"total_versions":197,"versions":198},2,[199,206],{"version":200,"download_url":23,"svn_tag_url":201,"released_at":26,"has_diff":202,"diff_files_changed":203,"diff_lines":26,"trac_diff_url":204,"vulnerabilities":205,"is_current":202},"0.2.0","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdynamic-asset-versioning\u002Ftags\u002F0.2.0\u002F",false,[],"https:\u002F\u002Fplugins.trac.wordpress.org\u002Fchangeset?old_path=%2Fdynamic-asset-versioning%2Ftags%2F0.1.0&new_path=%2Fdynamic-asset-versioning%2Ftags%2F0.2.0",[],{"version":6,"download_url":207,"svn_tag_url":208,"released_at":26,"has_diff":202,"diff_files_changed":209,"diff_lines":26,"trac_diff_url":26,"vulnerabilities":210,"is_current":192},"https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdynamic-asset-versioning.0.1.0.zip","https:\u002F\u002Fplugins.svn.wordpress.org\u002Fdynamic-asset-versioning\u002Ftags\u002F0.1.0\u002F",[],[]]