It replaces all assets with versions available on jsDelivr. No options, nothing to configure, just works.<\/p>\n\n
The code needs to be openly hosted on NPM, Github or wordpress.org.<\/p>\n\n
This plugin adds a little a invisible button in the admin bar on the top right, left of \"Howdy, {Name}\". It turns dark red on hover. You can click that and see the assets loaded from jsDelivr. I hope you appreciate how I made it so its not annoying or distracting.<\/p>\n\n
The plugin serves your assets securely. It takes two hashes of your assets (and caches them). One sha256 hash for the jsDelivr API to check if the file is hosted there, another sha384 hash that is put on the This plugin serves JavaScript and CSS assets from the jsDelivr CDN (cdn.jsdelivr.net, no affiliation) instead of your own server. It also uses the jsDelivr hash lookup API (data.jsdelivr.com) to find whether a file is available on the CDN.<\/p>\n\n To detect CDN files, the plugin sends a SHA-256 hash of each local asset's content to the jsDelivr lookup API. Asset requests to the CDN and the hash lookup are made from your server when a page is loaded; your visitors' browsers then load the assets directly from cdn.jsdelivr.net. jsDelivr may log standard request metadata such as IP addresses and requested URLs (see their policies below).<\/p>\n\n The CDN and API are provided by Volentio JSD Limited (jsDelivr). See their Terms of Use<\/a> and Privacy Policy<\/a>.<\/p>\n\n It took me a lot of time to come up with this plugin and I had many iterations over various different approaches how to do this until I came up with this working solution that also does not need much code. I know the official plugin was abandoned years ago and I looked at complicated bloated code and did not even feel like learning what its doing and never looked at it again and started from scratch.<\/p>\n\n Please check out my commercial plugin and level up your video embeds with ARVE Pro<\/a> or Donate here<\/a><\/p>\n\n\nintegrity<\/code> attribute of every asset to make 100% sure that the exact same file you have on your server is the served by the CDN! In case this would ever not be the case the files gets rejected client side.<\/p>\n\nExternal services<\/h3>\n\n
Your donation would be appreciated<\/h3>\n\n
2026-08-20 1.3.8<\/h3>\n\n
\n
2026-08-11 1.3.7<\/h3>\n\n
\n
2025-06-12 1.3.6<\/h3>\n\n
\n
<link href='https:\/\/cdn.jsdelivr.net' crossorigin='anonymous' rel='preconnect' \/><\/code> to the header to improve performance.<\/li>\n<\/ul>\n\n2025-10-22 1.3.5<\/h3>\n\n
\n
2025-10-12 1.3.3<\/h3>\n\n
\n
2025-10-11 1.3.0<\/h3>\n\n
\n
<link rel=\"modulepreload\"<\/code><\/li>\n<\/ul>\n\n2025-09-16 1.2.6<\/h3>\n\n
\n
2025-03-22 1.2.4<\/h3>\n\n
\n
2024-12-21 1.2.3<\/h3>\n\n
\n
2024-12-06 1.2.1<\/h3>\n\n
\n
integrity<\/code> attribute to be wrong, plugin files would get blocked.<\/li>\n<\/ul>\n\n2024-12-04 1.2.0<\/h3>\n\n
\n
get_headers<\/code> with wp_safe_remote_head<\/code>. WP coding standards and more efficient.<\/li>\n2024-05-14 1.1.0<\/h3>\n\n
\n
2019-09-07 1.0.0<\/h3>\n\n
\n
wp_remote_get<\/code> referrer by default would send your site URL (I really do not like that)<\/li>\n<\/ul>\n\n2019-08-31 0.9.4<\/h3>\n\n
\n
2018-09-23 0.9.2<\/h3>\n\n
\n
2018-09-01 0.9.1<\/h3>\n\n
\n