[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fC1DIEdIQj11Dlu07LBSKIQpaxulUsAqel5o76-nek-0":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":144,"fingerprints":315},"hyper-cache-extended","Hyper Cache Extended","1.6.3","mlazarov","https:\u002F\u002Fprofiles.wordpress.org\u002Fmlazarov\u002F","\u003Cp>Hyper Cache Extended is a new cache system for WordPress, specifically written for\u003Cbr \u002F>\npeople which have their blogs on low resources hosting provider\u003Cbr \u002F>\n(cpu and mysql). It works even with hosting based on Microsoft IIS (just tuning\u003Cbr \u002F>\nthe configuration). It has three invalidation method: all the cache, single post\u003Cbr \u002F>\nbased and nothing but with control on home and archive pages invalidation.\u003Cbr \u002F>\nHyper Cache Extended is based on original wordpress plugin “Hyper Cache” wich is\u003Cbr \u002F>\nwriten by Satollo (https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fhyper-cache)\u003C\u002Fp>\n\u003Cp>It has not yet tested for multisite configuration (WordPress 3.0 feature).\u003C\u002Fp>\n\u003Cp>Some features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>compatible with the plugin wp-pda which enables a blog to be \u003Cem>accessible from mobile devices\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>manages (both) \u003Cem>plain and gzip compressed pages\u003C\u002Fem>\u003C\u002Fli>\n\u003Cli>autoclean system to reduce the disk usage\u003C\u002Fli>\n\u003Cli>404 caching\u003C\u002Fli>\n\u003Cli>redirects caching\u003C\u002Fli>\n\u003Cli>easy to configure\u003C\u002Fli>\n\u003Cli>Global Translator compatibility\u003C\u002Fli>\n\u003Cli>Last Modified http header compatibility with 304 responses\u003C\u002Fli>\n\u003Cli>compressed storage to reduce the disk space usage\u003C\u002Fli>\n\u003Cli>agents, urls and cookies based rejection configurable\u003C\u002Fli>\n\u003Cli>easy to integrated with other plugins\u003C\u002Fli>\n\u003Cli>option to move cache to other partition\u002Fdisk\u003C\u002Fli>\n\u003Cli>only serve cached pages when web server average load is above a certain number\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>More can be read on the \u003Ca href=\"http:\u002F\u002Fmarto.lazarov.org\u002Fplugins\u002Fhyper-cache-extended\" rel=\"nofollow ugc\">official plugin page\u003C\u002Fa> and write me\u003Cbr \u002F>\nif you have issues to lazarov@mail.bg\u003C\u002Fp>\n\u003Cp>Contribute to project:\u003Cbr \u002F>\nhttp:\u002F\u002Fgithub.com\u002Fmlazarov\u002FHyper-Cache-Extended\u003C\u002Fp>\n\u003Cp>Thanks to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Satollo which is the creator of Hyper Cache\u003C\u002Fli>\n\u003Cli>Amaury Balmer for internationalization and other modifications\u003C\u002Fli>\n\u003Cli>Frank Luef for german translation\u003C\u002Fli>\n\u003Cli>HypeScience, Martin Steldinger, Giorgio Guglielmino for test and bugs submissions\u003C\u002Fli>\n\u003Cli>Ishtiaq to ask me about compatibility with wp-pda\u003C\u002Fli>\n\u003Cli>Gene Steinberg to ask for an autoclean system\u003C\u002Fli>\n\u003Cli>Marcis Gasun (fatcow.com) for Bielorussian translation\u003C\u002Fli>\n\u003Cli>many others I don’t remember\u003C\u002Fli>\n\u003C\u002Ful>\n","Hyper Cache Extended is flexible and easy to configure cache system for WordPress. It's aim is to work on any installation.",400,77054,98,14,"2018-04-11T15:42:00.000Z","4.9.29","2.5","",[20,21,22,23,24],"cache","chaching","performance","speed","super-cache","http:\u002F\u002Fmarto.lazarov.org\u002Fplugins\u002Fhyper-cache-extended","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhyper-cache-extended.1.6.3.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":34,"avg_security_score":27,"avg_patch_time_days":35,"trust_score":36,"computed_at":37},10,1630,30,84,"2026-04-04T05:50:40.195Z",[39,59,82,104,124],{"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":18,"tags":54,"homepage":56,"download_link":57,"security_score":58,"vuln_count":28,"unpatched_count":28,"last_vuln_date":29,"fetched_at":30},"wpbase-cache","WPBase Cache","5.5.6","baseapp","https:\u002F\u002Fprofiles.wordpress.org\u002Fbaseapp\u002F","\u003Cp>Plugin is developed to optimize wordpress deployment on varnish + nginx + php-fpm + php-apc server stack using three type of caches full page cache, db cache and opcode cache. This plugin includes \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fnginx-compatibility\u002F\" rel=\"ugc\">nginx-compatibility\u003C\u002Fa>, \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fdb-cache-reloaded-fix\u002F\" rel=\"ugc\">db-cache-reloaded-fix\u003C\u002Fa> for nginx and database cache. This plguin also support varnish cache management with given default.vcl. We have included sample file for nginx and varnish configurations in utils folder. This plugin will automatically invalidate caches upon certain actions from wordpress admin panel.\u003C\u002Fp>\n\u003Cp>Thanks to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Ivan Kristianto\u003C\u002Fli>\n\u003Cli>Vladimir Kolesnikov\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Visit our blog for more information on deployment of wordpress on varnish, nginx and php-fpm stack at \u003Ca href=\"https:\u002F\u002Fwww.wpoven.com\u002Fblog\u002Fwpbase-cache-plugin-features-and-advantages\u002F\" rel=\"nofollow ugc\">WPOven Blog\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Please note that generally shared hosting don’t have varnish + nginx as server software so this plugin will not work on shared hostings.\u003C\u002Fp>\n","A wordpress plugin for using all caches on varnish, nginx, php-fpm stack with php-apc. This plugin includes db-cache-reloaded-fix for dbcache.",4000,755530,100,3,"2025-01-23T11:43:00.000Z","6.7.5","3.5",[20,21,55,22,23],"db-cache","https:\u002F\u002Fwww.wpoven.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwpbase-cache.zip",92,{"slug":60,"name":61,"version":62,"author":63,"author_profile":64,"description":65,"short_description":66,"active_installs":67,"downloaded":68,"rating":13,"num_ratings":69,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":18,"tags":73,"homepage":77,"download_link":78,"security_score":79,"vuln_count":80,"unpatched_count":28,"last_vuln_date":81,"fetched_at":30},"wp-fastest-cache","WP Fastest Cache – WordPress Cache Plugin","1.4.6","Emre Vona","https:\u002F\u002Fprofiles.wordpress.org\u002Femrevona\u002F","\u003Ch4>Official Website\u003C\u002Fh4>\n\u003Cp>You can find more information on our website (\u003Ca href=\"https:\u002F\u002Fwww.wpfastestcache.com\u002F\" rel=\"nofollow ugc\">wpfastestcache.com\u003C\u002Fa>)\u003C\u002Fp>\n\u003Cp>Welcome to the page of the WP Fastest Cache plugin, a WordPress cache plugin developed to speed up WordPress sites.\u003C\u002Fp>\n\u003Cp>In today’s world where every second counts, optimizing your website’s performance is very important. Meet WP Fastest Cache, your caching plugin that you can use to speed up WordPress websites. \u003C\u002Fp>\n\u003Cp>Optimize the performance of your website with WP Fastest Cache. Improve Google PageSpeed, Core Web Vitals, GTmetrix and Pingdom score with our wp cache plugin.\u003C\u002Fp>\n\u003Cp>In addition, page speed is a ranking factor in Google’s search algorithm. Therefore, using cache plugins helps improve your SEO ranking. Our WordPress optimization plugin not only accelerates your site but also boosts SEO rankings.\u003C\u002Fp>\n\u003Ch4>Features\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Mod_Rewrite which is the fastest method is used in this plugin\u003C\u002Fli>\n\u003Cli>All cache files are deleted when a post or page is published\u003C\u002Fli>\n\u003Cli>Admin can delete all cached files from the options page\u003C\u002Fli>\n\u003Cli>Admin can delete minified css and js files from the options page\u003C\u002Fli>\n\u003Cli>Block cache for specific page or post with Short Code\u003C\u002Fli>\n\u003Cli>Cache Timeout – All cached files are deleted at the determinated time\u003C\u002Fli>\n\u003Cli>Cache Timeout for specific pages\u003C\u002Fli>\n\u003Cli>Enable\u002FDisable cache option for mobile devices\u003C\u002Fli>\n\u003Cli>Enable\u002FDisable cache option for logged-in users\u003C\u002Fli>\n\u003Cli>SSL support\u003C\u002Fli>\n\u003Cli>CDN support – Effortlessly enhance website speed and performance with seamless CDN integration, supporting Bunny CDN, Cloudflare, and various other leading CDN providers. CDN integration modifies the URLs of static resources, enabling these assets to be served from your CDN service provider\u003C\u002Fli>\n\u003Cli>Cloudflare support – Cloudflare integration triggers the clearing of the cache on Cloudflare through API when a cache purge is initiated. As a result, WP Fastest Cache and Cloudflare operate seamlessly in tandem\u003C\u002Fli>\n\u003Cli>Preload Cache – Create the cache of all the site automatically\u003C\u002Fli>\n\u003Cli>Exclude pages and user-agents\u003C\u002Fli>\n\u003Cli>WP-CLI cache clearing\u003C\u002Fli>\n\u003Cli>Proxy Cache – Varnish Cache Integration to clear proxy cached content automatically when the cache created by WP Fastest Cache is cleared\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Performance Optimization\u003C\u002Fh4>\n\u003Cp>WP Fastest Cache is not only a wp cache plugin but also a speed optimization wordpress cache plugin. There are many features such as Minify Html, Minify Css, Enable Gzip Compression, Leverage Browser Caching, Add Expires Headers, Combine CSS, Combine JS, Disable Emoji.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Page Caching – Page caching feature generates and store static HTML files from your dynamic WordPress blog to reduce initial server response time, and improving page load time. Page cache and caching play a critical role in improving website speed and overall web performance. By storing frequently accessed data, effective caching reduces server workload and significantly improves cache performance, allowing pages to be delivered faster to users. This optimization directly lowers load time and enhances page speed, resulting in a smoother user experience and better SEO.\u003C\u002Fli>\n\u003Cli>Minify Html – Using an HTML minifier is an effective way to reduce HTML size and optimize HTML by removing unnecessary spaces, comments, and line breaks. A smaller HTML file helps reduce page size, which directly improves page speed and leads to a faster website experience for users. By focusing on web performance optimization, optimized HTML allows browsers to load and render pages more efficiently, helping to improve website speed, lower bandwidth usage, and deliver better overall performance across all devices\u003C\u002Fli>\n\u003Cli>Minify Css – CSS minify techniques play a crucial role in modern web development by reducing unnecessary characters through a reliable css minifier. With effective css compression, developers can compress CSS files and apply proper css minification to optimize CSS for production environments. This approach helps reduce CSS file size, which directly contributes to improve website speed and overall css performance optimization. As part of a broader page speed optimization strategy, these practices significantly enhance website performance optimization and lead to better website loading performance, especially on mobile and low-bandwidth connections\u003C\u002Fli>\n\u003Cli>Enable Gzip Compression – Reduce the size of files sent from your server to increase the speed to which they are transferred to the browser\u003C\u002Fli>\n\u003Cli>Leverage browser caching – Browser cache plays a critical role in how efficiently a web browser cache stores static resources like images, stylesheets, and scripts, directly impacting page load speed. By allowing returning visitors to load files from their local browser cache instead of downloading them again, websites can significantly reduce server requests and improve website speed. Properly configured browser caching not only creates a faster and smoother user experience but also helps lower bandwidth usage and enhance overall site performance\u003C\u002Fli>\n\u003Cli>Combine CSS – Reduce number of HTTP round-trips by combining multiple CSS resources into one\u003C\u002Fli>\n\u003Cli>Combine JS – Combining JavaScript files is a core technique in javascript optimization and js optimization, especially when the goal is to reduce requests and improve page load speed. By combine js assets or combine javascript files into a single bundle, developers can streamline how scripts are delivered to the browser. Whether you call it js combine or javascript combine, the idea is the same: fewer HTTP requests mean faster performance. Similarly, approaches that merge js or merge javascript—also known as js merge or javascript merge—help eliminate overhead caused by loading multiple separate files. When done correctly, combining and merging scripts leads to cleaner delivery, better caching, and noticeably faster websites\u003C\u002Fli>\n\u003Cli>Disable Emoji – You can remove the emoji inline css and wp-emoji-release.min.js\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Premium Performance Optimization\u003C\u002Fh4>\n\u003Cp>The free version is enough to speed up your site but in the premium version there are extra features such as Mobile Cache, Widget Cache, Minify HTML Plus, Minify CSS Plus, Minify JS, Combine JS Plus, Defer Javascript, Optimize Images, Convert WebP, Database Cleanup, Google Fonts Async, Lazy Load and Delay JS for super fast load times.\u003C\u002Fp>\n\u003Col>\n\u003Cli>Mobile Cache\u003C\u002Fli>\n\u003Cli>Widget Cache\u003C\u002Fli>\n\u003Cli>Minify HTML Plus\u003C\u002Fli>\n\u003Cli>Minify CSS Plus\u003C\u002Fli>\n\u003Cli>Minify Javascript – Minify JS is a core step in web performance optimization because js minify techniques remove unnecessary characters, comments, and whitespace, making files smaller and faster to load. Through proper javascript minification, developers can compress JavaScript assets and significantly reduce transfer size, which directly supports effective js optimization and overall javascript optimization strategies. When combined with caching and code splitting, minified scripts help improve website speed, lower bandwidth usage, and enhance user experience. As a result, page speed optimization becomes easier to achieve, leading to faster render times and better search engine rankings.\u003C\u002Fli>\n\u003Cli>Combine JS Plus\u003C\u002Fli>\n\u003Cli>Defer Javascript – Eliminate render-blocking JavaScript resources. Consider delivering critical JS inline and deferring all non-critical JS\u003C\u002Fli>\n\u003Cli>Optimize Images – Optimized images load faster and consume less cellular data. Looking for an easy image compressor? Our tool lets you compress images instantly, including Compress JPEG and Compress PNG options. Enjoy fast image compression to reduce image size without losing quality. Perfect for quick image optimization with a smart image optimizer designed for all your needs.\u003C\u002Fli>\n\u003Cli>Convert WebP – Serve images in next-gen formats. Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. A fast and reliable WebP converter helps you convert to WebP in seconds. Whether you need a WebP convert tool, a JPG to WEBP Converter, PNG to WEBP Converter, or a simple image to WebP option, you can easily optimize your images. Quickly handle JPG to WEBP, PNG to WEBP, jpg convert to webp, and png convert to webp tasks to reduce file size and improve web performance.\u003C\u002Fli>\n\u003Cli>Database Cleanup – To keep your system running smoothly, it’s important to clean database structures regularly and ensure you clean DB records that are no longer needed. A database cleaner is essential for effective database cleaning and long-term database optimization. By removing unused entries and organizing data efficiently, you can significantly improve database performance and speed up database operations. Modern db cleaner tools automate the entire db cleaning process, helping developers maintain fast, reliable, and scalable systems. The Database Cleanup feature clears out all of the garbage datas such as post revisions, trashed posts & pages, comments from trash & spam, trackbacks and pingbacks, transient options, orphaned post meta, comment meta, user meta, term meta, and term relationship etc.\u003C\u002Fli>\n\u003Cli>Google Fonts Async\u003C\u002Fli>\n\u003Cli>Lazy Load – Lazy loading technique improve page speed and overall website loading time by loading content only when it is needed. Using lazy load images, lazy loading images, lazy load videos, and lazy load iframe helps reduce initial load size, enhances web performance, and delivers a smoother user experience. When implemented correctly, these methods make it easier to optimize website performance, lower bandwidth usage, and ensure faster, more efficient page delivery for both users and search engines.\u003C\u002Fli>\n\u003Cli>Delay JS – The Delay JavaScript feature helps reduce the ‘Reduce unused JavaScript’ warning in the Google PageSpeed Insights tool\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch4>Information\u003C\u002Fh4>\n\u003Cp>It is very inconvenient to use multiple caching plugins at the same time. That’s why you need to disable plugins such as LiteSpeed Cache, WP-Optimize, W3 Total Cache, WP Super Cache, SiteGround Optimizer, Breeze while using WP Fastest Cache.\u003C\u002Fp>\n\u003Cp>WP Fastest Cache is compatible with most popular plugins such as Contact Form 7, Yoast SEO, Elementor Website Builder, Classic Editor, Akismet Spam Protection, WooCommerce, Contact Form by WPForms, Really Simple SSL, All-in-One WP Migration, Yoast Duplicate Post, Wordfence Security – Firewall & Malware Scan, WordPress Importer, UpdraftPlus WordPress Backup Plugin, MonsterInsights, All in One SEO, WP Mail SMTP by WPForms.\u003C\u002Fp>\n\u003Ch4>Supported Languages\u003C\u002Fh4>\n\u003Cp>Although there are over 7000 languages spoken in the world today, we feel very lucky to support 30 languages for now.\u003C\u002Fp>\n\u003Cp>However, localizing or adapting a plugin to another language or culture is time consuming and a demanding task. That’s where the amazing Translation Contributors team of WordPress comes into play. These selfless people spent their precious time without expecting anything in return so that other people can use the add-ons more easily. We sincerely thank all of them.\u003C\u002Fp>\n\u003Cp>Chinese Simplified (China), Chinese Traditional (Taiwan), Czech, Dutch (Belgium), Dutch (Netherlands), English (South Africa), English (UK), Finnish, French (France), Galician, German (Germany), Hungarian, Indonesian, Italian, Japanese, Korean (Korea), Persian, Russian, Slovak (Slovakia), Slovenian, Spanish (Argentina), Spanish (Chile), Spanish (Colombia), Spanish (Ecuador), Spanish (Mexico), Spanish (Spain), Spanish (Venezuela), Swedish, Turkish, Ukrainian\u003C\u002Fp>\n","The simplest and fastest WP Cache system",1000000,63353783,4207,"2026-02-10T14:26:00.000Z","6.9.4","5.3",[20,74,75,76,22],"core-web-vitals","optimize","pagespeed","http:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-fastest-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-fastest-cache.1.4.6.zip",76,35,"2025-11-26 21:34:28",{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":67,"downloaded":90,"rating":91,"num_ratings":92,"last_updated":93,"tested_up_to":71,"requires_at_least":94,"requires_php":95,"tags":96,"homepage":99,"download_link":100,"security_score":101,"vuln_count":102,"unpatched_count":28,"last_vuln_date":103,"fetched_at":30},"wp-super-cache","WP Super Cache","3.0.3","Automattic","https:\u002F\u002Fprofiles.wordpress.org\u002Fautomattic\u002F","\u003Cp>This plugin generates static html files from your dynamic WordPress blog.  After a html file is generated your webserver will serve that file instead of processing the comparatively heavier and more expensive WordPress PHP scripts.\u003C\u002Fp>\n\u003Cp>The static html files will be served to the vast majority of your users:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Users who are not logged in.\u003C\u002Fli>\n\u003Cli>Users who have not left a comment on your blog.\u003C\u002Fli>\n\u003Cli>Or users who have not viewed a password protected post.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>99% of your visitors will be served static html files. One cached file can be served thousands of times. Other visitors will be served custom cached files tailored to their visit. If they are logged in, or have left comments those details will be displayed and cached for them.\u003C\u002Fp>\n\u003Cp>The plugin serves cached files in 3 ways (ranked by speed):\u003C\u002Fp>\n\u003Col>\n\u003Cli>Expert. The fastest method is by using Apache mod_rewrite (or whatever similar module your web server supports) to serve “supercached” static html files. This completely bypasses PHP and is extremely quick. If your server is hit by a deluge of traffic it is more likely to cope as the requests are “lighter”. This does require the Apache mod_rewrite module (which is probably installed if you have custom permalinks) and a modification of your .htaccess file which is risky and may take down your site if modified incorrectly.\u003C\u002Fli>\n\u003Cli>Simple. Supercached static files can be served by PHP and this is the recommended way of using the plugin. The plugin will serve a “supercached” file if it exists and it’s almost as fast as the mod_rewrite method. It’s easier to configure as the .htaccess file doesn’t need to be changed. You still need a custom permalink. You can keep portions of your page dynamic in this caching mode.\u003C\u002Fli>\n\u003Cli>WP-Cache caching. This is mainly used to cache pages for known users, URLs with parameters and feeds. Known users are logged in users, visitors who leave comments or those who should be shown custom per-user data. It’s the most flexible caching method and slightly slower. WP-Cache caching will also cache visits by unknown users if supercaching is disabled. You can have dynamic parts to your page in this mode too. This mode is always enabled but you can disable caching for known users, URLs with parameters, or feeds separately. Set the constant “DISABLE_SUPERCACHE” to 1 in your wp-config.php if you want to only use WP-Cache caching.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>If you’re not comfortable with editing PHP files then use simple mode. It’s easy to set up and very fast.\u003C\u002Fp>\n\u003Ch3>Recommended Settings\u003C\u002Fh3>\n\u003Col>\n\u003Cli>Simple caching.\u003C\u002Fli>\n\u003Cli>Compress pages.\u003C\u002Fli>\n\u003Cli>Don’t cache pages for known users.\u003C\u002Fli>\n\u003Cli>Cache rebuild.\u003C\u002Fli>\n\u003Cli>CDN support.\u003C\u002Fli>\n\u003Cli>Extra homepage checks.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Garbage collection is the act of cleaning up cache files that are out of date and stale. There’s no correct value for the expiry time but a good starting point is 1800 seconds.\u003C\u002Fp>\n\u003Cp>Consider deleting the contents of the “Rejected User Agents” text box and allow search engines to cache files for you.\u003C\u002Fp>\n\u003Cp>Preload as many posts as you can and enable “Preload Mode”. Garbage collection of old cached files will be disabled. If you don’t care about sidebar widgets updating often set the preload interval to 2880 minutes (2 days) so all your posts aren’t recached very often. When the preload occurs the cache files for the post being refreshed is deleted and then regenerated. Afterwards a garbage collection of all old files is performed to clean out stale cache files.\u003Cbr \u002F>\nEven with preload mode enabled cached files will still be deleted when posts are modified or comments made.\u003C\u002Fp>\n\u003Ch3>Development\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Active development of this plugin is handled \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\" rel=\"nofollow ugc\">on GitHub\u003C\u002Fa>.\u003C\u002Fli>\n\u003Cli>Translation of the plugin into different languages is on the \u003Ca href=\"https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fwp-super-cache\" rel=\"nofollow ugc\">translation page\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Documentation\u003C\u002Fh3>\n\u003Cp>If you need more information than the following, you can have a look at \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fwiki\" rel=\"nofollow ugc\">the wiki\u003C\u002Fa> or the \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fwp-super-cache-developers\u002F\" rel=\"nofollow ugc\">Developer documentation\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch4>Preloading\u003C\u002Fh4>\n\u003Cp>You can generate cached files for the posts, categories and tags of your site by preloading. Preloading will visit each page of your site generating a cached page as it goes along, just like any other visitor to the site. Due to the sequential nature of this function, it can take some time to preload a complete site if there are many posts.\u003Cbr \u002F>\nTo make preloading more effective it can be useful to disable garbage collection so that older cache files are not deleted. This is done by enabling “Preload Mode” in the settings. Be aware however, that pages will go out of date eventually but that updates by submitting comments or editing posts will clear portions of the cache.\u003C\u002Fp>\n\u003Ch4>Garbage Collection\u003C\u002Fh4>\n\u003Cp>Your cache directory fills up over time, which takes up space on your server. If space is limited or billed by capacity, or if you worry that the cached pages of your site will go stale then garbage collection has to be done. Garbage collection happens on a regular basis and deletes old files in the cache directory. On the advanced settings page you can specify:\u003Cbr \u002F>\n1. Cache timeout. How long cache files are considered fresh for. After this time they are stale and can be deleted.\u003Cbr \u002F>\n2. Scheduler. Setup how often garbage collection should be done.\u003Cbr \u002F>\n3. Notification emails. You can be informed on garbage collection job progress.\u003Cbr \u002F>\nThere’s no right or wrong settings for garbage collection. It depends on your own site.\u003Cbr \u002F>\nIf your site gets regular updates, or comments then set the timeout to 1800 seconds, and set the timer to 600 seconds.\u003Cbr \u002F>\nIf your site is mostly static you can disable garbage collection by entering 0 as the timeout, or use a really large timeout value.\u003C\u002Fp>\n\u003Cp>The cache directory, usually wp-content\u002Fcache\u002F is only for temporary files. Do not ever put important files or symlinks to important files or directories in that directory. They will be deleted if the plugin has write access to them.\u003C\u002Fp>\n\u003Ch4>CDN\u003C\u002Fh4>\n\u003Cp>A Content Delivery Network (CDN) is usually a network of computers situated around the world that will serve the content of your website faster by using servers close to you. Static files like images, Javascript and CSS files can be served through these networks to speed up how fast your site loads. You can also create a “poor man’s CDN” by using a sub domain of your domain to serve static files too.\u003C\u002Fp>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fossdl-cdn-off-linker\u002F\" rel=\"ugc\">OSSDL CDN off-linker\u003C\u002Fa> has been integrated into WP Super Cache to provide basic CDN support. It works by rewriting the URLs of files (excluding .php files) in wp-content and wp-includes on your server so they point at a different hostname. Many CDNs support \u003Ca href=\"https:\u002F\u002Fwww.google.com\u002Fsearch?hl=en&q=%22origin+pull%22\" rel=\"nofollow ugc\">origin pull\u003C\u002Fa>. This means the CDN will download the file automatically from your server when it’s first requested, and will continue to serve it for a configurable length of time before downloading it again from your server.\u003C\u002Fp>\n\u003Cp>Configure this on the “CDN” tab of the plugin settings page. This is an advanced technique and requires a basic understanding of how your webserver or CDNs work. Please be sure to clear the file cache after you configure the CDN.\u003C\u002Fp>\n\u003Ch4>REST API\u003C\u002Fh4>\n\u003Cp>There are now REST API endpoints for accessing the settings of this plugin. You’ll need to be authenticated as an admin user with permission to view the settings page to use it. This has not been documented yet but you can find all the code that deals with this in the “rest” directory.\u003C\u002Fp>\n\u003Ch4>Custom Caching\u003C\u002Fh4>\n\u003Cp>It is now possible to hook into the caching process using the add_cacheaction() function.\u003C\u002Fp>\n\u003Cp>Three hooks are available:\u003C\u002Fp>\n\u003Col>\n\u003Cli>‘wp_cache_get_cookies_values’ – modify the key used by WP Cache.\u003C\u002Fli>\n\u003Cli>‘add_cacheaction’ – runs in phase2. Allows a plugin to add WordPress hooks.\u003C\u002Fli>\n\u003Cli>‘cache_admin_page’ – runs in the admin page. Use it to modify that page, perhaps by adding new configuration options.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>There is one regular WordPress filter too. Use the “do_createsupercache” filter\u003Cbr \u002F>\nto customize the checks made before caching. The filter accepts one parameter.\u003Cbr \u002F>\nThe output of WP-Cache’s wp_cache_get_cookies_values() function.\u003C\u002Fp>\n\u003Cp>WP Super Cache has its own plugin system. This code is loaded when WP Super Cache loads and can be used to change how caching is done. This is before most of WordPress loads so some functionality will not be available. Plugins can be located anywhere that PHP can load them. Add your own plugin either:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>by putting your plugin in the wp-content\u002Fplugins\u002Fwp-super-cache-plugins directory, or\u003C\u002Fli>\n\u003Cli>by calling wpsc_add_plugin( $name ) where $name is the full filename and path to the plugin. You only need to call that function once to add it. Use wpsc_delete_plugin( $name ) to remove it from the list of loaded plugins.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>The cookies WP Super Cache uses to identify “known users” can be modified now by adding the names of those cookies to a list in the plugin configuration. Use wpsc_add_cookie( $name ) to add a new cookie, and wpsc_delete_cookie( $name ) to remove it. The cookie names also modify the mod_rewrite rules used by the plugin but I recommend using Simple mode caching to avoid complications with updating the .htaccess file.\u003Cbr \u002F>\nThe cookie name and value are used to differenciate users so you can have one cookie, but different values for each type of user on your site for example. They’ll be served different cache files.\u003C\u002Fp>\n\u003Cp>See \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FAutomattic\u002Fwp-super-cache\u002Fblob\u002F4cda5c0f2218e40e118232b5bf22d227fb3206b7\u002Fplugins\u002Fsearchengine.php\" rel=\"nofollow ugc\">plugins\u002Fsearchengine.php\u003C\u002Fa> as an example I use for my \u003Ca href=\"https:\u002F\u002Fodd.blog\u002Fno-adverts-for-friends\u002F\" rel=\"nofollow ugc\">No Adverts for Friends\u003C\u002Fa> plugin.\u003C\u002Fp>\n\u003Ch3>Troubleshooting\u003C\u002Fh3>\n\u003Cp>If things don’t work when you installed the plugin here are a few things to check:\u003C\u002Fp>\n\u003Col>\n\u003Cli>Is wp-content writable by the web server?\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fwp-cache-config.php ? If not, copy the file wp-super-cache\u002Fwp-cache-config-sample.php to wp-content\u002Fwp-cache-config.php and make sure WPCACHEHOME points at the right place.\u003C\u002Fli>\n\u003Cli>Is there a wp-content\u002Fadvanced-cache.php ? If not, then you must copy wp-super-cache\u002Fadvanced-cache.php into wp-content\u002F. You must edit the file and change the path so it points at the wp-super-cache folder.\u003C\u002Fli>\n\u003Cli>If pages are not cached at all, remove wp-content\u002Fadvanced-cache.php and recreate it, following the advice above.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Make sure the following line is in wp-config.php and it is ABOVE the “require_once(ABSPATH.’wp-settings.php’);” line:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>define( 'WP_CACHE', true );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>Try the Settings->WP Super Cache page again and enable cache.\u003C\u002Fli>\n\u003Cli>Look in wp-content\u002Fcache\u002Fsupercache\u002F. Are there directories and files there?\u003C\u002Fli>\n\u003Cli>Anything in your php error_log?\u003C\u002Fli>\n\u003Cli>If your browser keeps asking you to save the file after the super cache is installed you must disable Super Cache compression. Go to the Settings->WP Super Cache page and disable it there.\u003C\u002Fli>\n\u003Cli>The plugin does not work very well when PHP’s safe mode is active. This must be disabled by your administrator.\u003C\u002Fli>\n\u003Cli>If pages are randomly super cached and sometimes not, your blog can probably be viewed with and without the “www” prefix on the URL. You should choose one way and install the \u003Ca href=\"http:\u002F\u002Ftxfx.net\u002Fcode\u002Fwordpress\u002Fenforce-www-preference\u002F\" rel=\"nofollow ugc\">Enforce www preference\u003C\u002Fa> plugin if you are using an old WordPress install. The latest versions redirect themselves (you should always be running the latest version of WordPress anyway!)\u003C\u002Fli>\n\u003Cli>Private Server users at Dreamhost should edit wp-content\u002Fwp-cache-config.php and set the cache dir to “\u002Ftmp\u002F” if they are getting errors about increasing CPU usage. See this \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fsupport\u002Ftopic\u002F145895?replies=42\" rel=\"ugc\">discussion\u003C\u002Fa> for more.\u003C\u002Fli>\n\u003Cli>File locking errors such as “failed to acquire key 0x152b: Permission denied in…” or “Page not cached by WP Super Cache. Could not get mutex lock.” are a sign that you may have to use file locking. Edit wp-content\u002Fwp-cache-config.php and uncomment “$use_flock = true” or set $sem_id to a different value. You can also disable file locking from the Admin screen as a last resort.\u003C\u002Fli>\n\u003Cli>Make sure cache\u002Fwp_cache_mutex.lock is writable by the web server if using coarse file locking.\u003C\u002Fli>\n\u003Cli>The cache folder cannot be put on an NFS or Samba or NAS share. It has to be on a local disk. File locking and deleting expired files will not work properly unless the cache folder is on the local machine.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Garbage collection of old cache files won’t work if WordPress can’t find wp-cron.php. If your hostname resolves to 127.0.0.1 it could be preventing the garbage collection from working. Check your access_logs for wp-cron.php entries. Do they return a 404 (file not found) or 200 code? If it’s 404 or you don’t see wp-cron.php anywhere WordPress may be looking for that script in the wrong place. You should speak to your server administator to correct this or edit \u002Fetc\u002Fhosts on Unix servers and remove the following line. Your hostname must resolve to the external IP address other servers on the network\u002FInternet use. See http:\u002F\u002Fyoast.com\u002Fwp-cron-issues\u002F for more. A line like “127.0.0.1 localhost localhost.localdomain” is ok.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>127.0.0.1 example.com\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>If old pages are being served to your visitors via the supercache, you may be missing Apache modules (or their equivalents if you don’t use Apache). 3 modules are required: mod_mime, mod_headers and mod_expires. The last two are especially important for making sure browsers load new versions of existing pages on your site.\u003C\u002Fli>\n\u003Cli>The error message, “WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content\u002Fadvanced-cache.php must be fixed!” appears at the end of every page. Open the file wp-content\u002Fadvanced-cache.php in your favourite editor. Is the path to wp-cache-phase1.php correct? This file will normally be in wp-content\u002Fplugins\u002Fwp-super-cache\u002F. If it is not correct the caching engine will not load.\u003C\u002Fli>\n\u003Cli>Caching doesn’t work. The timestamp on my blog keeps changing when I reload. Check that the path in your .htaccess rules matches where the supercache directory is. You may have to hardcode it. Try disabling supercache mode.\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If supercache cache files are generated but not served, check the permissions on all your wp-content\u002Fcache\u002Fsupercache folders (and each of wp-content cache and supercache folders) and wp-content\u002Fcache\u002F.htaccess. If your PHP runs as a different user to Apache and permissions are strict Apache may not be able to read the PHP generated cache files. To fix you must add the following line to your wp-config.php (Add it above the WP_CACHE define.) Then clear your cache.\u003C\u002Fp>\n\u003Cpre>\u003Ccode>umask( 0022 );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>If you see garbage in your browser after enabling compression in the plugin, compression may already be enabled in your web server. In Apache you must disable mod_deflate, or in PHP zlib compression may be enabled. You can disable that in three ways. If you have root access, edit your php.ini and find the zlib.output_compression setting and make sure it’s “Off” or add this line to your .htaccess:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>php_flag zlib.output_compression off\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>If that doesn’t work, add this line to your wp-config.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>ini_set('zlib.output_compression', 0);\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003C\u002Fli>\n\u003Cli>The “white screen of death” or a blank page  when you visit your site is almost always caused by a PHP error but \u003Ca href=\"http:\u002F\u002Fwww.johnberns.com\u002F2010\u002F03\u002F19\u002Fwp-super-cache-blank-page-problem-fixed\u002F\" rel=\"nofollow ugc\">it may also be caused by APC\u003C\u002Fa>. Disable that PHP extension if you have trouble and replace with eAccelerator or Xcache.\u003C\u002Fli>\n\u003Cli>After uninstalling, your permalinks may break if you remove the WordPress mod_rewrite rules too. Regenerate those rules by visiting the Settings->Permalink page and saving that form again.\u003C\u002Fli>\n\u003Cli>If your blog refuses to load make sure your wp-config.php is correct. Are you missing an opening or closing PHP tag?\u003C\u002Fli>\n\u003Cli>Your front  …\u003C\u002Fli>\n\u003C\u002Fol>\n","A very fast caching engine for WordPress that produces static html files.",62208732,86,1341,"2025-11-11T16:21:00.000Z","6.7","7.2",[20,97,22,98,83],"caching","wp-cache","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fwp-super-cache\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-super-cache.3.0.3.zip",95,12,"2022-10-03 00:00:00",{"slug":105,"name":106,"version":107,"author":86,"author_profile":87,"description":108,"short_description":109,"active_installs":110,"downloaded":111,"rating":112,"num_ratings":113,"last_updated":114,"tested_up_to":71,"requires_at_least":115,"requires_php":95,"tags":116,"homepage":119,"download_link":120,"security_score":121,"vuln_count":122,"unpatched_count":28,"last_vuln_date":123,"fetched_at":30},"jetpack-boost","Jetpack Boost – Website Speed, Performance and Critical CSS","4.5.7","\u003Cp>Speed up your WordPress site by optimizing page performance with Jetpack Boost. Easily activate one-click optimizations to boost your Core Web Vitals.\u003C\u002Fp>\n\u003Cp>Did you know that a faster website:-\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Ranks higher on Google.\u003C\u002Fli>\n\u003Cli>Improves bounce rate (people stay on your site for longer).\u003C\u002Fli>\n\u003Cli>Increases your conversion rate.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Increase your website performance and speed up your website with one-click optimizations that supercharge your WordPress site’s performance and improve core web vitals scores for better search engine listings.\u003C\u002Fp>\n\u003Cp>Improving Core Web Vitals helps you rank higher on Google. A faster website also improves your SEO, helps you reduce your bounce rate and increase your ecommerce conversion rate.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Largest Contentful Paint (LCP): Measures loading performance. Improve your LCP and improve your website loading speed.\u003C\u002Fli>\n\u003Cli>First Input Delay (FID): Measures interactivity. To improve user experience pages should have a low FID.\u003C\u002Fli>\n\u003Cli>Cumulative Layout Shift (CLS): Measures visual stability. Lowering your CLS helps improve your user experience.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Performance Modules\u003C\u002Fh3>\n\u003Cp>Optimize your website with the same techniques used on the world’s most successful websites.\u003C\u002Fp>\n\u003Cp>Each technique that is used to increase website performance is packaged up as a module that you can activate and try out.\u003C\u002Fp>\n\u003Cp>Currently, the plugin has 6 performance modules available:\u003C\u002Fp>\n\u003Col>\n\u003Cli>\n\u003Cp>\u003Cem>Optimize CSS Loading\u003C\u002Fem> generates Critical CSS for your homepage, posts and pages. This can allow your content to show up on the screen much faster, particularly for viewers using mobile devices.\u003C\u002Fp>\n\u003Cp>Read more about critical CSS generation at \u003Ca href=\"https:\u002F\u002Fjetpack.com\u002Fredirect\u002F?source=jetpack-boost-critical-css\" rel=\"nofollow ugc\">web.dev\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Page Cache\u003C\u002Fem> speeds up your site by saving pages as static files. These files are quickly served to visitors, reducing load times and enhancing user experience.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Defer Non-Essential JavaScript\u003C\u002Fem> moves some tasks to after the page loads, so that important visual information can be seen sooner and your website loads quicker.\u003C\u002Fp>\n\u003Cp>Read more about deferring JavaScript at \u003Ca href=\"https:\u002F\u002Fjetpack.com\u002Fredirect\u002F?source=jetpack-boost-defer-js\" rel=\"nofollow ugc\">web.dev\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Image Guide\u003C\u002Fem> is a must-have feature for anyone who wants to optimize the images on their website. With this guide, you can ensure that the images on your site are the right size and dimensions, which is critical for improving user experience, page speed, and site ranking. Following the tips and best practices outlined in the guide, you can reduce image file sizes and speed up your site. Check out our \u003Ca href=\"https:\u002F\u002Fjetpack.com\u002Fsupport\u002Fjetpack-boost\u002Fimage-performance-guide\u002F\" rel=\"nofollow ugc\">support page\u003C\u002Fa> to learn more about this feature and how it can help you achieve a faster and smoother website experience for your users.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Image CDN\u003C\u002Fem> allows your site to serve automatically-resized images in modern web formats directly from Jetpack’s worldwide Content Delivery Network.\u003C\u002Fp>\n\u003Cp>Read more about Image CDNs at \u003Ca href=\"https:\u002F\u002Fweb.dev\u002Fimage-cdns\u002F\" rel=\"nofollow ugc\">web.dev\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Cem>Concatenate and Minify CSS and JS\u003C\u002Fem> combines and shrinks your JavaScript and CSS resources to reduce the number and size of requests to your server, ensuring your content loads faster.\u003C\u002Fp>\n\u003Cp>Read more about minifying files at \u003Ca href=\"https:\u002F\u002Fweb.dev\u002Fminify-css\u002F\" rel=\"nofollow ugc\">web.dev\u003C\u002Fa>\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>Don’t want to have to manually generate your critical CSS each time you update your site? Let us do the heavy lifting for you with automated critical CSS – each time you update your site we will automatically regenerate your critical CSS and update your performance scores. Upgrading also gives you dedicated email support access.\u003C\u002Fp>\n\u003Ch3>With 💚 by Jetpack\u003C\u002Fh3>\n\u003Cp>This is just the start!\u003C\u002Fp>\n\u003Cp>We are working hard to bring more features and improvements to Jetpack Boost. Let us know your thoughts and ideas!\u003C\u002Fp>\n\u003Cp>We’d also like to give a special THANK YOU to the XWP team who provided help with initial research and scoping of the plugin and were engaged with our team throughout the project.\u003C\u002Fp>\n","Speed up your WordPress site with one-click optimizations like Page Cache, Critical CSS, and Image CDN to improve Core Web Vitals.",200000,12459727,94,598,"2026-02-04T16:40:00.000Z","6.8",[20,117,22,23,118],"critical-css","web-vitals","https:\u002F\u002Fjetpack.com\u002Fboost","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fjetpack-boost.4.5.7.zip",99,2,"2024-10-17 00:00:00",{"slug":125,"name":126,"version":127,"author":128,"author_profile":129,"description":130,"short_description":131,"active_installs":132,"downloaded":133,"rating":134,"num_ratings":33,"last_updated":135,"tested_up_to":71,"requires_at_least":136,"requires_php":137,"tags":138,"homepage":140,"download_link":141,"security_score":101,"vuln_count":142,"unpatched_count":28,"last_vuln_date":143,"fetched_at":30},"aruba-hispeed-cache","Aruba HiSpeed Cache","3.0.10","Aruba.it Dev","https:\u002F\u002Fprofiles.wordpress.org\u002Farubadev\u002F","\u003Cp>\u003Cstrong>Aruba HiSpeed Cache\u003C\u002Fstrong> is a plugin that interfaces directly with the \u003Cstrong>HiSpeed Cache\u003C\u002Fstrong> service for an \u003Ca href=\"https:\u002F\u002Fwww.aruba.it\u002Fen\u002F\" rel=\"nofollow ugc\">Aruba\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fhosting.aruba.it\u002Fen\u002F\" rel=\"nofollow ugc\">hosting platform\u003C\u002Fa> and automates its management in the WordPress dashboard, without having to access the website’s control panel.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>The plugin can only be used if your WordPress website is hosted on an \u003Ca href=\"https:\u002F\u002Fwww.aruba.it\u002Fen\u002F\" rel=\"nofollow ugc\">Aruba\u003C\u002Fa> \u003Ca href=\"https:\u002F\u002Fhosting.aruba.it\u002Fen\u002F\" rel=\"nofollow ugc\">hosting platform\u003C\u002Fa>.\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The HiSpeed Cache service significantly reduces the TTFB (first Byte transfer time) and webpage loading times.\u003C\u002Fp>\n\u003Cp>When the service is active, using the plugin allows you to automatically (and\u002For manually) clear the cache whenever a page or post is modified, without needing to access the website’s control panel by clicking the dedicated link.\u003C\u002Fp>\n\u003Cp>Thanks to AI, HiSpeed Cache analyzes traffic on your pages to automatically preload the most requested content, improving your users’ browsing experience. In addition, it stores dynamic content in the server memory after the first load, making it available for subsequent requests in a significantly shorter time, thus making website navigation much faster. The plugin simply clears the cache whenever a page, post, or custom content type is modified.\u003C\u002Fp>\n\u003Cp>For more details and to find out whether the HiSpeed Cache service is active on your website \u003Ca href=\"https:\u002F\u002Fguide.aruba.it\u002Fen\u002Fhosting-e-domini\u002Fhosting\u002Futilizzo-wordpress\u002Fvelocita-prestazioni-sito-wordpress\u002Fwordpress-utilizzare-aruba-hispeed-cache\" rel=\"nofollow ugc\">please refer to our guide\u003C\u002Fa>.\u003C\u002Fp>\n","Aruba HiSpeed Cache interfaces directly with an Aruba hosting platform's HiSpeed Cache service and automates its management.",100000,999575,60,"2026-03-13T16:08:00.000Z","5.4","5.6",[139,20,75,76,22],"aruba","https:\u002F\u002Fhosting.aruba.it\u002Fwordpress.aspx","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Faruba-hispeed-cache.3.0.10.zip",6,"2026-02-18 14:59:09",{"attackSurface":145,"codeSignals":192,"taintFlows":250,"riskAssessment":296,"analyzedAt":314},{"hooks":146,"ajaxHandlers":183,"restRoutes":184,"shortcodes":185,"cronEvents":186,"entryPointCount":28,"unprotectedCount":28},[147,152,156,161,165,169,173,176,179],{"type":148,"name":149,"callback":149,"file":150,"line":151},"action","hyper_clean","plugin.php",80,{"type":148,"name":153,"callback":154,"file":150,"line":155},"admin_notices","hyper_admin_notices",134,{"type":157,"name":158,"callback":159,"file":150,"line":160},"filter","plugin_action_links_hyper-cache-extended\u002Fplugin.php","hyper_plugin_action_links",169,{"type":148,"name":162,"callback":163,"file":150,"line":164},"admin_menu","hyper_admin_menu",176,{"type":148,"name":166,"callback":167,"priority":28,"file":150,"line":168},"switch_theme","hyper_cache_invalidate",311,{"type":148,"name":170,"callback":171,"priority":28,"file":150,"line":172},"edit_post","hyper_cache_invalidate_post",312,{"type":148,"name":174,"callback":171,"priority":28,"file":150,"line":175},"publish_post",313,{"type":148,"name":177,"callback":171,"priority":28,"file":150,"line":178},"delete_post",314,{"type":157,"name":180,"callback":181,"priority":33,"file":150,"line":182},"redirect_canonical","hyper_redirect_canonical",321,[],[],[],[187,190],{"hook":149,"callback":149,"file":188,"line":189},"options.php",44,{"hook":149,"callback":149,"file":150,"line":191},73,{"dangerousFunctions":193,"sqlUsage":199,"outputEscaping":201,"fileOperations":248,"externalRequests":28,"nonceChecks":28,"capabilityChecks":28,"bundledLibraries":249},[194],{"fn":195,"file":196,"line":197,"context":198},"unserialize","cache.php",147,"$hyper_data = @ unserialize(file_get_contents($hc_file));",{"prepared":28,"raw":28,"locations":200},[],{"escaped":28,"rawEcho":202,"locations":203},23,[204,207,209,211,213,215,217,219,221,222,223,225,227,229,231,233,235,237,239,241,243,245,247],{"file":196,"line":205,"context":206},216,"raw output",{"file":196,"line":208,"context":206},225,{"file":196,"line":210,"context":206},232,{"file":188,"line":212,"context":206},96,{"file":188,"line":214,"context":206},118,{"file":188,"line":216,"context":206},130,{"file":188,"line":218,"context":206},136,{"file":188,"line":220,"context":206},149,{"file":188,"line":220,"context":206},{"file":188,"line":220,"context":206},{"file":188,"line":224,"context":206},164,{"file":188,"line":226,"context":206},208,{"file":188,"line":228,"context":206},291,{"file":188,"line":230,"context":206},293,{"file":188,"line":232,"context":206},449,{"file":188,"line":234,"context":206},451,{"file":188,"line":236,"context":206},470,{"file":188,"line":238,"context":206},482,{"file":188,"line":240,"context":206},484,{"file":188,"line":242,"context":206},499,{"file":188,"line":244,"context":206},501,{"file":188,"line":246,"context":206},515,{"file":150,"line":224,"context":206},28,[],[251,269],{"entryPoint":252,"graph":253,"unsanitizedCount":33,"severity":268},"\u003Coptions> (options.php:0)",{"nodes":254,"edges":265},[255,260],{"id":256,"type":257,"label":258,"file":188,"line":259},"n0","source","$_POST (x10)",55,{"id":261,"type":262,"label":263,"file":188,"line":214,"wp_function":264},"n1","sink","echo() [XSS]","echo",[266],{"from":256,"to":261,"sanitized":267},false,"low",{"entryPoint":270,"graph":271,"unsanitizedCount":50,"severity":295},"\u003Ccache> (cache.php:0)",{"nodes":272,"edges":291},[273,276,278,280,284,286],{"id":256,"type":257,"label":274,"file":196,"line":275},"$_SERVER",117,{"id":261,"type":262,"label":277,"file":196,"line":197,"wp_function":195},"unserialize() [Object Injection]",{"id":279,"type":257,"label":274,"file":196,"line":275},"n2",{"id":281,"type":262,"label":282,"file":196,"line":197,"wp_function":283},"n3","file_get_contents() [SSRF\u002FLFI]","file_get_contents",{"id":285,"type":257,"label":274,"file":196,"line":275},"n4",{"id":287,"type":262,"label":288,"file":196,"line":289,"wp_function":290},"n5","fopen() [File Access]",363,"fopen",[292,293,294],{"from":256,"to":261,"sanitized":267},{"from":279,"to":281,"sanitized":267},{"from":285,"to":287,"sanitized":267},"high",{"summary":297,"deductions":298},"Hyper Cache Extended v1.6.3 presents a mixed security posture. On the positive side, the plugin demonstrates good practices by having no known CVEs, a clean vulnerability history, and utilizing prepared statements for all SQL queries. The limited attack surface with no exposed AJAX handlers, REST API routes, or shortcodes is also a strength. However, significant concerns arise from the static analysis. The presence of the `unserialize` function, combined with two identified flows with unsanitized paths in the taint analysis (one high severity), points to a potential for remote code execution or other critical vulnerabilities if user-controlled data is passed to `unserialize`. Furthermore, the complete lack of output escaping for all 23 identified outputs is a major weakness, exposing the plugin to Cross-Site Scripting (XSS) vulnerabilities. The absence of nonce and capability checks on the identified cron events also indicates potential for privilege escalation or unauthorized actions if these events are susceptible to manipulation.",[299,301,304,307,310,312],{"reason":300,"points":102},"High severity taint flow with unsanitized path",{"reason":302,"points":303},"All outputs unescaped (XSS risk)",15,{"reason":305,"points":306},"Dangerous function: unserialize",8,{"reason":308,"points":309},"Flows with unsanitized paths detected",5,{"reason":311,"points":309},"No nonce checks on cron events",{"reason":313,"points":309},"No capability checks on cron events","2026-03-16T19:48:58.392Z",{"wat":316,"direct":325},{"assetPaths":317,"generatorPatterns":320,"scriptPaths":321,"versionParams":322},[318,319],"\u002Fwp-content\u002Fplugins\u002Fhyper-cache-extended\u002Fhyper-cache-extended.css","\u002Fwp-content\u002Fplugins\u002Fhyper-cache-extended\u002Fhyper-cache-extended.js",[],[319],[323,324],"hyper-cache-extended\u002Fhyper-cache-extended.css?ver=","hyper-cache-extended\u002Fhyper-cache-extended.js?ver=",{"cssClasses":326,"htmlComments":327,"htmlAttributes":330,"restEndpoints":335,"jsGlobals":336,"shortcodeOutput":338},[],[328,329],"\u003C!-- Hyper Cache Extended -->","\u003C!-- Hyper Cache Extended Stats -->",[331,332,333,334],"data-hyper-cache-type","data-hyper-cache-id","data-hyper-cache-time","data-hyper-cache-hash",[],[337],"hyper_cache_status",[]]