If your website has gone sluggish, WordPress slowed down by plugins is one of the first suspicions worth checking. Three kinds of plugin deserve a close look: large page builders, slider plugins and heavy security suites. All three load code or trigger database queries on every page view, and all three can be measured with built-in tools and tested safely on a copy of your site. This article shows how, and which checks you can automate for good.
A WordPress site rarely becomes slow overnight. It happens bit by bit: a plugin here, a nice feature there, and two years later the homepage takes noticeably longer to load than it did at the start. I am writing about types of plugin on purpose, not individual products. Vendors change their plugins constantly, and what is heavy today may be much leaner in a year. The pattern behind it stays the same, though: a plugin is installed for one purpose that can often be met with a fraction of the weight. So for every plugin I think it is worth asking two things. Why was it installed, and is it still needed?
How do I measure whether plugins are slowing my site down?
With Google's PageSpeed Insights and the network tab of your browser, both free. Before you change anything, write down two values: the Largest Contentful Paint (LCP), which is the moment the largest visible piece of content has finished loading, and the server response time. Google recommends an LCP of 2.5 seconds or less (web.dev on Core Web Vitals, accessed 25 September 2026). Our glossary entry on LCP explains what the value measures. If yours is above that, find the cause before you uninstall anything.
The network tab (press F12, choose "Network" and reload the page) lists every file transferred when the page loads. Sort by size. If you see files named after a plugin whose function is nowhere to be seen on the page, you have a first suspect.
Why does a page builder cost loading time?
Because it brings code for its features along, often for ones you never use. Page builders such as Elementor, Divi or WPBakery are popular because you can click a page together without any programming. That is the deal. You pay with extra CSS and JavaScript that the browser has to load before the first text appears. How much that is on your site only your own measurement can show. Say several hundred kilobytes in the network tab come from a page builder: then check whether it loads code for carousels, countdown timers or pricing tables that do not appear in your layout at all.
What helps:
- Look in the builder's settings for options that load only the CSS and JavaScript actually in use. On older installations these are often still switched off. What they are called depends on the product and version.
- Build the homepage and the two or three most important pages as a lean template without the builder. Subpages that rarely change can keep it.
- If you are reworking the site anyway, you can drop the builder altogether, for example for a block theme or hand-written HTML. That is more work, but it lasts.
Removing a page builder completely is the most laborious of the three measures, because half the site often depends on it. On a tight budget, start with the next two plugin types instead. The risk is smaller there.
Does my site still need the slider plugin?
You can check that in a minute: does your homepage still show a slider at all? Big slider plugins were a status symbol for a long time, an animated slideshow across the full width at the top. When the homepage is later rebuilt, the slider often disappears from the layout. The plugin, though, easily stays active, keeps loading its scripts and keeps querying the database on every visit, without any visitor seeing a thing.
A worked example with no real case behind it: if an unused plugin loads 300 kilobytes of scripts, then on an assumed mobile connection of 10 megabits per second that is about a quarter of a second for the transfer alone, before the phone has spent any time running them.
What helps:
- In the back end under "Plugins", check whether a slider plugin is active, and on the front end whether you can see it anywhere.
- Replace the slideshow with a single, well-compressed image with a clear message. Your own analytics will show whether visitors click through several images on your site at all.
- If it has to move, the WordPress gallery or a small script is often enough instead of a large plugin.
When does a security plugin slow things down?
When it works on every page view while the visitor waits for the response. The need behind it is legitimate, nobody wants a hacked website. But some security suites check every request against the database, write every access to a log and compare IP lists. Each of those queries costs time, and the server response time is the base everything else builds on. If that is already slow, even the leanest front end does little to help.
What helps:
- Switch on real-time logging of all requests only for a targeted analysis, then switch it off again.
- Ask your host about a server-level firewall that steps in before WordPress does. It takes load off the database.
- Keep the basics in order: current WordPress version, current plugins, strong passwords, login with a second factor. That takes a lot of work off a security plugin.
How do you test this safely?
On a copy, never directly on the live site. Do not deactivate a plugin blindly on a running site, because other features sometimes depend on it, such as a form or the cookie notice. Here is how to go about it:
- Measure first and note the LCP and the server response time.
- Create a copy of the site as a test environment, often called staging. Many hosts offer this at the click of a button.
- Deactivate one plugin at a time, measure again each time and click through the site: form, menu, cookie notice.
- Only what runs cleanly goes to the live site, with a fresh backup beforehand.
That takes a few hours of care. In daily business something else is usually more urgent, and so the ballast keeps growing. That is exactly why it pays to leave the regular checking to a machine.
Automating WordPress maintenance: what works, what does not?
Automating WordPress maintenance mainly means measuring, backing up and reporting; the decision about a plugin stays with you. An automatic check tells you when the site gets slower and which plugin needs an update before a customer notices.
- Measure load time regularly: the PageSpeed Insights API measures a page's performance, returns lab data from Lighthouse and can be queried by script, for example once a week. For data from real visits, Google now recommends the CrUX API (Google for Developers, accessed 25 September 2026). If the LCP rises above your threshold, a message arrives.
- Plugin list as a report: the command-line tool WP-CLI prints every plugin with status, version and available update using
wp plugin list, as CSV or JSON if you like (WP-CLI documentation, accessed 25 September 2026). Sent out once a month as a table, it shows inactive plugins and pending updates at a glance. - Updates with a backup: since WordPress 5.5 you can switch on automatic updates for individual plugins and themes, and the WordPress documentation advises regular automatic backups (WordPress documentation, accessed 25 September 2026).
- A short automatic test after every update: open the homepage, the contact form and the imprint, and check that they respond.
Say a joinery firm, Muster Joinery, runs its site on WordPress. Every Monday a short email arrives with three figures: the homepage load time, the number of pending updates and the inactive plugins. If everything is in the green, a glance is enough. If a value falls out of line, a person decides whether and when to work on the test copy. A process like this should never delete or deactivate anything automatically.
At bytebrise we build checking processes like this for businesses in the region. The automation is new for us and does not yet run permanently at any business. Every process starts as a prototype at a fixed price from €1,500 with four weeks of testing in your business, followed by a monthly flat fee, cancellable monthly (AI for businesses). If you would rather hand over the upkeep entirely, you can rent the website from us for €490 to start and €149 a month, hosting, maintenance and updates included, cancellable at the end of any calendar month with no notice period (pricing). For questions about your WordPress site, write to us through the contact form.