Hakeemify Debloater
Most optimisation plugins ask you to trust a switch. Debloater asks you to read a finding. It scans your site, records what it found, and shows you each change it could make: what the change does, what it might break, how confident it is, and how to get back. Nothing is applied until you confirm it,
About this tool.
Most optimisation plugins ask you to trust a switch. Debloater asks you to read a finding.
It scans your site, records what it found, and shows you each change it could make: what the change does, what it might break, how confident it is, and how to get back. Nothing is applied until you confirm it, and every apply takes a recovery point first. After applying, it checks your site, and if the check finds a page broken it puts everything back.
What it does
Scans, and records facts. Which core features are loading, how many revisions and expired transients you have, what your autoloaded options weigh, which of your plugins do the same job, and what your admin shows. Each scan is stored with the facts it read.
Explains every finding. Each finding names the facts it came from, so you can disagree with it and leave it alone.
Scores each area separately, and says what it covers. The Debloat Score is three scores out of 100 — Database, Admin and Assets — and they are not averaged into one number. None is a speed measurement. Each counts what your site has that Debloater offers to change, and not what WordPress does out of the box: a fresh install scores 100. Something it reports but cannot change for you, such as two plugins doing the same job or XML-RPC being on, is listed as a finding and costs nothing. Each finding that costs points says how many. When everything left in an area is behind deleting data — which Fix Safe Issues never does — the score says what is left and offers to review deleting it. If any check in an area could not run, that area is shown as not scored, with the reason, rather than as clean.
Reads your admin as you. Findings about the admin come from a request the scan makes to your dashboard, signed in as the person scanning, and describe what that person sees. The dashboard has 30 seconds to answer a scan started from the dashboard, and 120 seconds from WP-CLI. From WP-CLI, run the scan with –user=; without it, the admin is not read and the scan says so.
Plans before it acts. You get a preview: every change, its risk level, what it touches, and the recovery point that will be taken. The same scan and the same profile always produce the same plan.
Takes a recovery point first. Before anything changes, the current configuration is captured. Before rows are deleted, the rows themselves are captured, and the deletion does not run unless that capture completed.
Verifies, then rolls back if it has to. After applying, Debloater requests your front page, a post, your dashboard and your REST API, and if one of them fails, it puts everything back and tells you what failed. It also requests the login page, and warns rather than rolling back if that looks wrong. When you apply from the dashboard, it also asks a fresh request whether each change loaded, and puts everything back if one did not. From WP-CLI the same checks run as the administrator you name with --user=<an administrator> , and a failure puts everything back there too. Without --user , or on a site that cannot make requests to itself, these checks cannot run; the change stays, and Debloater reports which checks could not run.
