Zac Scott

Disable WordPress features for a faster, cleaner, more secure experience.
Currently these features can be disabled:
<ul>
<li>XMLRPC</li>
<li>REST API (when logged out)</li>
<li>Sitemaps (WordPress core generated)</li>
<li>RSS feeds (WordPress core generated)</li>
<li>Comments</li>
<li>Search (frontend only)</li>
<li>Author archives</li>
<li>Attachment pages</li>
<li>404 guessing </li>
<li>Emoji scripts cruft</li>
<li>srcset’s (WordPress core generated)</li>
<li>WordPress branding logos (admin bar, login page)</li>
<li>Disable select admin sidebar menus</li>
</ul>

Just Disable It


Any plugin that can disable unnecessary WordPress bloat has my approval. May I also suggest:



Remove Gutenberg block library CSS



function remove_wp_block_library_css(){
    wp_dequeue_style( 'wp-block-library' );
    wp_dequeue_style( 'wp-block-library-theme' );
    wp_dequeue_style( 'wc-blocks-style' );
} 
add_action( 'wp_enqueue_scripts', 'remove_wp_block_library_css', 100 );



Remove front-end admin bar



show_admin_bar(false);


Good work

Disable WordPress features for a faster, cleaner, more secure experience.

ggwicz

It’s way too easy to accidentally publish or update a post on WordPress.
https://vimeo.com/178698875
Post Lock prevents accidental updating or publishing of content by requiring a password to do either.
<ul>
<li>Adds a layer of protection without adding a headache: unlocking a post is a seamless experience and takes a few seconds.</li>
<li>Works on all post types (you can easily exclude or include post types with a plugin filter).</li>
<li>Simple, solid code.</li>
<li>If a post is unlocked, and two beats of the WordPress Heartbeat API happen without action (which is usally 30 seconds, 15 per beat), then the post is re-locked.</li>
<li>Numerous plugin filters make it easy to customize the plugin.</li>
</ul>

Post Lock

Post Lock prevents accidental updating or publishing of content by requiring a password to do either.

Just Disable It vs Post Lock