Non-developers can start by removing plugins they no longer use, then check whether plugins they still need load resources only on pages that require them. If the platform and tools support it, they can disable unnecessary scripts or CSS on individual pages and test the site’s front-end functionality. A plugin that is no longer used anywhere on the site needs a different approach from one that is unnecessary only on certain pages. Code with an unclear purpose should be assessed by a developer, not removed simply to improve a speed test score.
Review what you use: plugins and third-party services
In a 2023 article, Semrush recommends regularly reviewing third-party code, including scripts, tracking pixels, and plugins. Some of this code still serves a purpose and should not automatically be treated as a burden. Non-developers can begin with the features and services they recognize:
- Tools the site no longer uses: Remove the corresponding plugin or code after confirming it is no longer needed.
- Analytics or advertising tracking still in use: Confirm its purpose first rather than deleting it simply because it appears in a performance report.
- Unfamiliar service names: Flag them for investigation and ask the site’s maintainer to identify them.
Where to remove code also depends on the platform. The Semrush article lists possible approaches such as removing code from the CMS, uninstalling a WordPress plugin, or removing tags from a tag management tool. Not everything can be handled through the plugin list. Yoast’s maintenance guidance also recommends backing up the site and testing changes before updating the CMS, as well as checking for updates to plugins and themes you intend to keep using.
For plugins you keep, consider disabling resources page by page
In a Local Search Forum discussion, Yan Gilbert shares his experience with Asset CleanUp. When editing a page, users can see the scripts and CSS it loads and disable them individually. They still need to understand what those resources do and test whether the front end works properly.
He cites Contact Form 7 as an example: In his setup, its resources loaded even on pages without an embedded form, so they could be disabled on individual pages. This is an experience shared in a discussion; it does not mean every version currently behaves this way. Before trying this approach, check what your own pages actually load and then decide whether to make changes.
For WooCommerce, Yan Gilbert only suggests that a similar situation might occur. He also warns that some templates integrate its functionality, so extra care is needed when disabling scripts. Do not assume that every store can safely disable the same resources.
Unsure what a resource does? Take the report to a developer
In a 2023 BigCommerce case study, Screaming Frog used the browser’s Coverage report to examine used and unused portions of JavaScript. When the author encountered anything they could not interpret, they took the report to a developer rather than deleting the code outright.
Non-developers can also start by listing problem pages, potentially unnecessary resources, and features they need to keep, then ask a developer to assess them. A 2024 Semrush article likewise recommends consulting a developer before making advanced changes to reduce requests, to avoid harming site functionality and the user experience.
Avoiding unnecessary plugin code: perspectives from across the web
Does having fewer plugins always make a website faster?
Not necessarily. What matters is whether the plugins are needed, how well they are built, and how they actually affect the site. Relying too heavily on plugins can slow a site down, so prioritize essential, higher-quality plugins and consider whether they can handle the expected traffic. Do not disable useful functionality just to reduce the plugin count; the actual impact depends on the site and the plugins involved.
How can you check how many resources a page loads?
Open the page in Chrome, right-click and select “Inspect,” then switch to the Network tab. Reload the page to see the request list and total count. Removing unnecessary elements or plugins may help reduce requests, but the list alone cannot tell you whether a resource is safe to remove. For advanced changes, seek a developer's help to avoid harming functionality or the user experience.
Should you remove plugins if your speed test score is disappointing?
Do not decide based on the score alone. Start with PageSpeed Insights to check loading performance, then assess whether any plugins or code are unnecessary. Speed issues may also require other measures, such as file compression. Although third-party code can slow a page down, some of it is still needed for analytics or advertising tracking. Use scores to help diagnose problems rather than pursuing a perfect score at all costs.
References
- Ecommerce on website impact local seolocalsearchforum.com — Source used in the article above.
- The Ultimate Guide to Casino SEO: How to Rank Higher, Fasterwww.semrush.com · 2023-12-27T13:16:00Z — Discusses: Should you remove plugins if your speed test score is disappointing?
- 【WordPress SEO 外掛設定】 Yoast SEO 教學安裝、操作技巧welly.tw · 2022-03-07T10:26:57.133Z — Discusses: Does having fewer plugins always make a website faster?
- Got an old website? Update it and refresh your SEOyoast.com · 2026-07-06T12:46:52+00:00 — Source used in the article above.
- So You’ve Found JavaScript Issues in Your Site Crawl. What Now?www.screamingfrog.co.uk · 2023-09-01T10:57:38+00:00 — Source used in the article above.
- PageSpeed是什麼?會影響SEO嗎?網站測速工具這裡看!welly.tw · 2024-10-07T10:41:12.274Z — Discusses: Should you remove plugins if your speed test score is disappointing?
- Drupal vs. WordPress: Which Should You Use?www.semrush.com · 2021-07-27T20:14:00Z — Discusses: Does having fewer plugins always make a website faster?
- Google PageSpeed Insights: What It Is & How to Boost Your Scorewww.semrush.com · 2023-07-10T09:40:00Z — Discusses: Should you remove plugins if your speed test score is disappointing?
- How to Improve Website Performance: 9 Optimization Tipswww.semrush.com · 2024-11-07T11:09:00Z — Discusses: How can you check how many resources a page loads?
