You added one plugin. A booking form, perhaps, or a reviews widget, a popup builder, a social feed. It looked great on the demo. Since then the site has felt heavier: pages hesitate before appearing, and a speed test that used to be green is now amber. You suspect the new plugin, but you also need what it does, and you are not certain it is really the cause.
The good part about a website slow after installing a plugin is that you have a prime suspect and a date. What is left is to confirm the suspicion properly, find out what the plugin is actually loading, and then decide whether to tame it, replace it or ask its developer for help.
First, confirm it was the plugin
It is easy to blame the newest thing on the site. Sometimes that is right; sometimes the plugin arrived the same week as an update, a new image on the home page or a change at the host. Before acting, check three things.
- Was it the only change? Look at what else was updated or added in the same few days. If several things changed, you need to separate them.
- Do you have a before number? An earlier speed test result, a monitoring graph or even a note of how long the home page took. Without one, you are comparing against memory.
- Is it every page or some? A plugin used only on the contact page that slows down every page is telling you it loads its files site-wide.
Website slow after installing a plugin? Test off, on, off
The reliable way to know is to measure the site with the plugin active and inactive, under the same conditions, a few times each. Do this on a staging copy if you have one, so visitors never see a missing feature; our post on setting up a WordPress staging site explains how. If you must test on the live site, choose a quiet hour and keep the plugin off for as short a time as possible.
- Take a backup.
- Pick two pages: one where the plugin’s feature appears, and one where it does not.
- With the plugin active, clear all caches, load each page once to warm the cache, then run a speed test three times. Note the middle result for server response time, Largest Contentful Paint, total page size and number of requests.
- Deactivate the plugin. Clear the caches again, warm them, and repeat the same tests.
- Reactivate the plugin and test once more, to make sure the numbers return to where they were.
If the numbers move clearly with the plugin, you have your answer. If they barely move, the plugin is probably innocent and the cause is elsewhere; the triage in why a website is slow and how to narrow it down is the better next step. And if you suspect a different plugin altogether, finding which plugin is slowing the site covers the wider search.
What is the plugin actually loading?
Knowing that a new plugin slowed the site is half the answer. Knowing how it does so tells you what you can do about it. Plugins add cost in a few distinct ways, and each one maps to a section of our hub on how to make a website load faster, where the fixes are covered in depth.
Files in the visitor’s browser
Open the browser’s developer tools, go to the Network panel and reload a page. In the filter box, type the plugin’s folder name as it appears in /wp-content/plugins/. Everything that plugin adds to the page will be listed: stylesheets, scripts, fonts, icons, images. Do this on a page where the feature is not used. If the list is not empty, the plugin is loading its files everywhere, even where nobody needs them.
Calls to outside servers
Clear the filter and look at the domain column. Reviews widgets, social feeds, maps, chat tools and some form plugins fetch content or scripts from their own servers. Those requests are only as fast as the provider’s server, and some of them block the page while they load.
Work on your server
If the server response time rose rather than the page size, the plugin is doing work while the page is being built: extra database queries, a call to an outside service before the page can be sent, or heavy processing. This shows up most on pages that cannot be cached and in the dashboard. A developer tool such as Query Monitor can show how many queries a plugin adds and how long they take.
Background activity
Some plugins add scheduled tasks, frequent background requests from the page, or log every visit to the database. None of this is visible on the page, but it all competes for the same server.
Keeping the plugin but cutting its cost
If you need what the plugin does, look for ways to reduce what it loads before you think about replacing it.
- Read its settings carefully. Many plugins have options to turn off features you do not use, disable their own fonts or icon sets, or stop loading on every page. Some include a “performance” or “advanced” tab.
- Load it only where it is used. Plugins such as Perfmatters and Asset CleanUp let you switch off a plugin’s scripts and styles on pages where it is not needed. The idea is explained in cutting JavaScript the page never uses; test carefully, because switching off the wrong file can break a feature.
- Replace live embeds with lighter options. A social feed can often be swapped for a link or a static image. A reviews widget may offer a lighter display mode or a static summary.
- Check its cache compatibility. Some plugins prevent pages from being cached at all, for example by setting a cookie or adding unique content for each visitor. If pages stopped being cached after the install, that is the problem rather than the files.
When replacing it makes more sense
Sometimes the plugin is simply heavy for what it does. Before choosing an alternative, write down what you actually need from it, which is usually less than the feature list. Then judge candidates on:
- Whether they load their files only on pages that use them.
- Whether they depend on an outside service for every page view.
- How recently they were updated and whether the support forum has unanswered performance complaints.
- Whether your theme or an existing plugin already does the job. Forms, galleries and popups are often duplicated by page builders.
Test the replacement the same way you tested the original, with before and after numbers. A lighter plugin on paper is not always lighter on your site.
The number of plugins matters less than what each one does; that argument is made properly in whether too many plugins slow WordPress down.
Asking the plugin’s developer
Developers of well-maintained plugins often respond well to a clear, specific report. A vague “your plugin is slow” gets nowhere. A useful report includes:
- The plugin version, WordPress version and PHP version.
- Your before and after numbers from the clean test, and the pages you tested.
- Which files the plugin loads on pages where its feature is not used.
- Any outside requests it makes and how long they take.
- Whether you are using a caching plugin, and which.
Sometimes the answer is a setting you missed. Sometimes it is a known issue with a fix coming. Either way, you learn more than you would by guessing.
Mistakes to avoid
- Deactivating the plugin once, seeing a quicker page, and concluding without repeating the test.
- Forgetting to clear caches between tests, so you compare a cached page with an uncached one.
- Installing a second plugin to “optimise” the first instead of looking at its settings.
- Leaving the plugin deactivated but not deleted, with its scheduled tasks and data still in place.
- Assuming a well-known plugin cannot be the cause.
Frequently asked questions
Does deactivating a plugin remove everything it added?
Not always. Deactivating stops its code running, but its settings, database tables and sometimes scheduled tasks can remain. Deleting it from the Plugins screen removes the files and, for many plugins, their data, though some leave entries behind on purpose so you can reinstall later. Check the plugin’s documentation for an uninstall or cleanup option.
Why is the site still slow after I removed the plugin?
The cache may still hold pages built with the plugin, so clear every cache and test again. The plugin may have left code in the theme, settings that load on every page, or scheduled tasks. Or the plugin was not the cause, and something else changed at the same time.
Can a plugin I only use in the dashboard slow down the public site?
It can, though it is less likely. Some admin tools still load on every page, add database queries to each request or run scheduled tasks that use server resources. Check the Network panel for its files on public pages and watch the server response time with it active and inactive.
Is it safe to stop a plugin’s scripts loading on some pages?
Usually, if you are careful. Turn off its files only on pages where its feature does not appear, then test those pages fully, including menus, forms and anything interactive. Write each change down, page by page, so that undoing it later takes minutes rather than guesswork.
Trimming what a plugin loads, and auditing the outside scripts it brings, is part of what our speed optimisation service does. We share the findings and a fix list first, apply changes with your approval, and re-test afterwards so the effect is clear.
Next in this series: WordPress Slow When Logged In but Fast for Visitors?
