NimboCDN – Image Optimization & Image CDN | Convert WebP & AVIF
| 开发者 | mandrakecrm |
|---|---|
| 更新时间 | 2026年10月3日 02:44 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Optimize images automatically — no bulk job, no queue, nothing to click
- Resize images to the width the screen needs, with a matching
srcset - Convert to WebP and AVIF, chosen per visitor from what their browser accepts
- Serve from a global image CDN — 335 cities in more than 125 countries
- Delegate image delivery to our network, so your server can get on with your blog or shop
- Leave every original file untouched, and undo the whole thing in one click
- No account, no API key, no credit card — install, activate, done
- Install and activate. The plugin registers your site and measures your home page in the background. Nothing to configure, no key to paste.
- The plugin rewrites your image URLs. In your HTML it updates
src,srcset,<picture>sources, gallery zoom and lightbox links and CSS backgrounds, so they point at our network. Nothing else changes. - Our network does the heavy lifting. The first time a real visitor asks for an image, the network fetches your original once, resizes it, encodes it as AVIF or WebP for that browser and keeps the result in a permanent cache. From then on your server never sees that request again.
- An image is processed once, the first time a real visitor asks for it. No bulk optimization to sit through.
- Traffic is unlimited on every plan. No bandwidth charge, no per-visit charge, no overage.
- One click to undo. Deactivate the plugin and your site serves its own images again, immediately.
sizes attribute and lets the browser pick. No width larger than the one WordPress offered is ever announced, so a page can never get heavier than it was.
This is exactly what PageSpeed Insights asks for when it reports serve images in next-gen formats and properly size images.
📁 We never modify your original files
Your JPEG and PNG files stay exactly as you uploaded them: not re-compressed, not resized, not moved, not deleted. The plugin only changes the address of the image in your HTML.
🎁 Free forever on your home page
The free plan is not a trial and does not expire. It serves every image on your home page in WebP, in three sizes, from the global cache, with up to 50 new home-page images per month — the number is here, before you install, on purpose. The rest of your site keeps being served by WordPress exactly as before, and visits are never counted or charged: ten visitors or ten thousand, it stays free.
👑 What the Pro plan adds
- Your whole site: catalogue, product pages, blog and pages — not just the home page
- AVIF, about 21% lighter than WebP on the same image
- No image limit
- One fixed price, monthly or annual, with bandwidth included
data-large_image), lightboxes, category banners and CSS background heroes. A catalogue is where image weight hurts most — one product page can carry five images, a category page forty.
It works just as well on a blog, a portfolio or a company site, and is at its most useful on shared hosting, where delegating image delivery is the cheapest speed there is. WooCommerce is not required.
🧩 Works with your caching plugin, your page builder and your theme
- Caching plugins. The plugin only rewrites image attributes, and cached HTML stays valid: old delivery hostnames keep working indefinitely, by design.
- Page builders and themes. Elementor, Divi, Gutenberg blocks, galleries and sliders all produce the same HTML, which is where the plugin works.
- Existing WebP plugins. If another plugin wraps your images in a
<picture>block with its own WebP copies, NimboCDN finds the original behind it and serves that. - Lazy loading. No JavaScript is added to your pages, and your theme's lazy loading is untouched.
- If the service stops responding, the plugin stops rewriting URLs and WordPress serves its own images.
- If a single image cannot be processed, the edge redirects to your original.
- If even that fails, the
<img>element falls back to the file WordPress would have served.
安装:
- In your WordPress dashboard go to Plugins → Add New, search for NimboCDN, then click Install Now and Activate. Or upload the zip under Plugins → Add New → Upload Plugin.
- That is all. Activation registers your site and images begin being delivered from the edge.
屏幕截图:
常见问题:
Do I need an account or an API key?
No. Activation registers your site automatically and proves that you control the domain. There is nothing to sign up for and nothing to paste. Your credentials are stored in your WordPress options and travel with your site.
Does this change my original images?
No. Nothing in your media library is modified, re-compressed, moved or deleted. The plugin only changes the address of the image in your HTML, so it points to our global network instead of your server.
Is NimboCDN a content delivery network (CDN) for images?
Yes, and only for images. Your pages, your CSS and your JavaScript keep being served by your own hosting exactly as they are today; only the images are answered by our network, from a point near each visitor. It is not a WebP converter that leaves a second copy of every file on your disk: each image is prepared the first time a real visitor asks for it, and nothing new is written to your server.
What exactly does the free plan include?
Every image on your home page, delivered in WebP at 400, 800 and 1200 pixels wide, from a permanent global cache, with up to 50 new home-page images per month. The allowance renews on the 1st. Traffic and visits are unlimited. No credit card.
Is there a catch with the free plan?
No. It is not a trial and it does not expire. Visits cost us almost nothing, so we do not charge for them. The limit is on new home-page images, not on how many people see them. If the rest of your site needs optimizing too, that is what Pro is for.
Will I get a surprise bill?
No. Pro is one fixed price with bandwidth included: no charge per visit, per gigabyte, or for going over. If a payment fails there are three days of grace and then the site falls back to the free plan — your images never break.
What does the Pro plan add?
Your whole site instead of just the home page — catalogue, product pages, blog and pages — in AVIF, which is about 21% lighter than WebP on the same image, with no image limit. Monthly or annual billing.
Do I have to run a bulk optimization?
No, and there is nothing to sit through. Each image is prepared the first time a real visitor asks for it. Your home page is measured as soon as you activate, so you see a result within minutes rather than after a batch job.
How do I fix "serve images in next-gen formats" in PageSpeed Insights?
That warning means your images are being sent as JPEG or PNG to browsers that accept better formats. NimboCDN answers each request with AVIF or WebP when the browser's Accept header says it supports them, and with your original file when it does not.
How do I fix "properly size images"?
That warning means the file is bigger than the space it is displayed in. NimboCDN offers three widths — 400, 800 and 1200 pixels — with a matching sizes attribute, and lets the browser pick. It never offers a width larger than the one WordPress already offered, so a page cannot get heavier than it was.
Does it handle responsive images and srcset?
Yes. NimboCDN offers each image at 400, 800 and 1200 pixels wide and writes the matching srcset and sizes, so the browser downloads the width it is actually going to show. An image that arrived without a responsive set gets one; an image that already had one keeps it, and no width larger than the one WordPress already offered is ever announced.
Does this make my site faster?
Yes, on the part that depends on images — which is usually the biggest part. Your visitor downloads far fewer bytes and gets them from a point near them, so the images appear sooner, and how fast your page appears is what Google measures. We can tell you how many bytes your visitors stopped downloading; we cannot promise a score or a position in search, because those also depend on your hosting, your theme and everything else on the page.
Does NimboCDN help with Core Web Vitals and LCP?
Yes, and on most sites that is where the biggest gain is. Largest Contentful Paint — LCP — is how long your page takes to show its main piece of content, and on most WordPress sites that piece is an image: exactly what NimboCDN makes lighter and delivers from a point near the visitor. On one real home page, weighed file by file, it came out 88% lighter at the same quality level, and a lighter image appears sooner. What we do not put a number on is your final score, because your hosting, your theme and the rest of the page count too — but on most sites the images are what your visitor is waiting for, and that is the part we take care of.
Does it work with JPEG and PNG, and with transparency?
Yes. JPEG and PNG originals are both delivered optimized, as AVIF or WebP. Both formats keep transparency, so it is never lost; a client that accepts neither receives your original file, transparency included.
I already use an image compression plugin. Do I need to remove it?
No. A compressor works on the files in your library; NimboCDN works on what reaches the visitor. If the other plugin wraps your images in a <picture> block with its own WebP copies, NimboCDN finds your original behind that copy and serves it, so nothing is compressed twice.
Will it conflict with my caching plugin?
It should not. The plugin only rewrites image attributes, and cached HTML containing rewritten URLs stays valid — old delivery hostnames keep working indefinitely, by design. Rewriting the same HTML twice never produces nested URLs.
Does it add JavaScript or CSS to my pages?
No. On the front end the plugin changes image attributes and nothing else. The only script it loads is on its own settings screen.
What happens if I deactivate or uninstall it?
Your site immediately serves its own images again — they were never altered. Uninstalling additionally removes every option, transient and scheduled task the plugin created, leaving no rows behind. Your delivery statistics are kept by the service under your domain, so reinstalling shows them again; write to hello@nimbocdn.net to have them erased.
What if the service goes down?
Your site keeps working with its own images, exactly as before. The plugin stops rewriting on its own after three failed checks and resumes when the service answers again. NimboCDN is not a single point of failure for your site.
Does it work without WooCommerce?
Yes. WooCommerce stores are what it was built for and tested against, but it optimizes images on any WordPress site.
Do you store data about my visitors?
No. Not their IP address, not their browser, not the page they viewed. The service counts bytes and formats per site and nothing else, and the plugin makes no network calls during a page view. The full disclosure is in the External services section above.
Is it compatible with GDPR and LGPD?
The plugin collects no personal data about your visitors, so there is nothing about them to disclose or erase. The only personal data the service holds is the administrator email address used for account notices; you can change it from the settings screen and have it erased by writing to hello@nimbocdn.net. Details: https://nimbocdn.net/privacy
What do the numbers on the settings screen mean?
Every number names what it was measured on. "Your visitors downloaded X less" is the sum, over every image served in the last 30 days, of the difference between what WordPress would have sent and what NimboCDN sent. It comes from sampled edge analytics, so it is labelled estimated. "Your home page" is weighed file by file and is labelled measured.
Which languages does it come in?
English. Translations are delivered by WordPress itself as language packs from translate.wordpress.org, where our Brazilian Portuguese and Spanish translations are published. Languages without a translation fall back to English.
Where do I get support?
Through the plugin's support forum on WordPress.org, or by email at hello@nimbocdn.net. The Support link on the plugins list opens a message with your plugin version already filled in.
更新日志:
- Images uploaded in AVIF format are now delivered straight from your site instead of taking a detour through the image service, which cannot read AVIF as a source on our plan and sent every visitor back to your server. Measured on 2 October 2026: one AVIF photo on a store's home page failed on all 56 requests in a day. An AVIF original is already the lightest format, so nothing is lost; JPEG, PNG, GIF and WebP images are optimized as before.
- Sites behind Cloudflare's Bot Fight Mode now get their home page measured and its images optimized. Bot Fight Mode challenges the site's own server when it opens its home page, so the plugin could neither measure it nor tell the service which images it has, and on the free plan no image was delivered. Measured on 2 October 2026 on a store with Bot Fight Mode on. When that challenge appears, the plugin now asks the site's own server directly for the same page, as WordPress does for its own health checks. Sites without the challenge make exactly the same request as before.
- An error page is no longer read as a home page without images: the list of optimized images stays as it was, and the screen says what blocked it.
- Activating the plugin from the "More details" window of Plugins → Add New now takes you to the NimboCDN screen and connects the site. That window activates without reloading the page, and the connection waited for the twice-daily check: up to 12 hours with the plugin doing nothing. Measured on WordPress 7.1. Activating from the plugin card or the Plugins list works as before.
- While the site is not connected to the service, a notice in the admin says so and links to the NimboCDN screen. That screen now shows only the reason and the button that finishes the activation, instead of a Pause button and settings that could not do anything yet.
- When the service cannot confirm that the site is yours, the screen now says what usually causes it, a firewall, and what to allow: /wp-content/uploads/, without country blocks or bot challenges. It no longer says the images are optimized all the same, because a firewall that blocks the check blocks the images too.
- Photos whose reduced "-scaled" copy is missing from the server are now delivered from the original upload. WordPress records that copy of a large photo as the image's main file; when it has been deleted but the original is still there, as can happen after regenerating thumbnails or running an optimizer, the plugin pointed to the missing file, the CDN could not fetch it, and the photo reached visitors late through the fallback. Measured on 26 September 2026: 24 of 10,484 images on one store, each taking 3.5 to 4.2 seconds instead of under 0.2. Nothing else changes: images whose files are present, stored on another server, or missing altogether are handled exactly as before.
- Elementor galleries: photos in the Gallery widget, and in galleries built on it such as CMSMasters', are now delivered through NimboCDN, and so is the large image the lightbox opens when a visitor clicks one. These galleries do not use image tags: each photo is a background that Elementor's script paints from a
data-thumbnailaddress, and the plugin did not read it. Measured on 25 September 2026: all 6 gallery photos on one site's home page, and their lightbox links, came from its own server. A thumbnail cropped to a different shape than the original stays as it is, so the gallery layout does not change. On the free plan, gallery photos on the home page are now included.
- Sites running Elementor on WordPress 6.9 or later: images are delivered through NimboCDN in full again. Elementor switches off the page buffer that WordPress 6.9 introduced, and the plugin relied on it, so only each image's main address was rewritten: the responsive sizes that browsers actually download (
srcset), theme images, lazy-loaded images, backgrounds and lightbox links stayed on your server. Measured on 25 September 2026: 24 of 24 home page images on one site. The plugin now opens its own buffer when WordPress does not start one, never both, and leaves Elementor's editor preview as it was.
- SVG, BMP, PDF, ICO and TIFF files are no longer sent to the image network. It cannot optimize them, so each one cost your visitors a redirect back to your own server: measured on 25 September 2026, one site's SVG logo took that detour on every page view. WordPress serves them exactly as it did before you installed the plugin, and on the free plan they no longer use up the month's allowance.
- Free plan: home page images are now recognised when WebP Express replaces their addresses with its own WebP copies. Before, a site using it had none of its photos admitted. Savings are measured against the weight of that WebP copy, not the original.
- Free plan: CSS background images on the home page, such as banners and hero sections, are now included.
- WordPress older than 6.9 with WebP Express: images and backgrounds whose address it rewrote are now delivered through NimboCDN as well.
- Fixed an error that stopped the home page sync, and the measurement after activation, when another plugin filters attachment lookups (WP Offload Media, WPML and others).
- First stable release. Nothing changes in how your images are delivered: the version number catches up with a plugin that is already serving real stores, and that is now published in the WordPress.org plugin directory.
- Three answers added to the FAQ, for three questions the listing did not answer: whether NimboCDN is a content delivery network for images, how it handles responsive images and
srcset, and what it does for Core Web Vitals and LCP.
- The package downloaded from nimbocdn.net now carries the Spanish and Portuguese translations, so the settings screen is in your language the moment you activate it. Sites installed from the WordPress.org directory are unaffected: they keep getting translations as language packs, which always take precedence over any bundled file.
- The settings screen no longer runs the free and Pro plan labels into their own text in Spanish and Portuguese. The label column was a fixed width sized for the English "Free"; "Gratuito" is twice as long and touched its description with no gap. Found on 20 September 2026, rendering the screen in all three languages for the directory screenshots.
- Directory listing rewritten: what NimboCDN is and what it does, in English, Spanish and Portuguese. Nothing in the plugin's behaviour changes.
- When your domain is verified, the plugin empties your page cache so cached pages come back with the new image addresses. Measured on a store running WP Rocket on 19 September 2026: after verification, 3,393 cached pages kept the old addresses and loaded the original images. Supported: WP Rocket, LiteSpeed Cache, W3 Total Cache, WP Super Cache, WP Fastest Cache, SiteGround Speed Optimizer, Cache Enabler, Hummingbird, WP-Optimize, Comet Cache, Swift Performance, Proxy Cache Purge, Cloudflare, and the Kinsta, WP Engine, Pantheon, GoDaddy and Pressable host caches.
- Our network also keeps accepting the previous addresses for 30 days, so any cache the plugin cannot reach keeps serving optimized images.
- Works behind a hosting antibots (SiteGround and similar) with nothing for you to do. Measured on a SiteGround store on 19 September 2026: the domain could not be verified, so upgrading and billing were locked, and the free plan admitted 0 of the 72 images on the home page. With this version the domain was verified in 3 seconds and the home page images were admitted, without touching the firewall.
- Domain verification writes a blank PNG image next to the verification file and removes both when it finishes. The service reads its size through Cloudflare Images, which the antibots let through.
- Home page sync sends the HTML of your home page, read by your own server, so the service can check the images even when its own visit is blocked.
- The settings screen no longer asks you to allow a user agent in your firewall.
- The settings screen loads its stylesheet through the WordPress style queue instead of printing a
<style>tag in the page. - On WordPress 6.9 and later, image rewriting uses the template output buffer that WordPress itself opens and closes; the plugin no longer opens a buffer of its own. On earlier versions the buffer is closed explicitly at the end of the request.
- Translations are no longer bundled in the package; WordPress delivers them as language packs from translate.wordpress.org.
- Nothing assumes
/wp-content/uploadsany more: the verification file falls back tocontent_url(), and CSS background images are matched against the uploads path WordPress reports, so sites with a relocated content directory are covered.
- Crawlers no longer cost a new image copy. A client that accepts neither AVIF nor WebP now receives your original file, or a JPEG or PNG copy made earlier, instead of triggering a new JPEG. Measured on two stores from 10 to 14 September 2026: 71% of new copies were being made only for crawlers such as Amazonbot, AhrefsBot, bingbot and Googlebot-Image. Visitors whose browser accepts AVIF or WebP see no change.
- The plugin's author link now points to its author's page. No change to how images are rewritten.
- Release prepared for the WordPress.org plugin directory. The distributed package now carries no code comments at all, and every note WordPress requires — translator hints and licence attributions — is in English.
- Checkout, invoice and billing-portal redirects now go through
wp_safe_redirect()with an explicit allow-list of destinations (our own service and the payment provider's hosted pages). A URL that does not qualify sends you back to the settings screen with a notice instead of anywhere else. - The "we could not charge your card" notice registers its dismiss handler through the WordPress script queue instead of printing a
<script>tag. - The
Tested up tofield is declared only in the readme, as the directory asks. - Code style aligned with the WordPress Coding Standards throughout; no behaviour change.
- Category banners and other full-width backgrounds are no longer blurry on desktop. A background image has no responsive set, so it was capped at 1200 px and stretched to fill a 1920 px screen. Backgrounds, the lightbox link and the product zoom now go up to 2048 px — the size WordPress already keeps on disk — when the original photo is that big.
- Nothing else grows. Catalogue grids, thumbnails and every responsive set stay at 400/800/1200: the larger step is only used where the visitor clicked or scrolled to see the picture big, never as a candidate the browser could pick for a small slot.
- If another plugin on your site already makes WebP copies and wraps your photos in a
<picture>block, NimboCDN was doing nothing at all, and saying otherwise. It now finds the original photo behind their copy and serves that instead. Measured on a test page: 107 KB down to 39 KB. - When the original cannot be found on disk, the whole block is left alone. Nothing is deleted, and the other plugin keeps working exactly as it did.
- Sites that serve different photos on phones and on desktop are untouched: a
<picture>block that switches by screen size is left exactly as it was.
- Thumbnails now download at the size they are shown: lazy-loaded images that declare their dimensions let the browser pick the candidate for the space they occupy — the same rule WordPress applies to its own images since 6.7. Measured on a 28-image grid: 3.2 MB → 0.4 MB on desktop.
- The responsive set added in 0.5.1 now declares
sizes, so a desktop browser no longer downloads a larger file than before.
- Photos that carried no responsive set now get one, so a phone downloads a phone-sized file instead of the one your desktop gets.
- The annual plan: Pro can be paid yearly for the price of ten months, with a one-click switch from monthly and a scheduled switch back.
- Prices in the panel now come from the service instead of being written into the plugin, so what you are shown is what you are charged.
- Fixed: a site that had not proved its domain yet was told "could not reach the billing service", which was false.
- The "Our global network" card times the response with the browser's network clock, over three measurements, and says so when it cannot reach the service.
- The plugin reports the site language on every panel sync, so service emails arrive in the language your WordPress uses.
- Spanish translation.
- A "Product emails" preference under Your account, which you can turn off from the panel or from the foot of any email. Payment notices are separate and always arrive.
- The settings screen in English, Spanish and Portuguese.
- The settings screen wears the brand and follows the admin colour scheme you picked in your profile.
- Activation works behind a firewall: the domain proof can be read from a static file in
uploads, and a site that cannot be verified is still optimized on the free plan. - CSS backgrounds, product gallery zoom and lightbox links are delivered optimized too.
- Settings screen rebuilt around what visitors actually downloaded, measured per request at the edge.
- Brazilian Portuguese translation.
- Initial release.