Slow WordPress Plugins: How to Find Them With 5 Free Checks (2026)

Slow WordPress plugins rarely announce themselves. Your site just gets a little heavier with every install until PageSpeed Insights turns orange. This guide shows the five free checks we use to find slow WordPress plugins, with real numbers from the 33 plugins we tested on our own site.

What makes slow WordPress plugins slow

A plugin can slow your site in three different places, and each needs a different check:

• In the browser: extra CSS and JavaScript files that every visitor downloads. In our test, MetForm added 18 files (922 KB) to pages without a form.
• On the server: extra PHP work and memory on every request. MailPoet added 27.9 MB of memory and 40 database tables.
• In the admin: heavy dashboards, notices and background tasks. These do not hurt visitors, but they slow you down every day.

Most speed tools only show the first kind of slow plugin. That is why a plugin can look fine in PageSpeed Insights and still make your hosting struggle.

Signs you have slow WordPress plugins

Before you start measuring, look for the symptoms. Any of these is a good reason to check your plugins:

• Your site is fast when logged out but slow in the dashboard or when logged in.
• Time to first byte is high even on cached pages, or your host warns you about CPU or memory limits.
• PageSpeed Insights lists CSS or JavaScript files from plugins you do not use on that page.
• The site got slower right after you installed or updated a plugin.
• Your database or backups have grown much faster than your content.

Each of these points to a different kind of slow plugin, which is why the five methods below check different things.

Method 1: Test plugins one at a time in WordPress Playground

WordPress Playground runs a full WordPress site in your browser, so you can install a plugin without touching your live site. This is how we tested all 33 plugins:

1. Open Playground and install the same theme you use on your site.
2. Load a normal page and note what it loads (Method 2) and how long it takes.
3. Install and activate one plugin, then load the same page again.
4. Write down the difference, deactivate the plugin and move on to the next one.

Playground is slower than real hosting, so treat timings as relative. File counts, memory and table counts are reliable, because they do not depend on the speed of the machine.

Method 2: Check the Network tab on a page that does not use the plugin

The fastest check takes two minutes. Open a page that does not use the plugin, for example a blog post when you are testing a form plugin:

1. Open the page in a private window so you see what visitors see.
2. Open your browser developer tools and go to the Network tab.
3. Reload the page and filter by CSS and JS.
4. Look for file names that contain the plugin’s folder name.

This check catches the most common kind of slow plugin. Anything you find there is weight every visitor pays for. In our tests, Contact Form 7 loaded 5 files (44.3 KB) on every page, Essential Addons loaded 5 files (170.4 KB) on pages not built with Elementor and ThirstyAffiliates loaded 3 files (102.2 KB).

Method 3: Measure memory and queries with Query Monitor

Query Monitor is a free developer plugin that shows memory use, database queries and PHP errors for every page you load while logged in. Use it on a staging copy:

1. Install Query Monitor and load a page. Note the peak memory and the number of queries in the admin bar.
2. Activate the plugin you want to test and load the same page again.
3. Open the Queries by Component panel to see how many queries came from that plugin.

Query Monitor finds slow WordPress plugins that the Network tab cannot see, because their cost is on the server. Our memory measurements followed the same idea. The biggest increases were MailPoet (27.9 MB), Kadence Blocks (19.8 MB), WPForms Lite (16.7 MB) and MetForm (11.6 MB). At the other end, Bit Form and the MailerLite and ActiveCampaign form plugins added 0.1 MB.

Method 4: Compare page generation time before and after

The fourth check is time. We rendered the home page five times before and after each plugin and took the median. These are Playground numbers, so the absolute values are not what you will see on real hosting, but the differences between plugins are telling:

A slow plugin shows up here even when it loads no files. Kadence Blocks added the most time in this test (+210 ms) on a page that used none of its blocks. GenerateBlocks, FluentSMTP and Formidable added 6 ms or less. On real hosting all of these numbers would be smaller, but the order would usually be similar.

Method 5: Run PageSpeed Insights on a staging copy

PageSpeed Insights shows how a page feels to real visitors, so it confirms whether slow WordPress plugins actually hurt your users. Use it last, after you know which plugins load files or use a lot of memory:

1. Test the same page before and after a plugin change, three times each, and use the median.
2. Compare Largest Contentful Paint and Total Blocking Time, not just the overall score.
3. Clear your caching plugin between runs, or you will measure the cache instead of the plugin.

What to do when you find slow WordPress plugins

Finding a slow plugin does not always mean deleting it, and most slow WordPress plugins can be tamed. Work through these options in order:

1. Check the plugin settings first. Many plugins can turn off modules or widgets you do not use, which reduces what they load.
2. Limit where it loads. Some plugins, such as Contact Form 7, only need their files on one page. A small snippet or a script manager can unload them elsewhere.
3. Replace it with a lighter alternative. Our list of lightweight WordPress plugins compares 33 plugins across nine categories.
4. Remove it. If you have not used a plugin in months, deactivate it and delete it.

A quick checklist before you install a new plugin

The easiest slow plugin to deal with is the one you never install. Before adding a plugin to a live site, run through this list:

1. Check the last update date and the “tested up to” version on WordPress.org.
2. Read the one-star reviews for mentions of speed, memory or conflicts.
3. Install it on a staging copy or in Playground first and run Method 2 on a page that does not use it.
4. Look at the settings for module switches, so you can turn off what you do not need.
5. Decide in advance what would make you remove it again.

This takes ten minutes and saves hours of hunting for slow WordPress plugins later. It is the same routine we follow before any plugin goes on WPGlory.

The slowest plugins in our own tests

For reference, these were the plugins with the biggest cost in each area across all 33 tests:

• Most files for visitors: MetForm (922 KB), CartFlows (276.1 KB), Essential Addons (170.4 KB), ThirstyAffiliates (102.2 KB).
• Most memory: MailPoet (27.9 MB), Kadence Blocks (19.8 MB), WPForms Lite (16.7 MB).
• Most database tables: MailPoet (40), FluentCRM (17), Bit Form, Ninja Forms and PrettyLinks (11 each).
• Most render time added in Playground: Kadence Blocks (+210 ms), MailPoet (+89 ms), WPForms Lite (+88 ms).

None of these is automatically a slow plugin for your site. Each one also does a lot, and several are good choices when you need their features. The point is to install them because you need them, not by default, and to check what they cost after you do.

FAQ

Modasser Jasim

Meet Modasser, an industry specialist, website designer, and developer with professional experience. With over 5 years of expertise in crafting interactive websites and providing intelligent business solutions, Modasser has established a solid reputation for excellence in the industry.

I install every plugin on a clean test site and publish the numbers.

More postsHow we testwpglory.com