PressHangar Site Checkup

No. PressHangar Site Checkup is read-only. The only things it ever writes are its own two settings (phcheckup_settings, which check to run, and phcheckup_last_scan, the cached result of your last checkup). It never calls WordPress's plugin/theme deactivation or deletion functions, never edits a post, and never touches any other plugin's data.

No. There is no background job, no cron event, and no code that runs on a normal front-end page view. Every check only runs when you click "Run checkup" (or, separately, "Measure front-page load time") on the PressHangar Site Checkup admin screen, and each run is a single, bounded request.

It matches each active plugin's folder name against a small dictionary of well-known plugins (Yoast SEO, Rank Math, WP Super Cache, Wordfence, UpdraftPlus, Contact Form 7, and more) to work out what job it does. For anything not in that dictionary, it falls back to a keyword guess based on the plugin's name and description, clearly noted as a lower-confidence guess. If your active plugins include more than one of Musubiemu's own PressHangar-suite plugins in the same category (for example SEOPilot and CitePilot), they're never flagged against each other — they're built to work together.

Three cheap, safe-to-read signals: your active plugin count, the total size of "autoload" options (data WordPress loads into memory on every page, regardless of whether that page needs it), and the disk space used by each active plugin's folder. None of these are a substitute for a real profiling tool (Query Monitor and similar developer tools measure actual request time); they're meant as an approachable starting point for a non-developer site owner.

Yes. Each of the three checks (overlapping plugins, heaviness hints, unused items) has its own on/off toggle on the PressHangar Site Checkup screen. All three are on by default, since none of them change anything about your site.