abhishek

Abhishek Deshpande

WordPress prioritises backwards compatibility. 
That’s a feature. It also means every install ships with things you didn’t ask for.
An emoji CDN script. An oEmbed script. A Windows Live Writer manifest (discontinued 2017). 
Dashicons loaded for logged-out visitors. Heartbeat polling every 15 seconds. 
A version tag that tells the world exactly which WordPress you’re running.
None of these are bugs. They’re just not needed on most sites.
Disable what you don’t need. Keep what you do.
The Off Switch lets you disable each one, individually.
<h4>The Off Switches</h4>
<ul>
<li>Emoji script – ~15 KB + 1 HTTP request. Browsers handle emoji natively.</li>
<li>Embed script – ~4 KB + oEmbed discovery links in <code><head></code>.</li>
<li>RSD link – Really Simple Discovery. Only needed for legacy XML-RPC clients.</li>
<li>WLW manifest – Windows Live Writer has been discontinued since 2017.</li>
<li>WP version tag – Stops advertising your WordPress version to the world.</li>
<li>Shortlink – Removes <code><link rel="shortlink"></code> from <code><head></code> and HTTP headers. Search engines ignore it.</li>
<li>Asset query strings – Strips <code>?ver=</code> from scripts, styles, and WP 6.5+ Script Modules so CDNs and proxies cache correctly.</li>
<li>XML-RPC – Closes a common brute-force attack vector.</li>
<li>XML-RPC Kill Requests – Goes further than disabling: hard-kills any incoming xmlrpc.php request with a 403 before WordPress loads at all.</li>
<li>Heartbeat API – Reduces admin polling from every 15 s to every 60 s.</li>
<li>Dashicons (frontend) – ~35 KB (CSS + font) saved for every logged-out visitor.</li>
<li>REST API Discovery Link – Removes <code><link rel="https://api.w.org/"></code> from <code><head></code>. Safe to remove on standard sites.</li>
<li>RSS Feed Links – Removes feed autodiscovery <code><link></code> tags from <code><head></code>. Modern browsers no longer act on them. Leave enabled if you publish an RSS feed.</li>
<li>Speculation Rules (WP 6.8+) – Disables the WP 6.8+ Speculation Rules API that prefetches links before users click. Can inflate analytics, increase server bandwidth, and trigger consent flows on unfetched pages.</li>
<li>Disable All Feeds – Redirects all RSS and Atom feed URLs to the homepage. For sites with no RSS subscribers.</li>
<li>Comment Auto-Links – Stops WordPress from converting plain-text URLs in comments into clickable links.</li>
<li>Editor Autosave – Deregisters the autosave script that POSTs editor content to the server every 60 seconds. For teams that prefer explicit saves.</li>
<li>DNS Prefetch – Removes all <code><link rel="dns-prefetch"></code> hints from <code><head></code>. Redundant when Emojis and Embeds are already disabled.</li>
<li>Recent Comments Inline CSS – WordPress outputs a small inline <code><style></code> block in <code><head></code> whenever the Recent Comments widget is active. Remove it if your theme already styles the widget.</li>
</ul>
<h4>Script & Style Control</h4>
<ul>
<li>jQuery Migrate – ~30 KB. Modern themes don’t need it.</li>
<li>Block Library CSS – ~7 KB loaded on every page, even with no Gutenberg blocks.</li>
<li>Global Styles (theme.json CSS) – 10-50 KB inline CSS from block themes.</li>
<li>SVG Duotone Filters – Hidden SVG blob injected on every page, even with no duotone images.</li>
<li>Script/Style type attributes – <code>type="text/javascript"</code> and <code>type="text/css"</code> are redundant in HTML5.</li>
<li>Defer non-critical JavaScript – Adds <code>defer</code> so scripts don’t block HTML parsing. jQuery is never deferred.</li>
<li>Move scripts to footer – Relocates enqueued scripts from <code><head></code> to just before <code></body></code>. jQuery is never moved.</li>
</ul>
<h4>WordPress Behaviour Tweaks</h4>
<ul>
<li>Self-pingbacks – WordPress pings your own posts when you link between them – a wasted HTTP request that creates an unwanted comment on the target post.</li>
<li>Capital P filter – WordPress corrects “WordPress” to “WordPress” on every rendered string. Remove if you don’t need the autocorrect.</li>
<li>Limit post revisions – WordPress stores unlimited revisions per post. Caps revisions at 3 to prevent silent database growth on active editorial sites.</li>
<li>Attachment pages – WordPress creates a full template page for every uploaded file. These waste crawl budget on most sites. Sends a 301 redirect to the parent post instead.</li>
<li>Comments – Closes all comments and pingbacks site-wide, hides existing comments on the frontend, and removes comment-related UI from wp-admin (Comments menu, admin bar node, dashboard widget). Enable only if your site does not use comments.</li>
<li>Search – Redirects all WordPress search queries (<code>/?s=</code>) to the homepage with a 301, preventing bots from triggering repeated database queries. Also removes search forms rendered via <code>get_search_form()</code>. Hardcoded forms in theme templates are not affected.</li>
<li>oEmbed Provider – WordPress registers a REST endpoint at <code>/wp-json/oembed/1.0/embed</code> so other sites can embed your content via the oEmbed protocol. Remove it if you don’t want your content embeddable externally. Does not affect your ability to embed others’ content.</li>
<li>Post via Email – Removes the Post via Email configuration from Writing Settings and disables the feature. Almost no modern site uses email-to-post.</li>
<li>Update Services (Ping-o-Matic) – Removes Update Services from Writing Settings and stops outbound pings to weblog ping services on every published post.</li>
</ul>
<h4>Database & Query</h4>
<ul>
<li>Expired Transients – Schedules a daily cleanup of expired transient rows in wp_options. Useful on low-traffic sites where WP-Cron can go days without firing.</li>
<li>Abandoned Auto-Drafts – WordPress creates an auto-draft every time the post editor opens. Abandoned sessions leave these rows permanently. Runs a daily sweep to delete auto-drafts older than 30 days.</li>
<li>Skip Row Count on Singles – On every single post or page, MySQL runs SQL_CALC_FOUND_ROWS to count total matching rows – a full index scan only needed for paginated archives. Removes that sub-query on all singular views.</li>
<li>Adjacent Post Links – WordPress queries the previous and next post on every single post page to output <code><link rel="prev/next"></code> in <code><head></code>. Two extra DB queries per page load. Google dropped support for these SEO hints in 2019.</li>
<li>Reduce Trash Retention – WordPress keeps trashed items for 30 days before permanent deletion. Reducing to 7 days keeps wp_posts leaner on active editorial sites without affecting normal recovery workflows.</li>
</ul>
<h4>Image Performance</h4>
<ul>
<li>Google Fonts display:swap – Without <code>font-display:swap</code>, the browser hides text while your Google Font downloads (FOIT). Adds <code>display=swap</code> to every Google Fonts URL so visitors see text immediately.</li>
<li>Add missing image dimensions – Images without <code>width</code> and <code>height</code> attributes cause layout shifts (CLS). Reads dimensions from attachment metadata and injects them automatically.</li>
<li>LCP image priority – Adds <code>fetchpriority="high"</code> to the first content image so the browser loads it before lower-priority resources. Adds <code>fetchpriority="low"</code> and <code>decoding="async"</code> to all others.</li>
<li>Lazy load images – Adds <code>loading="lazy"</code> to images below the fold. The first image is never lazy-loaded – it is the LCP candidate and must load immediately.</li>
<li>Disable PDF thumbnails – WordPress generates thumbnail previews for every uploaded PDF when ImageMagick is available. Rarely used on the frontend; adds significant upload processing time.</li>
<li>Disable scaled images – WordPress 5.3+ creates a downsized -scaled copy of any image whose longest side exceeds 2560 px on upload. On most sites this extra file is never served. Disabling it stores the original as-uploaded. Applies to new uploads only.</li>
<li>Disable extra image sizes – WordPress 5.3 added 1536×1536 and 2048×2048 intermediate sizes to every image upload. These oversized copies are rarely requested and waste disk space. Theme and plugin image sizes are not affected. Applies to new uploads only.</li>
</ul>
<h4>Security & Admin Hardening</h4>
<ul>
<li>Block User Enumeration – WordPress redirects <code>?author=1</code> to <code>/author/username/</code>, exposing registered usernames. Intercepts those requests and redirects to the homepage before the username is revealed.</li>
<li>Disable Author Archives – Redirects all <code>/author/username/</code> pages to the homepage. For sites with no author profile pages.</li>
<li>Disable File Editor – Defines <code>DISALLOW_FILE_EDIT</code> to remove the plugin and theme code editor from wp-admin. Eliminates a code-injection surface a compromised admin account could exploit.</li>
<li>Disable Application Passwords – Removes the Application Passwords UI and stops all tokens from being accepted. For sites that don’t use REST API or XML-RPC integrations.</li>
<li>Suppress Admin Email Check – Disables the periodic full-screen prompt asking admins to confirm their email address. One less interruption, no functional change.</li>
<li>Remove X-Pingback Header – Strips <code>X-Pingback:</code> from every HTTP response, stopping the site from advertising its XML-RPC endpoint URL to scanners.</li>
<li>Clean Admin Bar – Removes the WordPress logo dropdown, the duplicate “Visit Site” link, and the admin bar search for a less cluttered editing environment.</li>
<li>Hide Update Nag for Non-Admins – Hides the core update notice from editors and contributors who cannot action it. Administrators still see it normally.</li>
<li>Restrict REST API to Logged-In Users – The REST API is publicly accessible by default, allowing unauthenticated enumeration of posts, users, and other data. Restricting access to authenticated users reduces the attack surface. Will break public REST consumers such as headless frontends.</li>
<li>Redirect Unauthenticated Admin Access – By default, visiting /wp-admin/ without being logged in redirects to the login page, confirming a WordPress admin area exists. This redirects unauthenticated requests to the homepage instead, reducing information disclosure to scanners. AJAX, Cron, WP-CLI, and admin-post.php requests are never affected.</li>
<li>Hide Author Sitemap – WordPress 5.5 added a built-in XML sitemap that includes a users file listing the author archive URL for every user with published posts — up to 2,000 usernames, publicly accessible. Removes the users entry from the sitemap index entirely (WP 5.5+, default ON).</li>
<li>Remove X-Redirect-By Header – WordPress 5.1+ adds an X-Redirect-By: WordPress header on every redirect, openly advertising that the site runs WordPress. Removes it from all redirects (default ON).</li>
<li>Hide PHP Version Header – PHP sends an X-Powered-By: PHP/x.x.x header on every response, exposing your exact PHP version to every visitor and scanner. Removes it from all responses (default ON).</li>
<li>Generic PHP Error Messages – WordPress fatal error messages can include internal file paths and line numbers. Replaces them with a generic response that reveals nothing about server structure (default ON).</li>
<li>Hide Admin Bar on Frontend – Removes the WordPress admin toolbar from the public-facing site for all logged-in users. Reduces frontend CSS/JS overhead for logged-in sessions (default OFF).</li>
<li>Remove Dashboard Welcome Panel – Removes the “Welcome to WordPress” panel from the dashboard home screen for all users (default OFF).</li>
<li>Remove Default Dashboard Widgets – Removes four default dashboard widgets including WordPress Events and News, which makes an outbound HTTP request to api.wordpress.org on every dashboard load (default OFF).</li>
<li>Remove Admin Footer Text – Removes the “Thank you for creating with WordPress” text and WordPress version number from the wp-admin footer (default OFF).</li>
<li>Disable REST Users Endpoint – WordPress’s REST API exposes <code>/wp-json/wp/v2/users</code> publicly, returning usernames and slugs for all users with published posts. Removes this endpoint for unauthenticated requests only — Gutenberg and plugins that need it while logged in are unaffected (default ON).</li>
<li>Disable Email Change Notifications – WordPress sends emails to users when their email address or password changes. On agency-managed sites these are noise. Suppresses both notification types (default OFF).</li>
<li>Disable Auto-Update Emails – WordPress emails after every automatic core, plugin (WP 5.5+), and theme (WP 5.5+) update. On sites where auto-updates are routine these arrive constantly (default OFF).</li>
<li>Auto-Update Emails: Errors Only – A middle ground: suppresses core auto-update success emails only. Failure emails still arrive so you know when action is needed (default OFF).</li>
<li>Skip Bundled Themes on Upgrade – Defines <code>CORE_UPGRADE_SKIP_NEW_BUNDLED</code> to stop WordPress installing a new default theme on every core upgrade. Existing themes are not affected (default OFF).</li>
</ul>
<h4>Block Editor</h4>
<ul>
<li>Remote Block Patterns – WordPress fetches patterns from api.wordpress.org on every editor load. An outbound HTTP request that adds latency even if editors never use the Pattern inserter. Local patterns from themes and plugins are unaffected.</li>
<li>Core Block Patterns – Removes WordPress’s built-in block patterns (headers, galleries, CTAs) from the Pattern inserter. For sites using custom patterns or none at all.</li>
<li>Block Directory – The editor includes a live search of wordpress.org that lets users install new blocks without leaving the editor. Remove it to keep block installation under your control.</li>
<li>Font Library (WP 6.5+) – WordPress 6.5 added a Font Library panel for uploading custom fonts and browsing Google Fonts in the Site Editor. Remove it if fonts are managed through your theme or code.</li>
<li>Widget Block Editor (WP 5.8+) – WordPress 5.8 replaced the classic Widgets screen with a block-based editor. Restores the classic screen for classic themes, sidebar widgets, and page builders.</li>
</ul>
<h4>WooCommerce</h4>
These toggles are only shown when WooCommerce is active.
<ul>
<li>Cart Fragments – wc-cart-fragments.js fires an AJAX request to keep mini-cart counts accurate when the Cart Widget is rendered (~3 KB + 1 request). Disable on stores where the Cart Widget is not used, or where real-time cart accuracy across tabs is not needed.</li>
<li>WooCommerce Generator Tag – Removes <code><meta name="generator" content="WooCommerce x.x.x"></code> from <code><head></code>. Same reason as the WordPress version tag: stops advertising which version of WooCommerce you’re running.</li>
<li>WC Scripts on Non-WC Pages – WooCommerce loads ~114 KB of CSS and JS on every page (woocommerce-general, woocommerce-layout, woocommerce-smallscreen, woocommerce.js, wc-add-to-cart.js, and woocommerce-blocktheme on block themes). Dequeues them all on non-shop, non-cart, non-checkout, and non-account pages. Up to ~30 KB gzipped saved per non-WooCommerce page.</li>
<li>Password Strength Meter – WooCommerce already restricts wc-password-strength-meter to checkout and My Account pages where a password is required. This toggle is a secondary safety net for themes or plugins that enqueue the script more broadly, removing zxcvbn (~80 KB gzipped) wherever it loads unnecessarily.</li>
<li>Status Dashboard Widget – Removes the WooCommerce Status meta box from the WordPress admin dashboard. For stores managed from the WooCommerce screens directly.</li>
<li>WC Block Patterns – WooCommerce registers its own block patterns in the editor inserter. Remove them if your store does not use WooCommerce-provided patterns for page design – declutters the inserter and removes a small init overhead.</li>
<li>WC Legacy Widgets – WooCommerce registers 12 legacy widgets on every page load even on block-based themes. Unregistering them removes the initialisation overhead and hides them from Appearance -> Widgets.</li>
<li>WC Version Header – Removes the X-WooCommerce-Version HTTP response header that some WooCommerce extensions inject, closing the same version-leakage vector as the generator tag toggle.</li>
<li>Stripe Gateway Scripts – Prevents the WooCommerce Stripe Gateway from loading Stripe.js on product and cart pages when the Payment Request Button (Apple Pay / Google Pay) is disabled in the Stripe settings.</li>
<li>Related Products – On every product page WooCommerce queries products sharing the same categories or tags. On large catalogues this is a slow JOIN query. Removes both the query and the “Related products” section. Up-sells and cross-sells are not affected.</li>
</ul>
<h4>Login Page</h4>
<ul>
<li>Hide Login Error Details – WordPress returns different errors for “unknown username” vs “incorrect password”, letting attackers confirm which usernames exist. Replaces all messages with a single generic response. Enabled by default.</li>
<li>Disable Email Login – WordPress 4.5+ allows login with an email address. On sites where emails are publicly visible this …</li>
</ul>

