[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fA6kg_-bXJkepgdNrd6cyl9lxNkgd_9Gylz8zQXEvhPE":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":15,"tags":18,"homepage":24,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":36,"analysis":134,"fingerprints":382},"wptuner","WP Tuner","0.9.6","MrPeteH","https:\u002F\u002Fprofiles.wordpress.org\u002Fmrpeteh\u002F","\u003Cp>The (mu-compatible) WP Tuner plugin for WordPress is a powerful and easy to use way to answer many hard questions about why your blog is slow or cranky. What’s causing the slowdown? Is it a plugin? Is it your host?\u003C\u002Fp>\n\u003Cp>Used with a bit of common sense, this powerful plugin will help blog administrators as well as software developers improve their WordPress blog performance.\u003C\u002Fp>\n\u003Cp>Perfect for WordPress site administrators, plugin and theme designers, developers\u003C\u002Fp>\n\u003Cp>Fully translatable.\u003C\u002Fp>\n\u003Ch3>Advanced Use\u003C\u002Fh3>\n\u003Cp>Here are more advanced ways to make use of \u003Cem>WP Tuner\u003C\u002Fem>. Please \u003Ca href=\"http:\u002F\u002Fblogs.icta.net\u002Fplugins\u002Fwptuner\" title=\"(Visit the WP Tuner home page)\" rel=\"nofollow ugc\">share your questions and\u002For stories\u003C\u002Fa> examples to share with others!\u003C\u002Fp>\n\u003Cp>1) Hook any WordPress action\u003C\u002Fp>\n\u003Cp>In wptuner.php, you will find a default set of action hooks. You can add as many hooks as you like for other actions. They look like this (just change “admin_footer” to the name of the action you want to measure):\u003C\u002Fp>\n\u003Cpre>\u003Ccode>add_action('admin_footer', 'wpTuneFilterTime' );\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Each hook adds a line to the \u003Cem>WP Tuner\u003C\u002Fem> performance analysis table, when that action is triggered.\u003C\u002Fp>\n\u003Cp>2) Time anything at all in WordPress\u003C\u002Fp>\n\u003Cp>WP Tuner contains a function that causes performance analysis for any section of WordPress code. Just use\u003Cbr \u002F>\n  wpTuneMarkTime(‘My Marker string’);\u003C\u002Fp>\n\u003Cp>…at the beginning of the code you want analyzed. Add another marker at the end if needed.\u003C\u002Fp>\n\u003Cp>For example, suppose you want to know how much time is spent loading each of the plugins you have enabled. Here’s how to do it, by adding two simple lines to wp-settings.php:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>if (function_exists(wpTuneMarkTime)) wpTuneMarkTime('Load Plugins'); \u002F\u002F ** Add THIS line **\n\nif ( get_option('active_plugins') ) {\n  $current_plugins = get_option('active_plugins');\n  if ( is_array($current_plugins) ) {\n    foreach ($current_plugins as $plugin) {\n      if (function_exists(wpTuneMarkTime)) wpTuneMarkTime('Plugin: '.$plugin); \u002F\u002F ** Add THIS line **\n      if ( '' != $plugin && 0 == validate_file($plugin) && file_exists(WP_PLUGIN_DIR . '\u002F' . $plugin) )\n        include_once(WP_PLUGIN_DIR . '\u002F' . $plugin);\n    }\n  }\n}\u003Ch3>Credits\u003C\u002Fh3>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>Many thanks to the WP Tuner translation team!\u003C\u002Fp>\n\u003Cp>Русский: \u003Ca href=\"http:\u002F\u002Flecactus.ru\" rel=\"nofollow ugc\">Кактусу\u003C\u002Fa> (updated through WP Tuner 0.9.3)\u003C\u002Fp>\n\u003Ch3>Readme Validator\u003C\u002Fh3>\n\u003Cp>This readme was validated using:\u003Cbr \u002F>\n\u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fabout\u002Fvalidator\u002F\" rel=\"ugc\">https:\u002F\u002Fwordpress.org\u002Fextend\u002Fplugins\u002Fabout\u002Fvalidator\u002F\u003C\u002Fa>\u003C\u002Fp>\n","Easily, powerfully, discover why your blog or plugin is slow or cranky. Comprehensive time and database access analyzer. WPmu. multi-lingual.",10,47339,30,8,"","2.8.4","2.0.6",[19,20,21,22,23],"database","performance","slow","speed","tuning","http:\u002F\u002Fblogs.icta.net\u002Fplugins\u002Fwptuner","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwptuner.zip",100,0,null,"2026-03-15T10:48:56.248Z",[],{"slug":32,"display_name":7,"profile_url":8,"plugin_count":33,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":13,"trust_score":34,"computed_at":35},"mrpeteh",1,94,"2026-04-04T22:34:58.966Z",[37,58,82,100,116],{"slug":38,"name":39,"version":40,"author":41,"author_profile":42,"description":43,"short_description":44,"active_installs":45,"downloaded":46,"rating":26,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":15,"download_link":55,"security_score":56,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":57},"templ-optimizer","Templ Optimizer","2.1.2","Templ","https:\u002F\u002Fprofiles.wordpress.org\u002Ftempl\u002F","\u003Cp>Templ Optimizer lets you optimize your site and improve its performance with just a few clicks.\u003C\u002Fp>\n\u003Cp>We at Templ have optimized 1000s of WordPress websites through the years, and we’ve gathered some of our best optimization tricks in this easy-to-use plugin.\u003C\u002Fp>\n\u003Cp>Clean your site’s database and tweak WordPress settings to make your website faster.\u003C\u002Fp>\n\u003Cp>Features:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Clean your site’s database\u003C\u002Fli>\n\u003Cli>Delete trashed posts\u003C\u002Fli>\n\u003Cli>Delete revisions\u003C\u002Fli>\n\u003Cli>Delete auto-drafts\u003C\u002Fli>\n\u003Cli>Delete orphaned post meta\u003C\u002Fli>\n\u003Cli>Delete expired transients\u003C\u002Fli>\n\u003Cli>Delete database tables with other prefix\u003C\u002Fli>\n\u003Cli>Convert MyISAM database tables to InnoDB\u003C\u002Fli>\n\u003Cli>Optimize database tables\u003C\u002Fli>\n\u003Cli>Change heartbeat interval (a.k.a. “heartbeat control”)\u003C\u002Fli>\n\u003Cli>Change WP Rocket cache preload interval\u003C\u002Fli>\n\u003Cli>Limit post revisions\u003C\u002Fli>\n\u003Cli>Increase WordPress memory limit\u003C\u002Fli>\n\u003Cli>WP-CLI support\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Clean your site’s database\u003C\u002Fh3>\n\u003Cp>Your WordPress database grows with time and often contains a lot of unnecessary data. Clean your database with Templ Optimizer and see the effect on your database size and experience the difference in performance.\u003C\u002Fp>\n\u003Ch3>Tweak WordPress & plugin settings\u003C\u002Fh3>\n\u003Cp>Contains many smart tweaks and settings for WordPress as well as some of the most popular plugins. Free up more resources for your site to handle visitors and speed up your website.\u003C\u002Fp>\n\u003Ch3>Got a feature request?\u003C\u002Fh3>\n\u003Cp>Are you missing a feature? Do you have ideas on how Templ Optimizer can be improved? Get in touch with us on our website: \u003Ca href=\"https:\u002F\u002Ftempl.io\u002F?utm_source=wordpress.org&utm_medium=readme&utm_campaign=templ-optimizer-readme\" rel=\"nofollow ugc\">https:\u002F\u002Ftempl.io\u002F\u003C\u002Fa>\u003C\u002Fp>\n","Optimize your site and improve its performance with a few clicks.",1000,9995,3,"2025-02-04T08:13:00.000Z","6.7.5","5.0","7.4",[53,19,54,20,22],"clean-up","optimize","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ftempl-optimizer.2.1.2.zip",92,"2026-03-15T15:16:48.613Z",{"slug":59,"name":60,"version":61,"author":62,"author_profile":63,"description":64,"short_description":65,"active_installs":66,"downloaded":67,"rating":34,"num_ratings":68,"last_updated":69,"tested_up_to":70,"requires_at_least":71,"requires_php":72,"tags":73,"homepage":79,"download_link":80,"security_score":81,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":57},"wp-admin-cache","WP Admin Cache","0.2.7","Grf Studio","https:\u002F\u002Fprofiles.wordpress.org\u002Fgrfstudio\u002F","\u003Cp>This lightweight plugin caches the most visited pages in the admin area; it uses ajax to prefetch the pages and stores them on the server for each user.\u003C\u002Fp>\n\u003Cp>The cache is useful for sites with many installed plugins, which often make the administrative section very slow, especially in the case of woocommerce with many displayed products.\u003C\u002Fp>\n","The first cache plugin for the WordPress admin area.",300,8234,11,"2020-06-13T13:33:00.000Z","5.4.19","4.6","5.6",[74,75,76,77,78],"admin-cache","admin-performance","admin-speed","slow-admin","woocommerce-performance","https:\u002F\u002Fwww.wpadmincache.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-admin-cache.zip",85,{"slug":83,"name":84,"version":85,"author":86,"author_profile":87,"description":88,"short_description":89,"active_installs":90,"downloaded":91,"rating":27,"num_ratings":27,"last_updated":92,"tested_up_to":93,"requires_at_least":94,"requires_php":72,"tags":95,"homepage":98,"download_link":99,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":57},"mysql-query-cache-stats","MySQL query cache stats","1.0.4","Moris Papasmadov","https:\u002F\u002Fprofiles.wordpress.org\u002Fmorisdov\u002F","\u003Cp>Admin dashboard widget measuring and monitoring MySQL \u002F MariaDB \u003Ca href=\"https:\u002F\u002Fmariadb.com\u002Fresources\u002Fblog\u002Fflexible-mariadb-server-query-cache\" title=\"MariaDB Query Cache\" rel=\"nofollow ugc\">query cache\u003C\u002Fa> performance & statistics – to optimize sizing configuration and highlight bottlenecks.\u003C\u002Fp>\n\u003Ch4>Why\u003C\u002Fh4>\n\u003Cp>Database Query for \u003Ca href=\"https:\u002F\u002Fkinsta.com\u002Fknowledgebase\u002Fwp-options-autoloaded-data\u002F#what-is-the-wp_options-table\" title=\"What is the wp_options table\" rel=\"nofollow ugc\">Options Autoload\u003C\u002Fa> is repeatedly executed for each WP page load and its poor performance has been identified as a good indicator for a poorly performing database resulting in slow site.\u003C\u002Fp>\n\u003Ch4>How\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>Use dashboard widget to measure and monitor \u003Ccode>Options Autoload Query Time\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Use dashboard widget to measure and monitor \u003Ccode>Options Autoload Query Size\u003C\u002Fcode>\u003Cbr \u002F>\nThis query result size increases constantly over time, as WP site usage grows – but its oversized sudden growth or constant balooning must not be overlooked.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Heavy plugins might rely heavily on adding data to \u003Ccode>Options Autoload Query Size\u003C\u002Fcode>.\u003Cbr \u002F>\nPoorly written plugins causing WP performance degradation have been found to constantly increase this query result size.\u003C\u002Fp>\n\u003Ch4>Time Metrics\u003C\u002Fh4>\n\u003Cp>‘Options Autoload Query Time’ is measured in milliseconds (ms)\u003C\u002Fp>\n\u003Cp>0 ms – great performance below one millisecond\u003Cbr \u002F>\n 1-2 ms – good performance\u003Cbr \u002F>\n 3-5 ms – OK performance\u003Cbr \u002F>\n 50+ ms – poor performance should be investigated\u003C\u002Fp>\n\u003Ch4>Size Metrics\u003C\u002Fh4>\n\u003Cp>‘Options Autoload Size’ is measured in Bytes\u003Cbr \u002F>\nIf you have the control to enable the database server wide query cache – configure query_cache_limit to be larger than \u003Ccode>Options Autoload Size\u003C\u002Fcode>\u003C\u002Fp>\n\u003Cp>20,000 Bytes – freshly installed clean wordpress site\u003Cbr \u002F>\n 30,000 Bytes – small wordpress site\u003Cbr \u002F>\n 50,000 Bytes – medium wordpress site\u003Cbr \u002F>\n 250,000 Bytes – large wordpress site\u003Cbr \u002F>\n 2,000,000+ Bytes – too large should be investigated\u003Cbr \u002F>\n( \u003Ccode>all above are rough metrics\u003C\u002Fcode> )\u003C\u002Fp>\n","Admin dashboard widget measuring MySQL database performance & query cache",40,3106,"2025-12-02T17:06:00.000Z","6.9.4","3.6",[19,96,20,23,97],"mariadb","wp_options","https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fmysql-query-cache-stats","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmysql-query-cache-stats.zip",{"slug":101,"name":102,"version":103,"author":104,"author_profile":105,"description":106,"short_description":107,"active_installs":11,"downloaded":108,"rating":26,"num_ratings":33,"last_updated":109,"tested_up_to":93,"requires_at_least":110,"requires_php":51,"tags":111,"homepage":114,"download_link":115,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":57},"debughawk","DebugHawk – WordPress Performance Monitoring & Debugging","1.2.0","A5hleyRich","https:\u002F\u002Fprofiles.wordpress.org\u002Fa5hleyrich\u002F","\u003Cp>\u003Cstrong>Monitor and debug WordPress performance issues with DebugHawk\u003C\u002Fstrong> – the performance monitoring tool built specifically for WordPress developers and site owners who need to identify what’s slowing down their site.\u003C\u002Fp>\n\u003Ch4>Why WordPress Sites Are Slow\u003C\u002Fh4>\n\u003Cp>Slow WordPress sites lose visitors, conversions, and search rankings. But identifying the root cause is difficult when frontend tools like Google PageSpeed Insights only show part of the picture.\u003C\u002Fp>\n\u003Cp>DebugHawk monitors both frontend and backend performance so you can see exactly what’s slowing down your WordPress site – whether it’s slow database queries, external API calls, or frontend Core Web Vitals problems.\u003C\u002Fp>\n\u003Ch4>What DebugHawk Monitors\u003C\u002Fh4>\n\u003Cp>\u003Cstrong>Frontend Performance Metrics:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Core Web Vitals\u003C\u002Fstrong> – LCP (Largest Contentful Paint), INP (Interaction to Next Paint), CLS (Cumulative Layout Shift), TTFB (Time to First Byte), FCP (First Contentful Paint)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Network Performance\u003C\u002Fstrong> – DNS lookup time, connection time\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Browser Resources\u003C\u002Fstrong> – HTTP requests, page weight, transfer sizes\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Backend Performance Tracking:\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Database Query Performance\u003C\u002Fstrong> – Slow queries, query count, total database time\u003C\u002Fli>\n\u003Cli>\u003Cstrong>PHP Execution\u003C\u002Fstrong> – Execution time, memory usage\u003C\u002Fli>\n\u003Cli>\u003Cstrong>External HTTP Requests\u003C\u002Fstrong> – API call timing, external service performance\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Object Cache Performance\u003C\u002Fstrong> – Hit ratio, cache effectiveness\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Page Cache Effectiveness\u003C\u002Fstrong> – Cache hits vs misses\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Redirect Detection\u003C\u002Fstrong> – Unnecessary redirects slowing page loads\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Debug Slow WordPress Sites\u003C\u002Fh4>\n\u003Cp>Unlike generic performance tools, DebugHawk understands WordPress architecture. It shows you:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Which plugins are causing slow database queries\u003C\u002Fli>\n\u003Cli>Which external APIs are timing out\u003C\u002Fli>\n\u003Cli>Whether your caching is working effectively\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Perfect for WordPress developers, agencies managing multiple sites, and site owners who need to diagnose performance issues quickly.\u003C\u002Fp>\n\u003Ch4>How It Works\u003C\u002Fh4>\n\u003Col>\n\u003Cli>\u003Cstrong>Automatic Monitoring\u003C\u002Fstrong> – Once configured, DebugHawk tracks performance on every page load\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Real User Monitoring (RUM)\u003C\u002Fstrong> – See actual performance data from your real visitors, not synthetic tests\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Historical Data\u003C\u002Fstrong> – Track performance over time, identify when issues started\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Encrypted Transmission\u003C\u002Fstrong> – All data is encrypted before sending to DebugHawk’s dashboard\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>No impact on site performance – the monitoring overhead is negligible.\u003C\u002Fp>\n\u003Ch4>Perfect For\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Cstrong>WordPress Developers\u003C\u002Fstrong> debugging slow queries and performance bottlenecks\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Agencies\u003C\u002Fstrong> monitoring client site performance across multiple WordPress sites\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Site Owners\u003C\u002Fstrong> who need to understand why their WordPress site is slow\u003C\u002Fli>\n\u003Cli>\u003Cstrong>WooCommerce Stores\u003C\u002Fstrong> tracking checkout performance and database optimization\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Membership Sites\u003C\u002Fstrong> monitoring server load and query performance\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Get Started\u003C\u002Fh4>\n\u003Col>\n\u003Cli>Sign up for a free trial at \u003Ca href=\"https:\u002F\u002Fdebughawk.com\" rel=\"nofollow ugc\">DebugHawk.com\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Install and activate this plugin\u003C\u002Fli>\n\u003Cli>Add your site configuration to \u003Ccode>wp-config.php\u003C\u002Fcode>\u003C\u002Fli>\n\u003Cli>Start monitoring your WordPress performance\u003C\u002Fli>\n\u003C\u002Fol>\n","Monitor WordPress performance, debug slow sites, track Core Web Vitals, database queries, memory usage, and cache effectiveness.",924,"2026-01-05T20:26:00.000Z","6.3",[112,113,20,21,22],"debug","monitoring","https:\u002F\u002Fdebughawk.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fdebughawk.1.2.0.zip",{"slug":117,"name":118,"version":119,"author":120,"author_profile":121,"description":122,"short_description":123,"active_installs":11,"downloaded":124,"rating":27,"num_ratings":27,"last_updated":125,"tested_up_to":126,"requires_at_least":127,"requires_php":15,"tags":128,"homepage":132,"download_link":133,"security_score":81,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":57},"retina-stripper","Retina Stripper","1.4","David Favor","https:\u002F\u002Fprofiles.wordpress.org\u002Fdfavor\u002F","\u003Cp>For now only occurrences of the \u003Ca href=\"http:\u002F\u002Fimulus.github.io\u002Fretinajs\" rel=\"nofollow ugc\">retina.js\u003C\u002Fa> script are dequeue + deregister.\u003C\u002Fp>\n\u003Cp>If you identify other Retina related scripts open a support ticket + note the name.\u003C\u002Fp>\n\u003Cp>I’ll add any other identified scripts here, to strip them out also.\u003C\u002Fp>\n\u003Ch3>Problems Serving Retina Images\u003C\u002Fh3>\n\u003Cp>Some of these problems include…\u003C\u002Fp>\n\u003Ch4>Retina Image File Size + Mobile\u003C\u002Fh4>\n\u003Cp>Retina images have massive size. If you’re running a Food Porn blog or\u003Cbr \u002F>\nImage Hosting site, this might be okay.\u003C\u002Fp>\n\u003Cp>Otherwise, likely your visitor on page time will decrease + conversions tank.\u003C\u002Fp>\n\u003Cp>If you’re running a Click Arbitrage site or target Mobile devices, which\u003Cbr \u002F>\nmay be on 3G networks or simply have under powered CPUs or little memory.\u003C\u002Fp>\n\u003Cp>This occurs as size of Retina images eat up all your visitor’s connection\u003Cbr \u002F>\nbandwidth, then require heavy CPU + memory usage to render.\u003C\u002Fp>\n\u003Ch4>Retina Image 404s On Server\u003C\u002Fh4>\n\u003Cp>Most sites serving Retina images, do so via the horribly simplistic \u003Ca href=\"http:\u002F\u002Fimulus.github.io\u002Fretinajs\" rel=\"nofollow ugc\">retina.js\u003C\u002Fa> library.\u003C\u002Fp>\n\u003Cp>Unfortunately this script works by…\u003C\u002Fp>\n\u003Cp>1) Extracting every DOM  tag + rewriting the URL as\u003Cbr \u002F>\n   image-name@2X.extension back into the DOM.\u003C\u002Fp>\n\u003Cp>2) For many sites 100% of these image-name@2X.extension file access\u003Cbr \u002F>\n   result in a 404 (missing page) error. Then \u003Ca href=\"http:\u002F\u002Fimulus.github.io\u002Fretinajs\" rel=\"nofollow ugc\">retina.js\u003C\u002Fa> will walk\u003Cbr \u002F>\n   the DOM again, removing the @2X from images + the image file\u003Cbr \u002F>\n   fetch begins again. Since this process runs via AJAX, instantaneously\u003Cbr \u002F>\n   page load resource usage can spike very high.\u003C\u002Fp>\n\u003Cp>3) WordPress caching plugins specifically avoid caching 404 errors. This\u003Cbr \u002F>\n   is intentional. The idea being, once you notice 404s, you’ll fix them.\u003Cbr \u002F>\n   If 404s were cached, every permanent + transient 404 error would\u003Cbr \u002F>\n   require a manual cache flush, to clear the cache object, so the fixed\u003Cbr \u002F>\n   page could then reach visitors.\u003C\u002Fp>\n\u003Cp>4) Thus every 404 @2X image served generates what tends to be an extremely\u003Cbr \u002F>\n   high resource intensive page view… all for nothing…\u003C\u002Fp>\n\u003Cp>5) If you have 20 images on a page you’ll generate 20x 404s.\u003C\u002Fp>\n\u003Cp>You can see when this can lead to extreme dips in performance,\u003Cbr \u002F>\nwhich are hard to diagnose, unless you have a Server Savant\u003Cbr \u002F>\ndoing daily log studies with logtop to monitor page view patterns.\u003C\u002Fp>\n\u003Cp>Some servers where I host client sites showed 90%+ of all page\u003Cbr \u002F>\naccesses were 404s to Retina images.\u003C\u002Fp>\n\u003Cp>As traffic spends or natural traffic increase, 404s increase,\u003Cbr \u002F>\nstarving Apache + Database till eventually all visitors see become\u003Cbr \u002F>\nApache 500 errors + Database Connection Errors.\u003C\u002Fp>\n\u003Ch3>Plugin History\u003C\u002Fh3>\n\u003Cp>This code was originally written to serve my many private hosting clients.\u003C\u002Fp>\n\u003Cp>Check [http:\u002F\u002FFastStableHosting.com]http:\u002F\u002FFastStableHosting.com WordPress speedups.\u003C\u002Fp>\n\u003Cp>This site is a work in process, where my goal is to converge all the many\u003Cbr \u002F>\nchecklists I’ve published over the years cohesively + retire all other\u003Cbr \u002F>\nsite with related WordPress performance boosting tips.\u003C\u002Fp>\n\u003Cp>Material presented on this site is based on testing, rather than drivel + myth\u003Cbr \u002F>\nwhich pollutes the entire WordPress ecosystem, at every turn.\u003C\u002Fp>\n\u003Cp>If you wonder why you keep reading how to speed up your site + nothing seems\u003Cbr \u002F>\nto make any difference, likely your reading content written by posers.\u003C\u002Fp>\n","For now only occurrences of the retina.js script are dequeue + deregister.",1876,"2016-05-18T13:44:00.000Z","4.5.33","3.5.0",[129,20,130,131,22],"database-connection","retina","server","http:\u002F\u002FDavidFavor.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fretina-stripper.1.4.zip",{"attackSurface":135,"codeSignals":215,"taintFlows":324,"riskAssessment":367,"analyzedAt":381},{"hooks":136,"ajaxHandlers":211,"restRoutes":212,"shortcodes":213,"cronEvents":214,"entryPointCount":27,"unprotectedCount":27},[137,143,147,152,156,159,162,165,168,171,174,177,180,182,185,188,191,194,197,200,203,208],{"type":138,"name":139,"callback":140,"file":141,"line":142},"action","init","wptuner_auto_update","wptuner.php",97,{"type":138,"name":144,"callback":145,"file":141,"line":146},"admin_menu","wptuner_add_admin_menu",107,{"type":148,"name":149,"callback":150,"file":141,"line":151},"filter","plugin_action_links","wptuner_plugin_actions",108,{"type":138,"name":153,"callback":154,"file":141,"line":155},"plugins_loaded","wpTuneFilterTime",136,{"type":138,"name":157,"callback":154,"file":141,"line":158},"admin_init",137,{"type":138,"name":160,"callback":154,"file":141,"line":161},"admin_head",138,{"type":138,"name":163,"callback":154,"file":141,"line":164},"admin_notices",139,{"type":138,"name":166,"callback":154,"file":141,"line":167},"admin_footer",140,{"type":138,"name":169,"callback":154,"file":141,"line":170},"activity_box_end",141,{"type":138,"name":172,"callback":154,"file":141,"line":173},"load_feed_engine",142,{"type":138,"name":175,"callback":154,"file":141,"line":176},"wp_authenticate",143,{"type":138,"name":178,"callback":154,"file":141,"line":179},"wp_login",144,{"type":138,"name":139,"callback":154,"file":141,"line":181},145,{"type":138,"name":183,"callback":154,"file":141,"line":184},"widgets_init",146,{"type":138,"name":186,"callback":154,"file":141,"line":187},"posts_selection",147,{"type":138,"name":189,"callback":154,"file":141,"line":190},"wp_head",148,{"type":138,"name":192,"callback":154,"file":141,"line":193},"get_sidebar",149,{"type":138,"name":195,"callback":154,"file":141,"line":196},"loop_start",150,{"type":138,"name":198,"callback":154,"file":141,"line":199},"get_footer",151,{"type":138,"name":139,"callback":201,"file":141,"line":202},"wptuner_buf",154,{"type":138,"name":204,"callback":205,"priority":206,"file":141,"line":207},"wp_footer","wptuner_foot",9999999999,164,{"type":138,"name":166,"callback":205,"priority":209,"file":141,"line":210},999999999,165,[],[],[],[],{"dangerousFunctions":216,"sqlUsage":222,"outputEscaping":224,"fileOperations":14,"externalRequests":27,"nonceChecks":27,"capabilityChecks":322,"bundledLibraries":323},[217],{"fn":218,"file":219,"line":220,"context":221},"create_function","wptunerdebug.php",70,"create_function(",{"prepared":27,"raw":27,"locations":223},[],{"escaped":225,"rawEcho":226,"locations":227},6,47,[228,230,231,233,235,237,239,241,243,245,247,249,251,253,255,256,259,261,263,265,267,269,271,273,275,277,279,281,283,285,287,289,291,293,295,297,299,301,303,305,307,309,312,313,315,317,320],{"file":219,"line":11,"context":229},"raw output",{"file":219,"line":68,"context":229},{"file":219,"line":232,"context":229},12,{"file":219,"line":234,"context":229},13,{"file":219,"line":236,"context":229},14,{"file":219,"line":238,"context":229},15,{"file":219,"line":240,"context":229},16,{"file":219,"line":242,"context":229},20,{"file":219,"line":244,"context":229},42,{"file":219,"line":246,"context":229},46,{"file":219,"line":248,"context":229},53,{"file":219,"line":250,"context":229},54,{"file":219,"line":252,"context":229},58,{"file":219,"line":254,"context":229},67,{"file":219,"line":254,"context":229},{"file":257,"line":258,"context":229},"wptunersetup.php",392,{"file":257,"line":260,"context":229},398,{"file":257,"line":262,"context":229},424,{"file":257,"line":264,"context":229},425,{"file":257,"line":266,"context":229},426,{"file":257,"line":268,"context":229},442,{"file":257,"line":270,"context":229},446,{"file":257,"line":272,"context":229},456,{"file":257,"line":274,"context":229},462,{"file":257,"line":276,"context":229},478,{"file":257,"line":278,"context":229},481,{"file":257,"line":280,"context":229},482,{"file":257,"line":282,"context":229},491,{"file":257,"line":284,"context":229},493,{"file":257,"line":286,"context":229},495,{"file":257,"line":288,"context":229},500,{"file":257,"line":290,"context":229},502,{"file":257,"line":292,"context":229},505,{"file":257,"line":294,"context":229},507,{"file":257,"line":296,"context":229},513,{"file":257,"line":298,"context":229},574,{"file":257,"line":300,"context":229},590,{"file":257,"line":302,"context":229},597,{"file":257,"line":304,"context":229},618,{"file":257,"line":306,"context":229},626,{"file":257,"line":308,"context":229},632,{"file":310,"line":311,"context":229},"wptunershow.php",93,{"file":310,"line":173,"context":229},{"file":310,"line":314,"context":229},159,{"file":310,"line":316,"context":229},160,{"file":318,"line":319,"context":229},"wptunertop.php",96,{"file":318,"line":321,"context":229},116,2,[],[325,354],{"entryPoint":326,"graph":327,"unsanitizedCount":352,"severity":353},"wptuner_show_admin_page (wptunersetup.php:311)",{"nodes":328,"edges":348},[329,334,340,344],{"id":330,"type":331,"label":332,"file":257,"line":333},"n0","source","$_POST (x3)",341,{"id":335,"type":336,"label":337,"file":257,"line":338,"wp_function":339},"n1","sink","update_option() [Settings Manipulation]",349,"update_option",{"id":341,"type":331,"label":342,"file":257,"line":343},"n2","$_POST",377,{"id":345,"type":336,"label":346,"file":257,"line":260,"wp_function":347},"n3","echo() [XSS]","echo",[349,351],{"from":330,"to":335,"sanitized":350},false,{"from":341,"to":345,"sanitized":350},4,"medium",{"entryPoint":355,"graph":356,"unsanitizedCount":27,"severity":366},"\u003Cwptunersetup> (wptunersetup.php:0)",{"nodes":357,"edges":362},[358,359,360,361],{"id":330,"type":331,"label":332,"file":257,"line":333},{"id":335,"type":336,"label":337,"file":257,"line":338,"wp_function":339},{"id":341,"type":331,"label":342,"file":257,"line":343},{"id":345,"type":336,"label":346,"file":257,"line":260,"wp_function":347},[363,365],{"from":330,"to":335,"sanitized":364},true,{"from":341,"to":345,"sanitized":364},"low",{"summary":368,"deductions":369},"The plugin \"wptuner\" v0.9.6 exhibits a mixed security posture. On the positive side, there are no reported vulnerabilities in its history, and all SQL queries are properly prepared, suggesting a foundational understanding of secure database interactions. The absence of external HTTP requests also reduces the risk of supply chain attacks or data exfiltration through external services. However, several concerning signals are present in the static analysis.\n\nThe primary concern is the use of the deprecated `create_function()` which can lead to arbitrary code execution if not handled with extreme care, especially if any part of its arguments are influenced by user input. Furthermore, a significant portion of the plugin's output (89%) is not properly escaped, posing a substantial risk of Cross-Site Scripting (XSS) vulnerabilities. The taint analysis revealed one flow with an unsanitized path, which, although not classified as critical or high, warrants attention as it indicates a potential avenue for path traversal or file manipulation vulnerabilities. The lack of nonce checks across any of its entry points is also a significant weakness, leaving any potential future AJAX or other handler vulnerable to Cross-Site Request Forgery (CSRF) attacks. The low number of capability checks further compounds this risk.\n\nWhile the lack of a vulnerability history is a good sign, it doesn't negate the inherent risks identified in the code. The static analysis reveals weaknesses that could be exploited to create vulnerabilities, especially the unescaped output and the presence of `create_function()`. Therefore, while the plugin has some strengths, the identified code signals and taint flow create significant security concerns that need to be addressed.",[370,372,374,376,378],{"reason":371,"points":238},"Use of deprecated create_function()",{"reason":373,"points":14},"High percentage of unescaped output",{"reason":375,"points":11},"Taint flow with unsanitized path",{"reason":377,"points":11},"No nonce checks on entry points",{"reason":379,"points":380},"Limited capability checks",5,"2026-03-16T23:30:54.697Z",{"wat":383,"direct":394},{"assetPaths":384,"generatorPatterns":388,"scriptPaths":389,"versionParams":390},[385,386,387],"\u002Fwp-content\u002Fplugins\u002Fwptuner\u002Fjs\u002Fwptuner-admin.js","\u002Fwp-content\u002Fplugins\u002Fwptuner\u002Fjs\u002Fwptuner.js","\u002Fwp-content\u002Fplugins\u002Fwptuner\u002Fcss\u002Fwptuner.css",[],[385,386],[391,392,393],"wptuner\u002Fjs\u002Fwptuner-admin.js?ver=","wptuner\u002Fjs\u002Fwptuner.js?ver=","wptuner\u002Fcss\u002Fwptuner.css?ver=",{"cssClasses":395,"htmlComments":397,"htmlAttributes":399,"restEndpoints":400,"jsGlobals":401,"shortcodeOutput":403},[396],"wptuner-debug-info",[398],"\u003C!-- wptuner-->",[],[],[402],"wptuner_admin",[]]