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. Limits 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. Backend Speed Optimization Need a faster WordPress admin? I specialize in backend performance optimization. Read Backend Speed Optimization Service for more information.
WP-Sweep
WP-Sweep finds the rows WordPress leaves behind and removes them. Revisions of posts you edited years ago, meta belonging to a post that was deleted, terms attached to nothing, term relationships pointing at posts that no longer exist, expired transients: none of it is visible anywhere in wp-admin, and all of it is in your database. It uses the proper WordPress delete functions wherever they can reach the row, rather than running raw delete queries, so the hooks other plugins rely on still fire. Only the rows the API refuses to touch — orphaned meta whose object ID is 0 — are deleted directly. Features Revisions Auto drafts Deleted posts Unapproved comments Spammed comments Deleted comments Orphaned post meta Orphaned comment meta Orphaned user meta Orphaned term meta Orphaned term relationships Unused terms Duplicated post meta Duplicated comment meta Duplicated user meta Duplicated term meta Transient options oEmbed caches in post meta Optimizes database tables Delete functions used wp_delete_post_revision() wp_delete_post() wp_delete_comment() delete_post_meta() delete_comment_meta() delete_user_meta() delete_term_meta() wp_remove_object_terms() wp_delete_term() delete_transient() delete_site_transient() Known incompatibilities These plugins keep data in places WP-Sweep reads as orphaned. Protect their meta keys with the filters under Usage before sweeping. Custom Fonts Elementor Popup Builder MailPress Meta Slider Polylang Slider Revolution Viba Portfolio WPML Donations I spent most of my free time creating, updating, maintaining and supporting these plugins, if you really love my plugins and could spare me a couple of bucks, I will really appreciate it. If not feel free to use it without any obligations. Usage Every sweep is irreversible, so back your database up first. The screen lists every sweep with a short description of what it removes, how many items that is, and what proportion of the table they are. Tick the ones you want and use the Sweep bulk action, or use each row’s Sweep and Details buttons one at a time. Nothing on the screen needs JavaScript: the buttons are ordinary links and the bulk action is an ordinary form. There is no settings screen. The one thing worth tuning — how many items Details lists, 500 by default — is the wp_sweep_limit_details filter. The cap exists because the whole sample is held in memory and written into the page. WP-CLI wp sweep --all wp sweep revisions wp sweep revisions auto_drafts deleted_posts REST API All three routes need the activate_plugins capability. GET /wp-json/sweep/v1/count/ GET /wp-json/sweep/v1/details/ DELETE /wp-json/sweep/v1/sweep/ Item names revisions, `auto_drafts`, `deleted_posts`, `unapproved_comments`, `spam_comments`, `deleted_comments`, `transient_options`, `orphan_postmeta`, `orphan_commentmeta`, `orphan_usermeta`, `orphan_termmeta`, `orphan_term_relationships`, `unused_terms`, `duplicated_postmeta`, `duplicated_commentmeta`, `duplicated_usermeta`, `duplicated_termmeta`, `optimize_database`, `oembed_postmeta`. Filters wp_sweep_postmeta_whitelist (array) — post meta keys that must never be deleted, by the orphaned or the duplicated post meta sweep. * matches any run of characters. Default: empty. wp_sweep_commentmeta_whitelist (array) — the same, for comment meta. wp_sweep_usermeta_whitelist (array) — the same, for user meta. wp_sweep_termmeta_whitelist (array) — the same, for term meta. wp_sweep_excluded_taxonomies (array) — taxonomies left out of the orphaned term relationships sweep. Default: array( 'link_category' ). wp_sweep_excluded_termids (array) — term IDs left out of the unused terms sweep. Default: each taxonomy’s default term, plus any term that is the parent of another. wp_sweep_limit_details (int) — how many items a Details list shows. Default: 500. wp_sweep_defer_counts (bool) — whether the Sweep screen renders first and fetches its counts afterwards, one at a time. Return false to compute every count with the page, as versions before 2.0.1 always did. Default: true. wp_sweep_capability (string $capability, string $context) — the capability required. $context is one of sweep, ajax or rest. wp_sweep_total_count (int $count, string $name) — the total number of rows a sweep’s percentage is measured against. wp_sweep_count (int $count, string $name) — how many items a sweep would remove. wp_sweep_details (array $details, string $name) — the sample list shown by Details. wp_sweep_sweep (string $message, string $name) — the message reported after a sweep has run. Actions wp_sweep_admin_post_sweep, `wp_sweep_admin_comment_sweep`, `wp_sweep_admin_user_sweep`, `wp_sweep_admin_term_sweep`, `wp_sweep_admin_option_sweep` and `wp_sweep_admin_database_sweep` all fire below the sweep table, in that order. Protect specific post meta keys from being swept: add_filter( 'wp_sweep_postmeta_whitelist', function ( $meta_keys ) { $meta_keys[] = '_my_plugin_setting'; $meta_keys[] = '_acme_*'; return $meta_keys; } ); Exclude an additional taxonomy from the orphaned term relationships sweep: add_filter( 'wp_sweep_excluded_taxonomies', function ( $taxonomies ) { $taxonomies[] = 'product_type'; return $taxonomies; } );
