Pantry Cleanup compared with Disable Comments, Asset CleanUp and Perfmatters

Pantry Cleanup switches off the WordPress features a site is not using: the emoji script, oEmbed discovery, XML-RPC, the RSD and Windows Live Writer links in the page head, author archives, comments, jQuery Migrate, Dashicons on the front end, and the revision, autosave and Heartbeat settings that run in the background. That is the whole job: a dozen switches, each one on or off, each one doing exactly what its label says.

Most sites hand this job to a general-purpose performance plugin that also manages caching, image optimisation and per-page script loading, or to a single-purpose plugin that only covers one of the dozen switches, comments being the most common. Either route adds settings a site owner did not ask for, or a paid licence for a toolkit built to do far more than switch things off.

This article compares Pantry Cleanup with the plugins most sites already use for this job, and says plainly where each one is the better fit. The answer is not always Pantry.

The plugins most people install

Disable Comments has 1+ million active installations, making it the most widely used answer to just one of Pantry Cleanup's dozen switches: comments. It disables comments per post type or sitewide, and its current version adds conditional rules by taxonomy, page template or post age, a bulk dry-run tool for deleting existing comments, and a quick-setup wizard that runs immediately after activation. It is maintained by the WPDeveloper team and is free, with no paid tier.

Asset CleanUp has 100,000+ active installations. Its core job is different from Pantry Cleanup's: rather than a fixed set of switches, it lets a site owner inspect every CSS and JavaScript file loading on a given page and turn off the ones that page does not use, alongside options to remove the emoji script and Dashicons and to lazy-load images. The free Lite version covers posts, pages and custom post types; the paid Pro tier adds control over archive pages, async and defer attributes, device-specific rules, and a Plugins Manager that can stop an entire plugin running on chosen pages, a feature the free version only shows as a read-only preview.

Featherweight, still listed on wordpress.org under its original slug wp-disable, has 10,000+ active installations and is the closest match to Pantry Cleanup's scope. Its toggles cover the emoji script, oEmbeds, jQuery Migrate, Google Fonts and Font Awesome loading, the password-strength meter, the RSD and Windows Live Writer links, comments and pingbacks, revisions, autosave, Heartbeat, RSS feeds, XML-RPC and author archives, then go further with switches for Yoast SEO's HTML comments and breadcrumbs and for WooCommerce script loading and cart fragments. It is free and open source, with no paid tier.

Perfmatters is not listed on wordpress.org; it is sold directly from the developer's own site, perfmatters.io. Alongside feature toggles similar to the other three, it bundles a per-page script manager, image and video lazy loading, unused-CSS removal, database optimisation and local hosting of Google Analytics. There is no free tier: a licence costs $29.95 a year for one site, $59.95 a year for three sites, or $124.95 a year for unlimited sites, with a 15 percent renewal discount applied automatically.

Where the big plugins cost you

Featherweight's single settings screen carries switches for two other plugins a site might not even run. Yoast SEO's HTML comments and breadcrumb behaviour, and WooCommerce's script loading and cart fragments, sit in the same tabbed dashboard as the WordPress-native toggles, so a site without either plugin installed still sees settings written for them. Disable Comments takes the opposite shape: rather than one switch, it ships a quick-setup wizard on activation, conditional rules by taxonomy, template and post age, and a bulk dry-run deletion tool, for a job that on most sites is a single decision made once and left alone.

Asset CleanUp's free Lite version shows its Plugins Manager screen but will not act on it: stopping a plugin from running on a chosen page needs the Pro licence. The same pattern runs through the rest of its Pro upgrade list, archive-page control, async and defer attributes, device rules, each one a specific thing a site owner might want that the free version can only preview rather than do.

Perfmatters has no free version at all, and no free trial. Trying a single toggle, such as disabling the emoji script, means buying an annual licence first. An agency running the same toggle across several client sites either buys the unlimited-site tier at $124.95 a year or manages several separate licences at the lower tiers.

None of the four publish a measured PHP line count, a zip size, or a fixed list of what they will not do. A site owner comparing them has marketing copy, a changelog and a pricing page to go on, not a published contract for what the plugin is and is not going to become.

What Pantry Cleanup does instead

Pantry Cleanup does the twelve things listed on its own plugin page and nothing else: turn off the emoji detection script and inline styles; turn off oEmbed discovery links and the wp-embed script; turn off XML-RPC and remove the X-Pingback header that advertises it; remove the RSD link, the Windows Live Writer manifest link, the shortlink, the generator tag and the default feed links from the page head; stop WordPress pinging its own posts when one links to another; block the REST API's user-listing routes for visitors who are not logged in; send author archives to a 404 and rewrite author links to the homepage; close comments and pingbacks sitewide, hide the Comments menu and admin-bar item, and remove comment feeds, while leaving comments already stored in the database untouched; drop jQuery Migrate from the front end; remove Dashicons on the front end for visitors who are not logged in; limit how many revisions WordPress keeps per post and how often it autosaves; and set or turn off the Heartbeat interval, with a separate switch just for the dashboard screen. Every switch is off by default, and turning one on changes only the thing it names.

