

SlimPress turns off parts of WordPress core that your site does not use – emoji scripts, XML-RPC,
the REST API for logged-out visitors, Heartbeat, comments, feeds, author and date archives,
search, revisions, image sizes, block editor extras, dashboard clutter, automatic updates,
admin emails and more – grouped by area and explained in plain language. A built-in performance test
compares your own pages with and without SlimPress, without changing your settings.
What makes it different:
What SlimPress deliberately does not do: page caching, minification, “remove unused CSS”,
JavaScript delays, per-page script managers or CDN rewrites. Features must serve the purpose of
turning off something WordPress core does.
Nothing is switched off until you switch it off. Every switch is a runtime filter, so
deactivating SlimPress restores WordPress’s default behaviour on the next request. SlimPress never
writes to core tables or core options itself, except when you click the one-off “Delete old
revisions” button and confirm. Retention limits also have lasting effects: when you set a limit
for revisions, trash, WooCommerce scheduled actions or logs, WordPress or WooCommerce permanently deletes anything
that exceeds it. Media switches affect the image copies created during upload; switching them
off or deactivating SlimPress does not recreate missing copies or restore deleted data.