Remove Cookies From Static Resources


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

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.
If your page requests 10 scripts, then it sends 10 times the cookies.
As you have probably heard, a way to solve this issue is to serve the static resources from a cookies-free subdomain.
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.

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.
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.
However, this solution will work only with the modern browsers that support the crossorigin attribute.
The plugin simply adds crossorigin=”anonymous” to all the requested scripts, links, and images. Nothing else.
This plugin will not work for old browsers. It will also not work for all those resources that are added with JavaScript, or CSS.

This plugin has no settings. No additional HTTP requests, no additional database queries. It consumes practically zero.

You should see an improvement in performance if yor website requests many static resources sending big data through the cookies.
In all other cases you don’t need this plugin, as you would not need to serve static resources from a cookies-free domain.
Removing cookies from static resources is not always the performance saver that some people think. This is totally not true in many cases.
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 Freesoul Deactivate Plugins.

Of course, removing cookies from static resources improves also the privacy of your visitors.

As a side note, removing cookies form static resources with this plugin will have no impact on the score given by some speed meters.
The speed meters only check if the static resources are requested to free-cookies domains, but they don’t check the crossorigin paramenter.

How to remove cookies from static resources

  • Install Remove Cookies From Static Resources
  • Done!

How to understand if I really need to remove cookies from static resources

  • Go to your website
  • Right-click => Ispect => Console => write document.cookie.length and press enter
  • 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.

Does removing cookies from static resources always improve the performance?

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.


  • This plugin doesn’t work for old browsers that don’t support the crossorigin attribute
  • 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.

You may also be interested in


Dawout 22, 2023
Recently we started using WordPress as a headless platform, and it’s so odd that WordPress has this behaviour of applying cookies on static files.This plugin does what it says it does, Simple small and short code which works well.
Read all 1 review

Contributors & Developers

“Remove Cookies From Static Resources” is open source software. The following people have contributed to this plugin.




*Initial release