Two of the switches make a point of not overriding something else. The revisions switch checks for the WP_POST_REVISIONS constant in wp-config.php first; if that constant is already defined, the settings screen says so plainly and the switch has no effect, because a value set directly in code should win over a value set in a database option. The comments switch closes comments and hides the screens for managing them, but never runs a query that deletes anything: comments already in the database stay there, in case the switch is turned off again later or the data is wanted for another reason.

Pantry Cleanup follows the same rules as every Pantry plugin: no admin notice after activation beyond a PHP-version warning if the server runs something older than PHP 8.1, no tracking or phone-home of any kind, and nothing withheld for a paid tier that the free plugin only lets a site owner see. All twelve switches sit on the one screen at Plugin Pantry > Cleanup, grouped into sections for emoji and embeds, XML-RPC and the REST API, the page head and author archives, comments, scripts and styles, revisions and autosave, and Heartbeat.

The measured footprint, from the plugin's own FACTS.json: an 18KB zip, 1,297 lines of PHP, and one options row, pantry_cleanup_settings, holding every switch and number as a single array. No custom database tables, no custom post type, no cron event, no transient, no post meta. Admin CSS and JS load only on the Plugin Pantry > Cleanup screen, and there are no front-end assets and no external requests: every switch works by adding or removing a WordPress hook, never by loading a script or calling out to another server.

What it does not do, and who should stay with the big plugin

Pantry Cleanup's own published limits are exact: no per-page script manager, no caching or minification, no database clean-up, and no image or font optimisation. Those four gaps are deliberate, and they describe most of what the four competitors above actually specialise in.

A site owner who wants to see every script and stylesheet loading on a specific page and switch individual ones off, rather than pick from a fixed dozen toggles, needs Asset CleanUp; that per-page inspection is its whole reason to exist, and its free Lite version already does it for posts, pages and custom post types. A site that wants caching, minification, database optimisation and image handling alongside its feature toggles, in one paid product with support included, is better served by Perfmatters, which builds all of that in rather than expecting a second and third plugin alongside it. Neither job is one Pantry Cleanup will grow into: adding a script manager or a database cleaner would turn a dozen fixed switches into an open-ended settings screen, which is the exact shape the plugin exists to avoid.

Moving over

Moving from Featherweight is the most direct migration of the four, because most of its switches and Pantry Cleanup's twelve name the same underlying WordPress hook. Its emoji, oEmbeds, jQuery Migrate, head-links, comments, revisions, autosave, Heartbeat, XML-RPC and author-archive toggles map one-to-one to Pantry Cleanup's switches of the same name; the numeric settings for revisions kept, autosave seconds and Heartbeat seconds need typing in again, since there is no export file, just three numbers to copy across by hand. Featherweight's switches for Google Fonts, Font Awesome, the password-strength meter, spam auto-cleanup, and its Yoast SEO and WooCommerce settings have no equivalent in Pantry Cleanup and do not carry across; a site relying on any of them needs to keep Featherweight active for those switches alone, or find a plugin built for that specific job.

Moving from Disable Comments only replaces one of Pantry Cleanup's twelve switches. Its sitewide close-comments behaviour maps to Pantry Cleanup's single Comments switch; existing comments are kept either way, since both plugins filter comment display rather than delete anything. What does not carry across is precision: Disable Comments can close comments on one post type while leaving another open, or by taxonomy, template or post age, where Pantry Cleanup's switch is sitewide only, on or off. A site using that finer targeting should keep Disable Comments for comments and use Pantry Cleanup for the other eleven switches, since nothing stops the two plugins running together on settings they do not share.

Moving from Asset CleanUp or Perfmatters means separating the two jobs first. Whichever feature toggles those plugins also offer, emoji and Dashicons removal being the most common overlap, can move to the matching Pantry Cleanup switch, then be switched off in the old plugin so the same hook is not touched twice. The per-page script control, lazy loading, database work, caching and minification that make up the rest of either plugin have no Pantry Cleanup equivalent and are not part of the migration; the old plugin stays installed for those, with only its overlapping toggles turned off.

The short version

Pantry Cleanup is worth installing on a site that wants a fixed, published list of WordPress features switched off, with nothing else to configure and nothing held back for a later upgrade. It is not a substitute for Asset CleanUp on a site that needs per-page control over scripts and styles, and it is not a substitute for Perfmatters on a site that wants caching, database work and image optimisation in the same product. The plugin's argument is its size: twelve switches, one screen, and a published list of what it will never do.

Measure	Pantry Cleanup
Zip size	18 KB
PHP lines	1,297
Options	1 (pantry_cleanup_settings)
Custom tables	0
Front-end assets	0
External requests	0
Tracking	None
Locked features	None