Preview a Row and Open the JavaScript Assets Interface
Use the JS Assets Preview button to open a live preview of the page using the plugin configuration shown in the current row and, at the same time, display the interface for managing plugin JavaScript files.
This feature is useful when you want to keep a plugin active for functionality, but you want to prevent some of its scripts from loading on that specific page.
What This Button Does
This button opens the page represented by the current row and applies:
- the plugin state currently shown in that row
- the selected theme for that row, when applicable
- the FDP assets interface in JS mode
So the button combines two things:
- it previews the page using the row configuration currently visible in FDP
- it opens the interface for unloading or repositioning JavaScript files
This is the JavaScript equivalent of the CSS assets preview workflow.

Where to Find It
Open the Action Buttons bar for the row.
Inside the row actions, look for the preview button with the code icon and the JS label.
This button is available only in Freesoul Deactivate Plugins PRO.
Its purpose is to help you work on the scripts of the remaining active plugins while previewing the page with the current row setup.
When to Use It
Use this button when:
- the plugin setup of the row is already close to what you want
- one or more plugins still need to remain active
- but you want to remove or move some JavaScript files for that page
Typical use cases include:
- plugins loading JS on pages where it is not needed
- sliders, galleries, builders, forms, or analytics plugins loading scripts unnecessarily
- scripts causing layout shifts or render delays
- scripts that could be safely moved from head to footer
- testing whether a page still works without certain plugin scripts
What the Preview Is Based On
The preview uses the current row state shown in FDP.
That means it reflects:
- the plugin checkboxes currently visible in the row
- the target page of that row
- the currently selected theme, where applicable
You do not need to save the row first.
This makes the feature ideal for testing temporary row configurations before saving anything permanently.
How to Open the JS Assets Interface
- Open the FDP page containing the row you want to optimize.
- Adjust the row plugin checkboxes as needed.
- Open the row action bar.
- Click the JS Assets Preview button.
The page opens in a new tab with the assets interface in JS mode.

What You Will See in the JS Assets Interface
The page opens with the PRO assets panel attached to the preview.
In the interface you can typically find:
- a Save button
- a Global View button
- a Close button
- a Reset button
- a switch between CSS and JS
- filters such as:
- All
- Core
- Plugins
- Theme
- a plugin filter dropdown
- a Preview control inside the panel
- a list of the loaded JavaScript assets
When opened through this button, the panel starts in JS mode.
What the JS List Shows
For each script, the interface can show:
- the script handle
- its source type:
- core
- plugin
- theme
- whether it currently appears active in the preview context
- whether it is loaded in the head or footer
- the file path
- the file inspection link
- the action controls for that script
This helps you understand not only which scripts are loaded, but also where they come from and where they are printed.
What You Can Do with a Script
In the JavaScript assets interface, each script can be managed with several controls.
The main actions are:
- Unload the script
- Activate the script again
- Move the script to head
- Move the script to footer
- Reset the script position
- Edit options
This makes the JavaScript assets interface more flexible than the CSS one, because for scripts you can often choose between unloading them completely or just changing their load position.
Unloading a Script
If a script is not needed on the current page, you can disable it.
This is useful when:
- the script belongs to an active plugin that must stay enabled
- but the script itself is unnecessary on that page
A typical workflow is:
- identify the suspicious script
- disable it
- check whether the page still works
- save the asset settings only if everything remains functional
Be careful with scripts tied to interactive features such as forms, navigation, search, checkout, sliders, tabs, modals, or AJAX.
Moving a Script to Head or Footer
For JavaScript assets, FDP also lets you change loading position.
You can use the controls to:
- move a script to the head
- move a script to the footer
- reset the script to its original position
This is useful when a script is still needed, but its current loading position is not ideal.
For example, moving a non-critical script to the footer may reduce render-blocking behavior.
Reset Position Settings
If you moved a script and want to restore its original placement, use the Reset position settings control for that script.
This returns the script to the original head/footer position detected by FDP.
Edit Options for a Script
Each script also includes an Edit options panel.
This panel allows more specific targeting, such as:
- This page
- Unload by custom URL
- Post Types
- Archives
- Terms
This means you are not limited to the current page preview only. You can build reusable unloading rules for the selected script.

Custom URL Rules
Inside the edit panel you can define custom URL-based rules for unloading the script.
If you want to unload an asset everywhere, the interface supports the star symbol:
*
This makes the assets interface suitable both for page-specific testing and for broader rule creation.
Global View
The Global View button opens a broader view of the saved rules for the selected asset type.
When you are working in JS mode, this helps you inspect the larger picture of JavaScript unload rules across the site.
Use it when you want to review existing decisions before making more changes.
Reset
The Reset button resets settings related to the current asset type.
In this workflow, that means resetting JavaScript-related asset settings.
Use it when you want to discard the current JS asset adjustments and start over.
Save
The Save button in the assets panel saves the JavaScript asset settings.
Important distinction:
- the row preview is based on the current FDP row state
- the JS assets interface manages JavaScript asset rules
Saving the assets panel does not mean the row itself is automatically saved in FDP.
So if you are testing both the row setup and the script-level setup, remember that they are separate layers.
Navigation Inside the Preview
While the JS assets interface is open, internal links are handled so the assets mode remains active as you navigate.
This helps you continue working in the same optimization session without immediately losing the JS panel.
Suggested Workflow
- configure the FDP row
- open the JS Assets Preview
- inspect the loaded scripts
- unload one script or move it to the footer
- check whether the page still works correctly
- repeat carefully as needed
- save the asset settings
- return to FDP and save the row if the full configuration is correct
Best Practices
- First optimize at the plugin level in FDP.
- Then use the JS assets interface to optimize remaining scripts.
- Disable one script at a time when testing.
- If a script is necessary, consider moving it instead of unloading it.
- Be especially careful with scripts required for interactivity, forms, checkout, login, navigation, and AJAX.
- Save only after verifying that the page still behaves correctly.
Typical Use Cases
- a plugin must remain active but its script is unnecessary on the page
- a script is needed, but it can safely move to the footer
- you want finer control after row-level optimization
- a page feels heavy because of frontend JavaScript
- you want to reduce unused JS without disabling the whole plugin
Summary
The JS Assets Preview button opens a preview of the page using the plugin configuration shown in the current row and provides the interface for unloading or repositioning plugin JavaScript files.
Use it to:
- preview the page with the current row settings
- inspect loaded JavaScript assets
- unload unnecessary plugin scripts
- move scripts between head and footer
- save script-level optimization rules
It is the natural next step after row-level plugin optimization when you want deeper control over frontend JavaScript loading.
