At ScoreApps we offer ourpartnersa networkWordPressso that they can easily create websites under our platform. Although WordPress allows you to add thousands of extensions, this freedom has a cost:each plugin adds code, requests and queries to the databaseso that the sum of extensions can slow down the entire network. Several studies show that each active plugin increases HTTP requests and database queries, which lengthens loading time. The longer it takes to upload a page, the worse the user experience andworse position in search engines; Google has incorporated load speed as a key factor in its algorithm and points out that slow pages lose organic traffic.
In addition, the infrastructure shares the same server resources across all sites. A poorly optimized or incompatible plugin can consume memory and CPU, or create code conflicts, which will affect not only one site but the entire network. For this reason,we do not allow each client to install any plugin. Our plugin policy exists forensure performance, security and SEOof all sites hosted on ScoreApps.
Low speed = worse positioning.When a site is loaded, the server processes the code of all active plugins. Excess plugins generates additional requests and styles thatslow down time to first byte and response time. Google has confirmed that a slow site not only bores visitors, but alsoreduces their positioning in results.
User experience and conversions.Users leave pages that take more than three seconds to load; slow-loading stores lose sales. The impact of performance not only affects SEO, it also affects conversions.
Quality rather than quantity.There is a myth that "the more plugins, the more functionalities without disadvantages". In reality,add plugins without assessing their impact slows down the siteand a slow site damages SEO and business. Choosing high-quality plugins and eliminating redundant improves performance.
In WordPress, the same set of files serves many sites. This adds complexity.
Conflicts and errors.Some plugins work in individual installations butare not supported in network environments. They can create conflicts with other plugins or kernel and cause errors that affect the entire network.
Outdated or low-quality plugins.Extensions without frequent updates or without support generate security holes and performance issues.
Duplication of functionalities.Using multiple plugins for the same function (e.g. multiple visual builders or SEO) creates redundancy and conflicts and increases server load.
CPU, memory, database and cache are common resources. A heavy plugin on one site can affect everyone. That is why it is necessaryOverall control the code running on the networkand dimension the infrastructure well.
To protect the performance and positioning of all sites, we have adopted a policy that classifies plugins into three groups and describes the application process:
We will draw up a list of tested and approved extensions. A list that includes essential functionalities (integration with CRM, forms, SEO, analytics, etc.) that have passed a compatibility and performance test. These plugins can be activated per site when you need it.
You can request the installation of a new plugin using a form (e.g.Plugin request formwhich we have created). In the application you must indicate:
Name and URL of the plugin.
Brief justification for the use case: what problem does it solve? Why does it not use any of the options available in the catalogue?
Our technical team will evaluate the request on the basis of:
CompatibilityWe check whether the plugin is ready for the network and whether your code complies with good practices.
Performance:We check whether you add heavy queries, external scripts, cron jobs or other processes that can increase the burden.
Updates and support:We value whether you have regular updates and active support.
License:We verify that the license allows its use in network environment and marks clear costs.
Sometimes we propose lighter alternatives or native integrations. We only install and activate a plugin when the evaluation passes.
For the protection of the system we reject the following categories:
Pluginsbackupand cloning, as copies are made at server level.
Plugins that allowedit filesor manage directories from the WordPress dashboard (security risk).
Pluginscacheor optimization of images that overlap with our infrastructure (CDN, server cache).
Outdated plugins, without valid licenses or downloaded from unofficial sites (risk of malicious code).
Plugins that duplicate existing functionalities in the catalogue (e.g. installers of visual builders other than those supported).
This policy is not intended to limit you; it seeksensure a solid basis for your sites. By keeping the number of plugins under control and selecting only those that offer quality and compatibility, we achieve:
Fast and reliable sites.An optimized code reduces response time and improves Core Web Vitals score, which favours SEO.
Better positioning and conversions.Fast pages retain users and scale better on Google, increasing traffic and sales.
Safety and stability.We avoid vulnerabilities and conflicts by preventing poorly coded or incompatible plugins.
Cost savings.By centralizing management and avoiding duplication, we reduce licences and maintenance.
Less is more.Install only the strictly necessary plugins and periodically check the list to disable and delete those you do not use. Off plugins can leave tables and data unnecessary.
Choose quality plugins.It prefers extensions with good ratings, active support and frequent updates.
Avoid duplicating functions.Do not install two plugins that do the same; it causes conflicts and extra consumption.
Keep your sites up to date.The WordPress core, plugins and themes must be kept up to date to avoid vulnerabilities.
Why can't I install plugins on my own?
Our infrastructure shares resources; an inadequate plugin can affect everyone. We centralize the facility to protect your site and that of others.
What if I need a function that is not in the catalogue?
You can request it using the form. We will evaluate your case and look for the best solution, whether through an approved plugin, custom code or existing tools.
How long does the approval process take?
The process can take up to 7 working days as system updates are performed on a weekly basis.
What happens if my plugin is not approved?
We will propose alternatives to you or try to integrate that functionality differently. Our goal is to respond to your need without compromising performance or SEO.
ScoreApps' plugin policy is a measure ofprevention and quality. Limiting and reviewing the extensions we use allows us to keep sites fast, safe and well positioned. We appreciate your understanding and collaboration: by respecting these guidelines, all members of the network benefit from a stable platform that helps grow their businesses.