How to Find Which Plugin Is Slowing Down Your WordPress Site with Pagemeter

When a WordPress site is slow, the hardest question is which plugin is to blame. Pagemeter answers it. Pagemeter is a free, on-demand speed test that Ultra Web Hosting publishes on WordPress.org: you install it like any plugin, click Run test, and it ranks your plugins by how much PHP time each one spends building a page, measures how much your caching is actually helping, and flags dead third-party services quietly slowing you down. This guide explains how to install it, run a test, read the report, and turn what you find into a faster site.

01. What Pagemeter Is (and What It Is Not)

Most speed tools fall into one of three camps: developer debug bars that are too heavy to leave running, paid services that will not run on shared hosting, or lab benchmarks that test a plugin on a clean site rather than on your site with your theme and content. Pagemeter is none of those. It is a simple, on-demand speed test that runs on your own site, on demand, and stores everything locally.

• It is on-demand. Pagemeter records nothing during normal visitor traffic. It only measures when you click Run test, so there is no ongoing overhead.
• It measures your real site. The test loads your actual front page, both cached (what visitors get) and uncached (a genuine cache miss), so the numbers reflect your live configuration.
• It is private. Everything is measured locally and stored in your own database. It contains no telemetry and contacts no external server.
• It is read-only and fail-safe. It never wraps or alters your plugins, and if it ever fails to start it disables itself for that request and WordPress carries on normally.

02. Diagnose First, Then Fix

The most common mistake with a slow WordPress site is fixing blind: installing three caching plugins, deleting things at random, and hoping. Pagemeter lets you work in the right order. Measure first, so you know what is actually heavy, then apply the specific fix, then measure again to confirm it worked.

1. Measure with Pagemeter. Run a test to see which plugin is heaviest and whether caching is helping.
2. Fix the specific problem. Remove or replace a heavy plugin, add a page cache, or run the Performance Toolkit to strip unused scripts and clean the database.
3. Measure again. Run another test. Because every run is saved, Pagemeter shows the before and after side by side so you can prove the change helped.

03. Installing Pagemeter

Pagemeter is in the official WordPress.org plugin directory, so it installs the same way as any other plugin, with no license key and no account.

1. In your WordPress admin, go to Plugins > Add New.
2. Search for Pagemeter (published by ultrawebhosting), click Install Now, then Activate.
3. A new Pagemeter item appears in your admin menu, with a shortcut in the toolbar.

04. Running a Test

A test is a single click. Pagemeter loads your front page a few times over a loopback request, both cached and uncached, and shows the results on one screen a moment later.

1. Open Pagemeter from the admin menu.
2. Click Run test. Pagemeter loads your home page several times: cached loads (what a real visitor gets) and uncached loads (a cache miss that forces PHP to rebuild the page).
3. Read the report that appears. Nothing is stored about your visitors; only this test you started is recorded.
4. After any change (removing a plugin, enabling caching, running the Toolkit), click Run test again to compare against the previous run.

05. Reading the Results

The report is one screen with a few panels. You do not need all of them at once; start at the top and work down.

• Runtime by plugin - your plugins ranked by how much PHP time their code spends building a page. This is where you find the heavy one.
• Caching impact - how much faster caching makes your site, measured rather than guessed.
• Page performance - the total page build time split into Load, Setup, and Render, with peak memory and database query count.
• Outbound HTTP by plugin - every external service your plugins contact while building the page, and how slow or error-prone each one is.
• Test history - your recent runs, so you can watch the numbers move as you optimize.

06. Runtime by Plugin: Finding the Heavy One

This is the headline panel for most sites. Pagemeter estimates the PHP time each plugin's code spends running during a page build and ranks them heaviest first, so the plugin dragging your site down is usually right at the top.

