Jose Mortellaro

<p>It removes cookies from the requests to static resources for modern browsers.</p>
<p>When the browser requests a static resource such as an image, a stylesheet, or a script, it sends to the server all the cookies, and it does it at every request.<br />
If your page requests 10 scripts, then it sends 10 times the cookies.<br />
As you have probably heard, a way to solve this issue is to serve the static resources from a cookies-free subdomain.<br />
The cookies-free subdomain is a possible solution, but sometimes you have no wish to create a subdomain only for the static assets and give instructions to WordPress for fetching them from the subdomain.</p>
<p>Moreover, why don’t we solve this issue directly at the root? Is the browser that sends cookies to the server, so let’s address this issue with the browser.<br />
This is exactly what Remove Cookies From Static Resources does. It instructs the browser to don’t send its cookies when it requests static resources.<br />
However, this solution will work only with the modern browsers that support the crossorigin attribute.<br />
The plugin simply adds crossorigin=”anonymous” to all the requested scripts, links, and images. Nothing else.<br />
This plugin will not work for old browsers. It will also not work for all those resources that are added with JavaScript, or CSS.</p>
<p>This plugin has no settings. No additional HTTP requests, no additional database queries. It consumes practically zero.</p>
<p>You should see an improvement in performance if yor website requests many static resources sending big data through the cookies.<br />
In all other cases you don’t need this plugin, as you would not need to serve static resources from a cookies-free domain.<br />
Removing cookies from static resources is not always the performance saver that some people think. This is totally not true in many cases.<br />
In most cases the cookies aren’t the cause of bad peformance, but the resources itselves. In those cases, it would be more effective totally removing the resources that you don’t need everywhere with <a href="https://wordpress.org/plugins/freesoul-deactivate-plugins/" rel="ugc">Freesoul Deactivate Plugins</a>.</p>
<p>Of course, removing cookies from static resources improves also the privacy of your visitors.</p>
<p>As a side note, removing cookies form static resources with this plugin will have no impact on the score given by some speed meters.<br />
The speed meters only check if the static resources are requested to free-cookies domains, but they don’t check the crossorigin paramenter.</p>
<h3><a href="https://josemortellaro.com/remove-cookies-from-static-resources/" rel="nofollow ugc">How to remove cookies from static resources</a></h3>
<ul>
<li>Install Remove Cookies From Static Resources</li>
<li>Done!</li>
</ul>
<h3>How to understand if I really need to remove cookies from static resources</h3>
<ul>
<li>Go to your website</li>
<li>Right-click => Ispect => Console => write document.cookie.length and press enter</li>
<li>If you see a number higher than 5000 you probably need this plugin to save bandwidth due to big data transfers through the cookies. For lower numbers you will probably not need this plugin.</li>
</ul>
<h3>Does removing cookies from static resources always improve the performance?</h3>
<p>Absolutely not! It improves the performance only if yor website requests many HTTP requests due to static resources and it writes many data to the browser through the cookies.</p>
<h3>Limits</h3>
<ul>
<li>This plugin doesn’t work for old browsers that don’t support the crossorigin attribute</li>
<li>This plugin doesn’t work for all those resources that are added with JavaScript or CSS, and probably it will never work in those cases, neither with future versions of the plugin.</li>
</ul>
<h3>Backend Speed Optimization</h3>
<p>Need a faster WordPress admin? I specialize in backend performance optimization.<br />
Read <a href="https://josemortellaro.com/backend-speed-optimization/" rel="nofollow ugc">Backend Speed Optimization Service</a> for more information.</p>


Remove Cookies From Static Resources

It removes cookies from the requests to static resources for the modern browsers.

<p>Editor Cleanup For Oxygen is an add-on of <a href="https://wordpress.org/plugins/freesoul-deactivate-plugins/" rel="ugc">Freesoul Deactivate Plugins</a> to <strong>clean up the editor of <a href="https://oxygenbuilder.com/" rel="nofollow ugc">Oxygen</a></strong>.</p>
<p>It will not only clean up the assets added by other plugins, their PHP code will not run either.</p>
<p>The editor of Oxygen will load faster and without conflicts with other plugins.</p>
<p>Both Freesoul Deactivate Plugins and Oxygen must be active, in another case this plugin will not run.</p>
<h3>How to clean up the Oxygen editor</h3>
<ul>
<li>Install and activate Freesoul Deactivate Plugins if not active yet</li>
<li>Install and activate Oxygen if not active yet</li>
<li>Install and activate Editor Cleanup For Oxygen</li>
<li>Go to Oxygen => Editor CLeanup</li>
<li>Click on “Outer editor cleanup” to disable plugins that the outer editor does’t need (usually no plugin needed)</li>
<li>Click on “Inner editor cleanup” to disable plugins that the inner editor does’t need (the inner editor is like the page on frontend, but loaded inside the Oxygen editor)</li>
<li>Click on “Editor loading cleanup” to disable the plugins that are called during the loading of the editor (usually no plugin needed, disabling plugins here can solve conflicts with other plugins)</li>
</ul>
<h3>Similar add-ons to clean up</h3>
<ul>
<li><a href="https://wordpress.org/plugins/editor-cleanup-for-elementor/" rel="ugc">Editor Cleanup For Elementor</a></li>
<li><a href="https://wordpress.org/plugins/editor-cleanup-for-avada/" rel="ugc">Editor Cleanup For Avada</a></li>
<li><a href="https://wordpress.org/plugins/editor-cleanup-for-wpbakery/" rel="ugc">Editor Cleanup For WPBakery</a></li>
<li><a href="https://wordpress.org/plugins/editor-cleanup-for-divi-builder/" rel="ugc">Editor Cleanup For Divi Builder</a></li>
<li><a href="https://wordpress.org/plugins/editor-cleanup-for-flatsome/" rel="ugc">Editor Cleanup For Flatsome</a></li>
</ul>
<h3>Backend Speed Optimization</h3>
<p>Get a faster dashboard with deep plugin analysis and backend optimizations.<br />
Read <a href="https://josemortellaro.com/backend-speed-optimization/" rel="nofollow ugc">Backend Speed Optimization Service</a> for more information.</p>
<h3>Help</h3>
<p>For any question or if something doesn’t work, don’t hesitate to open a thread on the <a href="https://wordpress.org/support/plugin/editor-cleanup-for-oxygen/" rel="ugc">support forum</a>.</p>
<p>Read also <a href="https://freesoul-deactivate-plugins.com/editor-cleanup-for-oxygen/" rel="nofollow ugc">How to clean up the Oxygen editor</a> for more details.</p>
<p>Please, before posting enable the debugging in wp-config.php. Need a step-by-step guide? Read <a href="https://freesoul-deactivate-plugins.com/how-to-enable-debugging-in-wordpress-a-step-by-step-guide/" rel="nofollow ugc">this detailed tutorial</a> on <a href="https://freesoul-deactivate-plugins.com/how-to-enable-debugging-in-wordpress-a-step-by-step-guide/" rel="nofollow ugc">how to enable debugging in WordPress</a> to learn more.</p>


Editor Cleanup For Oxygen: FDP add-on to cleanup the Oxygen editor

FDP add-on to cleanup Oxygen in the backend. Your Oxygen backend will be faster and without conflicts with other plugins.

Remove Cookies From Static Resources vs Editor Cleanup For Oxygen: FDP add-on to cleanup the Oxygen editor