Find which plugins are slowing your WordPress site — measured on your own server, explained in plain English.
Features
What each plugin costs on the front end and in wp-admin, as honest measured ranges
Every script and stylesheet on your pages, attributed to the plugin that ships it, with render-blocking flags
Autoloaded-option weight and probable owners, a common hidden slowdown
Low, Medium and High impact badges, sorted worst first, no jargon
Scan before updating plugins and again after, and see exactly what changed
Plugins that cannot be separated are measured together and labelled honestly
Says "inconclusive" when the server is too noisy, instead of inventing a number
`wp speed-doctor scan` for scripted or scheduled diagnosis
Everything runs on your own server; nothing is sent anywhere
Guides
Step-by-step guides from the team that builds it. All guides
Site health
How to tell server time from front-end weight, measure what each plugin actually costs with leave-one-out profiling, read the results honestly, and prove the fix with a before-and-after scan.
Site health
Why sites get slower one update at a time, how to keep a measured baseline, scan after every update, and get an email that names the change responsible, only once a second scan confirms it.
Speed Doctor can now check your site on a schedule and after updates, keep a year of results, and email you when a second scan confirms a slowdown; it is off until you turn it on in Settings. • Automatic scans: weekly or daily at a quiet hour you pick, plus a follow-up scan 10 minutes after a plugin, theme or WordPress update (installing something new does not start one). A run of updates shares one scan. They run through WP-Cron in small steps, time the front end, and never install the measurement loader by themselves. • Slowdown emails: when an automatic scan finds a page or a plugin slower than the scans before it, a second scan an hour later has to agree before anything is sent.