1. Look at the top of the Runtime by plugin list. The plugins there cost the most time on every uncached page build.
2. Ask whether each heavy plugin is worth its cost. A page builder or a full security suite may legitimately be heavy; a plugin you barely use should not be near the top.
3. Note any plugin marked low confidence. That means the code ran from a shared library more than one plugin can bundle, so the exact owner is uncertain and Pagemeter is being honest rather than guessing.

07. Caching Impact: Proving Your Cache Works

A lot of sites install a caching plugin and never confirm it is doing anything. Pagemeter's caching impact figure settles it by comparing cached and uncached loads and showing how much faster caching makes your site.

1. Read the caching headline. A healthy page cache typically makes cached loads dramatically faster than the uncached rebuild.
2. If cached and uncached times are nearly identical, your page cache is probably not working, or the page is being excluded from cache. Revisit your caching plugin's settings.
3. Enable a page cache (or fix the one you have), then run the test again and watch the gap open up.

08. Outbound HTTP: The Invisible Slowdown

One of the most common and least visible causes of a slow WordPress site is a plugin phoning a third-party service on every page load, especially when that service has gone dead and every request quietly times out. Pagemeter attributes each outbound HTTP call to the plugin that made it and shows how slow or error-prone the destination is.

1. Open the Outbound HTTP by plugin panel and look for calls that are slow or repeatedly error out.
2. Watch for a plugin contacting a service that no longer exists. A dead endpoint that times out on every page build can add seconds to your load time and tie up PHP workers.
3. Check for self / loopback calls: a plugin making HTTP requests back to your own site is slow and can exhaust your PHP worker limit.

09. What to Do With What You Find

A test result is only useful if it changes something. Here is how to act on the common findings, then confirm the fix with another test.

1. A heavy plugin you do not really need: deactivate and delete it, then re-run the test to confirm the runtime dropped.
2. A heavy plugin you do need: check its own settings for features you can turn off, or look for a lighter alternative that does the same job.
3. Weak or missing caching: install and configure a page cache, using the caching plugins guide, then re-test to see the caching impact grow.
4. General front-end bloat: install the Ultra Web Hosting Performance Toolkit and use its optimizations to strip unused scripts and styles and clean the database.
5. A dead or unwanted outbound service: remove the plugin responsible, or, if you must keep the plugin, add the endpoint to Pagemeter's domain governor (below).

10. The Optional Domain Governor

Pagemeter includes an optional domain governor: a blocklist that you configure to stop a specific outbound endpoint from slowing your site. This is useful when a plugin insists on calling a dead or unwanted service and you cannot remove the plugin itself.

1. Confirm in the Outbound HTTP panel which destination is slow or dead, and which plugin calls it.
2. Open Pagemeter's Settings and add that domain to the blocklist.
3. Run another test and check that the offending call is gone and the page build time improved, and that nothing you rely on stopped working.

11. Privacy, Overhead, and Safety

Pagemeter is deliberately conservative about what it touches and what it stores.

• No telemetry. It measures locally and stores everything in your own database. No data about your site or your plugins leaves your site.
• Zero overhead between tests. It records nothing during normal visitor traffic, so it adds no measurement cost to real page loads.
• Read-only measurement. It never wraps or alters your plugins' code; the per-plugin runtime is an estimate sampled during your test, not intrusive profiling.
• Fail-safe startup. If Pagemeter ever fails to initialize, it disables itself for that request and WordPress continues normally, so it can never take your site down.
• Clean uninstall. Deleting the plugin removes its tables and options through the standard uninstall routine, leaving nothing behind.

Quick Recap: Pagemeter in Five Steps

If you only do five things from this guide, do these:

1. Install Pagemeter from Plugins > Add New (search "Pagemeter") and activate it.
2. Click Run test and read the one-screen report.
3. Find the heavy plugin at the top of Runtime by plugin, and check Outbound HTTP for dead services.
4. Fix the specific problem: remove or replace the plugin, add caching, or run the Performance Toolkit.
5. Run the test again to prove the number dropped.

Last updated August 2026 · Browse all WordPress articles