How to Find Which WordPress Plugin Is Slowing Your Site Down
You pushed a Core Web Vitals score of 87. Three weeks later it dropped to 34. Nobody touched the theme. No new plugins were added. What happened?
Most WordPress slowdowns are stealth. A plugin starts making API calls in the background. A hook begins firing on every page load. A database table grows without a cleanup routine. These things creep in gradually, and by the time you notice, you have no idea what changed.
The Anatomy of a Slow WordPress Site
WordPress performance problems fall into three buckets. First, frontend bloat: large images, render-blocking JavaScript, excessive CSS. Second, server-side drag: slow database queries, PHP execution bottlenecks, memory limits being hit. Third, plugin interference: hooks that fire on every request, API calls that block page rendering, cron jobs that monopolize CPU.
The third bucket is the most insidious. Plugins that worked fine for months suddenly start causing problems when they update. A developer changes the default behavior of a hook. An external API goes down and your plugin’s retry logic kicks in synchronously. These issues are nearly impossible to find without visibility into what’s actually running on each page load.
What SitePulse Shows You That Other Tools Don’t
Most WordPress monitoring tools tell you your site is slow. SitePulse tells you why. When you activate it, the plugin profiles every hook that fires on a request, every database query that runs, and every external API call that gets made. You see a breakdown per plugin, per hook, per load time contribution.
Here is what that looks like in practice. You have six plugins that claim to improve performance. SitePulse runs for 24 hours and shows you that Plugin X is responsible for 62% of your total hook execution time. Plugin X was updated 11 days ago. The update log mentions a change to how it handles admin-ajax.php calls. That is your culprit.
You did not have to disable plugins one by one. You did not have to stare at a waterfall chart and guess. You had a number and a timeline, and the problem surfaced automatically.
How to Find the Slow Plugin in 15 Minutes
Start with SitePulse’s plugin hook timeline. This shows you every hook each plugin registers and how long each one takes to execute. Sort by execution time, not by alphabetical order. The plugin at the top of that list is where your attention goes first.
Check the plugin’s update history. WordPress.org logs show you what changed in each version. Look for updates that touched admin-ajax, cron scheduling, or database queries. These are the three most common sources of regression.
If the plugin was updated recently and your performance dropped around the same date, open a support thread and link to the specific changelog entry. Most developers respond quickly when you give them a precise window and a specific symptom.
Database Bloat Is Often the Real Culprit
Plugin hook profiling gets attention because it is visible and dramatic. Database bloat is quieter but equally damaging. As your site ages, options tables accumulate orphaned entries. Post revisions pile up. Transients expire but do not get cleaned up. A site with moderate traffic can accumulate 500MB of bloat in under a year.
SitePulse’s database analysis flags tables that have grown without bounds and queries that are running more often than they should. Run the cleanup check once a month. It takes two minutes and typically recovers 200MB to 600MB of storage, depending on how long your site has been running.
Set Up Alerts, Not Just Dashboards
A dashboard that you check manually is not monitoring. It is archaeology. Real monitoring fires an alert when something crosses a threshold. SitePulse lets you set alert rules: TTFB above 2 seconds, error rate above 1%, hook execution time above 800ms on any single plugin.
When one of those rules triggers, you get an email or a Slack message. You fix the problem while it is affecting five visitors, not fifty. That is the difference between a maintenance task and a firefight.
Most WordPress sites do not need a full-time DevOps team. They need a tool that tells them what broke before their visitors tell them. That is what SitePulse was built for.
If you are on a plan that includes AI diagnostics, SitePulse will suggest which plugin is most likely responsible for a given slowdown and surface the specific hook that is causing it. You still decide what to do. The tool does the archaeology.
The Bottom Line
WordPress performance is not a set-it-and-forget-it problem. Plugins update, databases grow, traffic patterns shift. You need visibility that updates with your site, not a snapshot from the day you launched. SitePulse runs continuously and flags issues before they become user-facing problems. Free tier covers 1 site. Paid plans start at $9.99 for 6 sites.