Hey r/Wordpress,

A couple of weeks ago I shared SlimPress here, and the feedback from this community was awesome. Today I’m back with another tool I built out of my own day-to-day frustration: Cron Monitor.

Every time a scheduled post missed its publish window, a backup silently failed, or a site slowed down because of background tasks, I ran into the same wall. Existing cron plugins are great at showing you what is scheduled to run, but unless you pay for a Pro tier or an external SaaS, you're mostly flying blind on what actually happened when the job executed.

I wanted full execution visibility without paywalls, so I built it myself. Just like my last plugin, it is 100% free. There is no pro tier, no locked features, no nag banners, and zero telemetry.

What it covers

• Execution History & Timing: See exactly when jobs ran, how long they took, and any recorded errors—including fatal crashes and timeouts.
• Instant Failure Alerts: Get notified via Email, Slack, or Discord when a background job crashes, runs late, or stops running altogether.
• Plugin & Theme Ownership: Automatically maps cryptic cron hooks back to the specific plugin or theme that owns them by inspecting their observed callbacks.
• Orphan & Duplicate Cleanup: Identifies duplicate events and leftover cron jobs from long-deleted plugins based on what actually happens when they run, with a safe preview before you remove anything.
• Full Job Management: Add, edit, run on-demand, pause, resume, or bulk-delete events and custom schedules straight from the admin.
• Cron Health & WooCommerce Support: Tracks cron jobs that are progressively getting slower, flags server config issues blocking wp-cron.php, and automatically logs failed Action Scheduler tasks (huge for debugging WooCommerce).
• Developer Tools: Includes native WP-CLI commands, CSV exports, and a REST API for connecting your own external monitoring tools.

How it behaves on your site

• Zero bloat or phoning home: All logs stay strictly inside your local WordPress database. The only outbound requests are the optional failure alerts if you explicitly configure an email address or Slack/Discord webhook.
• Works out of the box: Once activated, just head to Tools → Cron Monitor. Duplicate detection, ownership mapping, and health checks work immediately, and your execution history starts building as your background jobs run.
  

Quick transparency note on AI: All the core logic and architecture were written by hand - AI was only used to help with UI mockups, class scaffolding/boilerplate, testing, documentation, and a final code review pass.

👉 Cron Monitor on WordPress.org

I’d love to get some feedback from others maintaining WordPress sites—especially if there are specific edge cases, WP-CLI flags, or webhook payloads that would make debugging background tasks easier for your workflow!

Hey everyone,

I’ve built a free WordPress plugin that lets webadmins disable unused WordPress features like emoji scripts, XML-RPC, Heartbeat and a million other features. But building it is the part I’m comfortable with - getting it in front of people is where I could use some advice.

For anyone who’s launched a plugin, what actually helped you get your first users?

• Tutorials targeting specific problems?
• Sharing in WordPress communities?
• Reaching out to bloggers or YouTubers?
• Improving your WordPress.org listing?

I’d especially appreciate firsthand experiences: what was worth the effort, and what turned out to be a waste of time?

Hey r/Wordpress,

Like most of you, I found that every site I build ends up needing the exact same functions.php snippets: removing emoji scripts, killing XML-RPC, taming Heartbeat, dropping unnecessary image sizes, and hiding dashboard widgets.

I finally got tired of copying and pasting the same boilerplate, so I packaged it all into a single plugin called SlimPress.

It gives you 108 toggle switches across 13 categories. It is 100% free. There is no pro tier, no upsells, no admin nag banners, and zero telemetry.

What it covers

• Front-end: Emoji scripts, generator tags, RSD/shortlink/REST links in <head>, global styles, core block CSS, Dashicons, and jQuery Migrate for visitors.
• APIs & Core: XML-RPC, REST API for logged-out visitors (with a namespace allowlist), per-location Heartbeat control, WP-Cron on page load, oEmbed, and application passwords.
• Comments & Feeds: Granular comment control (site-wide or per post type), pingbacks, Gravatar, feeds, author/date/attachment pages, and search.
• Revisions & Media: Revision limits, autosave intervals, disabling the auto-generated 1536/2048px image copies, and managing custom image sizes.
• Admin: Dashboard widgets, admin bar items, block editor extras, admin emails, auto-updates, and file editing.
• WooCommerce (if active): Disables shop assets on non-shop pages, order attribution scripts, WC Analytics, the Marketing hub, marketplace suggestions, and controls Action Scheduler data retention.

Why I built this instead of using existing "disable bloat" plugins

Most optimization plugins overpromise or break things silently. I wanted a developer-first approach:

• Honest Impact Badges: Every switch tells you exactly what it does, and more importantly, what it might break. It will even warn you if an active plugin relies on the off. If a toggle is just for tidying up the codeand won't actually speed up the site, the badge honestly says "None – cleanup only."
• Built-in A/B Performance Testing: It loads your own pages with and without SlimPress's features in the same run. If the performance difference is too small to be meanins "within noise" instead of making up a fakescore. It also breaks down CSS/JS on each page by plugin, theme, and core to show exactly what can be removed.
• Safe Defaults & Presets: Activating the plugin changes absolutely nothing – every switch starts off. You can apply presets (Blog, Brochure, Headless, WooCommerce) ld change before applying them.
• Zero Footprint: It adds no CSS, JS, or markup to your public pages. Everything is done with runtime filters, so if you deactivate it, WordPress goes back to normal on g is permanently written to your core tables oroptions.

What it deliberately doesn't do

There is no caching, minification, "remove unuseiting. I also didn't include switches for thingsthat actively make sites slower or harder to cache (like removing ?ver= strings or disabling native lazy loading), even though other plugins sell those as "optimizations."

It requires WP 6.8+ and PHP 7.4+. WooCommerce is completely optional.

👉 SlimPress on the WordPress.org repo

I'd really appreciate some feedback from this coested in hearing if there are any switches youfeel are missing, or if you run into any edge cases where the "what might break" warning was inaccurate for your specific stack.