Scripts Dequeuer Backend

"Scripts Dequeuer Backend" helps you to dequeue WordPress backend scripts and styles from the admin area.Backend scripts and styles can be easily dequeued (in a controlled environment) without touching any code.

scenes to be used

If you're running a website with WordPress, it's obvious that you're probably using multiple plugins for website features and functionality.Many plugins use similar (or the same) resources, these may beResource is loaded multiple timesin your WordPress admin. This can happen if the resource (JS/CSS) handle names are different.

For example, consider a scenario where two or more plugins each load the same CSS file. (For example, the fontawesome stylesheet).Or the case where two or more plugins use the same jQuery plugin with different handle names. Such files are loaded multiple times, causing additional load on the admin area.Every time you visit any admin page; these files slow down the overall page load time.

Managing page load times can be improved by removing such redundant files.Deleting such files not only improves page load times, but also helps prevent problems caused by conflicting redundant files.

The "Scripts Dequeuer Backend" plugin helps you easily dequeue such files with its simple and reliable interface. The plugin alsoTake care not to dequeue system core filesThis is required for the admin interface to work properly. In such a controlled environment, people can safelyDelist CSS and JavaScript filesAdded by third-party plugins.

How it works

If backend scripts and styles are queued using native WordPress hooks (admin_enqueue_scripts, wp_print_scripts, wp_print_styles, etc.), Scripts Dequeuer Backend can detect all such scripts/stylesheets and list them in the WordPress admin area.

From the detected scripts/stylesheets, you can select items and add them to the dequeue. After saving the changes, the selected scripts and stylesheets will be dequeued and listed separately.

If the user selects system core files for dequeuing, they are not allowed to be listed as "unqueued" files side by side.However, the plugin has a filter hook that modifies the list of files that can be allowed or disallowed to be dequeued.

This plugin is responsible for not dequeuing scripts needed by other scripts. For example, if you choose jQuery to dequeue, it won't be dequeued if any other file still needs it.This is to prevent other scripts from failing.

Why use this plugin?

This plugin is suitable forUser-friendly and reliable solutionUsed to dequeue backend scripts without touching any code.

Not only does the plugin help you dequeue your backend files, it also gives you a clear view of the files your backend uses, their origins and dependencies.If you are keen on admin area performance and optimization, you can definitely have this useful plugin in your collection. You won't regret it.Also check plugin screenshots for backend settings and functionality.

main feature

Compatible with WordPress 4.5.x and 4.6.x
Unbranded settings panel with JavaScript tabbed navigation
Displays the full list of scripts and styles detected by the backend
Detect scripts and stylesheets queued using WordPress native hooks
Dequeue scripts and stylesheets in a controlled environment
Prevent system core files from being dequeued
Ability to dequeue all scripts and stylesheets at once or based on selection
Separate portlets showing "Dequeue List", "Successfully Dequeue List" and "Unqueue List"
Each portlet displays the number of files for a better understanding of the number of files
Clean and optimize code according to WordPress coding standards
100% translation ready samples. Include the pot file
Documentation help manual with instructions for use
Works with most themes and plugins (free + premium)
Compatible with all major browsers from IE 9+
Professional support within a reasonable time

Plugin support

All support is provided through the comments section and email. For any questions related to plugins or general inquiries please feel free to email meProfile pagemessage box, or leave a comment in the project comments section. I'd be happy to respond. Thanks for browsing the plugin.