The Off Switch (formerly WP Avoid Slow)


This plugin is amazing! Just install and activate — and the site becomes noticeably faster. No complicated settings, no technical configuration, nothing confusing.



Perfect for anyone who wants speed without spending hours optimizing. Highly recommended for beginners and advanced users both!


Simple & Powerful Performance Boost

Easy does it


This plugin does remove a lot of bloat and is recommended from the team at SKT Themes.



We did test it with our free as well as premium themes and can definitely recommend it to be working and reducing a lot of bloat in WordPress to make it a faster web experience.


A plugin to make your website faster

Disable unused WordPress features and remove bloat. 91 toggles for performance, security hardening, and WooCommerce — pure PHP, no .

Andy Fragen

Pieter Bos

Due to Matt Mullenweg’s latest <a href="https://wptavern.com/wordpress-org-login-introduces-mandatory-pineapple-pizza-checkbox" rel="nofollow ugc">pineapple pizza checkbox requirement</a> to log into the WordPress.org website, I can no longer support this plugin and have decided to pass it up to anyone interested to take it over.
Hides (sidebar) ads and premium version buttons of Yoast SEO from their settings pages and your website’s dashboard (and frontend).
The first version of the Hide SEO Bloat plugin was released in April 2015 and ever since team Yoast and I have been playing a game of cat and mouse.
Since version 20.0 of Yoast SEO however, the Settings page has received a complete overhaul, which made the Hide SEO Bloat plugin almost obsolete!
Things have become much, much more trickier to remove/hide now and some things simply can no longer be hidden (believe me, I have tried).
Why are there still people using Yoast SEO one might ask? There are so many great alternatives that come without screaming ads and hiding features behind a paywall!
And the only reason that I have to keep Yoast SEO installed (on a sandbox that is) is because of the mere 10K installs where Hide SEO Bloat is running. Compare that with my popular <a href="https://wordpress.org/plugins/classic-editor-addon/" rel="ugc">Classic Editor + plugin</a>, which has more than 30,000 active installs!
For everyone to become much more productive and happier, my proposal therefore is to switch to any of the other SEO plugins, such as SEOPress, The SEO Framework, Rankmath, or any other one out there! Did you know that most SEO plugins come with easy one-click migration tools?
I support this plugin exclusively through <a href="https://github.com/senlin/so-clean-up-wp-seo/issues" rel="nofollow ugc">Github</a>. Therefore, if you have any questions, need help and/or want to make a feature request, please open an issue over at Github. You can also browse through open and closed issues to find what you are looking for and perhaps even help others.
Thanks for your understanding and cooperation.
If you like the Hide SEO Bloat plugin, please consider leaving a <a href="https://wordpress.org/support/view/plugin-reviews/so-clean-up-wp-seo?rate=5#postform" rel="ugc">review</a>. You can also help a great deal by <a href="https://translate.wordpress.org/projects/wp-plugins/so-clean-up-wp-seo" rel="nofollow ugc">translating the plugin</a> into your own language. 
Alternatively you are welcome to make a <a href="https://so-wp.com/donations" rel="nofollow ugc">donation</a>. Thanks!
<a href="https://so-wp.com/plugin/hide-seo-bloat" rel="nofollow ugc">Hide SEO Bloat</a> by SO WP.

Hide SEO Bloat

Free addon for the Yoast SEO plugin to hide the bloat it adds to the WordPress backend. See changelog for what's new in this release.

The Off Switch (formerly WP Avoid Slow) vs Hide SEO Bloat