Site Cleanup Controls
Abhishek Site Cleanup Controls gives developers and site owners fine-grained control over 35+ WordPress features that are often unnecessary. Each feature has a simple on/off toggle, organised into five logical groups inside Settings -> Site Cleanup Controls. No features are enabled by default — activate only what you need. Security User Enumeration — Block ?author=N redirect attacks that expose usernames. Author Archives — Return 404 for author archive pages. XML-RPC + Pingback — Fully disable the XML-RPC endpoint and remove the X-Pingback header. Plugin and Theme Editor — Set DISALLOW_FILE_EDIT to prevent in-admin file editing. Application Passwords — Disable the Application Passwords feature. REST API — Restrict REST API access to authenticated users only. Right Click — Disable the browser context menu on the frontend. Performance Emojis — Remove all emoji scripts, styles, and DNS prefetch hints. Embed Objects — Disable WordPress oEmbed and embed scripts. Dashicons — Prevent Dashicons from loading for non-logged-in visitors. Heartbeat — Deregister the Heartbeat API script. Block Library CSS — Remove wp-block-library and global-styles stylesheets on the frontend. Version Var (?ver=) — Strip ?ver= query strings from enqueued asset URLs. PDF Thumbnails — Skip thumbnail generation for uploaded PDF files. oEmbed — Remove oEmbed discovery links and disable autoembed. Remote Block Patterns — Stop WordPress fetching patterns from api.wordpress.org. Head Cleanup Generator Meta Tag — Remove the WordPress version meta tag from head. WLW Manifest — Remove the Windows Live Writer manifest link. Really Simple Discovery (RSD) — Remove the RSD link tag. Short Link — Remove the shortlink tag and HTTP header. Adjacent Posts Links — Remove prev/next link tags from single post heads. RSS Feeds — Redirect all feed URLs to the homepage. Admin Cleanup capital_P_dangit — Remove WordPress forced capitalisation filter. Screen Options and Help Tabs — Hide Screen Options and Help dropdowns. Howdy to Welcome — Replace “Howdy,” with “Welcome,” in the admin bar. Navigation Items in Admin Bar — Remove WP logo, site name, updates, and comments. Clean Dashboard — Remove all default dashboard widgets. Privacy Tools — Hide Export/Erase Personal Data from the Tools menu. Site Health Page — Hide Site Health from the Tools menu. WP Login Logo and Favicon — Hide the WordPress logo on the login page. Admin Email Verification Prompt — Disable the admin email confirm interstitial. Empty Trash (1 week) — Shorten automatic trash-emptying from 30 days to 7 days. Content Comments — Disable comments sitewide. Post Revisions — Disable revision storage. Search — Redirect all search queries to the homepage. WordPress Features Thumbnails / Featured Images — Remove post thumbnail support. Widgets — Disable all widgets and sidebars. Navigation Menus — Remove nav menu theme support. Tags — Unregister tags from posts. Categories — Unregister categories from posts. Post Formats — Remove post format theme support. Custom Fields — Remove custom fields meta box from editor. Excerpts — Remove excerpt support from posts and pages. Trackbacks — Remove trackback support from posts. Attachment Pages — Redirect attachment URLs to the file directly. Automatic Updates — Disable automatic core, plugin, and theme updates. Self Pings — Stop WordPress pinging your own site. jQuery Migrate — Remove jQuery Migrate script on the frontend.
Remove Cookies From Static Resources
It removes cookies from the requests to static resources for modern browsers. When the browser requests a static resource such as an image, a stylesheet, or a script, it sends to the server all the cookies, and it does it at every request. If your page requests 10 scripts, then it sends 10 times the cookies. As you have probably heard, a way to solve this issue is to serve the static resources from a cookies-free subdomain. The cookies-free subdomain is a possible solution, but sometimes you have no wish to create a subdomain only for the static assets and give instructions to WordPress for fetching them from the subdomain. Moreover, why don’t we solve this issue directly at the root? Is the browser that sends cookies to the server, so let’s address this issue with the browser. This is exactly what Remove Cookies From Static Resources does. It instructs the browser to don’t send its cookies when it requests static resources. However, this solution will work only with the modern browsers that support the crossorigin attribute. The plugin simply adds crossorigin=”anonymous” to all the requested scripts, links, and images. Nothing else. This plugin will not work for old browsers. It will also not work for all those resources that are added with JavaScript, or CSS. This plugin has no settings. No additional HTTP requests, no additional database queries. It consumes practically zero. You should see an improvement in performance if yor website requests many static resources sending big data through the cookies. In all other cases you don’t need this plugin, as you would not need to serve static resources from a cookies-free domain. Removing cookies from static resources is not always the performance saver that some people think. This is totally not true in many cases. In most cases the cookies aren’t the cause of bad peformance, but the resources itselves. In those cases, it would be more effective totally removing the resources that you don’t need everywhere with Freesoul Deactivate Plugins. Of course, removing cookies from static resources improves also the privacy of your visitors. As a side note, removing cookies form static resources with this plugin will have no impact on the score given by some speed meters. The speed meters only check if the static resources are requested to free-cookies domains, but they don’t check the crossorigin paramenter. How to remove cookies from static resources Install Remove Cookies From Static Resources Done! How to understand if I really need to remove cookies from static resources Go to your website Right-click => Ispect => Console => write document.cookie.length and press enter If you see a number higher than 5000 you probably need this plugin to save bandwidth due to big data transfers through the cookies. For lower numbers you will probably not need this plugin. Does removing cookies from static resources always improve the performance? Absolutely not! It improves the performance only if yor website requests many HTTP requests due to static resources and it writes many data to the browser through the cookies. Limits This plugin doesn’t work for old browsers that don’t support the crossorigin attribute This plugin doesn’t work for all those resources that are added with JavaScript or CSS, and probably it will never work in those cases, neither with future versions of the plugin. Backend Speed Optimization Need a faster WordPress admin? I specialize in backend performance optimization. Read Backend Speed Optimization Service for more information.