Your CDN host may bill twice for auto-optimized images

Hosting with built-in CDN and automatic image optimization can improve page speed without stitching together separate services.

Table of Contents

Choose by image source, not CDN branding

The best image-delivery setup depends on where your images start. It also depends on how often they change.

A bundled content delivery network is complete only when it resizes images, converts formats, caches results, and shows usage limits clearly.

Choose integrated hosting when the site’s image workflow is simple. The workflow should also be tightly tied to the publishing platform.

WordPress libraries need fewer moving parts

Managed WordPress hosting is usually the lowest-maintenance choice for editorial sites. These sites mainly need automatic image optimization, WebP conversion, responsive image sizing, and reliable CDN delivery.

Ecommerce catalogs need transformation control

Ecommerce stores need predictable crop rules for product grids and zoom images. They also need controls for frequent catalog updates.

A portfolio can favor low monthly cost and easy WebP or AVIF delivery. SaaS products and headless CMS projects often need more control.

Headless apps need flexible image URLs

Apps with user uploads often benefit from a dedicated image CDN. They need an image optimization API, signed URLs, and on-demand variants.

In those cases, a separate image service can justify another vendor relationship. It handles changing image sources and transformation volume better than many hosting add-ons.

Count all six costs before calling it included

Bundled CDN hosting often costs less for a stable site. It can cost more at scale when transforms, storage, delivery, or cache misses have separate limits.

“Unlimited image optimization” does not mean unlimited image delivery, storage, transformations, or cache invalidations.

The six charges worth checking

Price image delivery as six separate lines. Check the hosting plan, original-image storage, transformed-image storage, and cache retention.

Also check transformation requests, CDN request fees, and image bandwidth costs. These costs can sit outside the main hosting price.

Check whether cache misses create billable origin requests. A low cache-hit ratio can raise latency and origin spend.

For example, an ecommerce site may upload one 2 MB product photo. It may then generate six widths, two crops, and WebP and AVIF variants.

The original upload is cheap. Repeated first-time transforms and global delivery can become the larger cost.

Ask whether transforms are charged once per unique URL, per request, or through a monthly quota. Model traffic at current volume and three times current volume.

This shows whether “included” image optimization stays economical as your catalog grows. It also shows the cost of more responsive variants or international visitors.

Test LCP, image bytes, and cache-hit ratio

A provider comparison works only when each candidate serves the same pages. It must also serve the same image sizes and regions.

For mobile image-heavy pages, cutting transferred image bytes by 40% to 70% can help LCP. It helps only when JavaScript, caching, and origin speed do not delay the LCP image.

Use one repeatable test method

Start with five to ten representative URLs. Include a home page, category page, product page, article, search page, and logged-out landing page.

Test from North America at mobile and desktop widths. Run both cold-cache and warm-cache tests.

Record these values for each provider:

Real-user LCP for at least 14 to 28 days, not just one lab run.
Total image bytes at 390-pixel, 768-pixel, and 1,440-pixel viewports.
CDN edge cache-hit ratio and origin requests during peak traffic.
Time to first byte, served format, and `srcset` width selection.
Monthly cost at current traffic and three times current traffic.

Compare common platform paths

Platform path	CDN delivery	Image transforms	Cost pattern	Best fit
Kinsta with Cloudflare CDN	Included CDN layer	[Image optimization](https://hosting.websitemaintenancelab.com/cdn-based-image-optimization-services-comparison/) is an add-on	Predictable hosting, separate image feature	Managed WordPress teams
SiteGround with Speed Optimizer	Plan and CDN option dependent	WebP generation via WordPress tools	Low entry price, check renewals and limits	Small WordPress sites
Hostinger with CDN and plugins	Tier dependent	Often plugin-based, not an image API	Budget hosting, feature limits vary	Portfolios and early-stage sites
Cloudinary or ImageKit	Dedicated image edge network	On-demand crop, resize, WebP, AVIF	Usage-based requests, storage, bandwidth	Headless, SaaS, user uploads

How an optimized image reaches a visitor

1. Original
JPEG or PNG upload

→

2. Transform
Width, crop, WebP or AVIF

→

3. Edge cache
Stores the requested variant

→

4. Browser
Gets the right size for its screen

Compression alone is not enough

Compression cuts file weight. Responsive images stop oversized downloads.

You need both methods. Set width and height attributes so browsers reserve image space before loading.

This prevents Cumulative Layout Shift, also called CLS.

Migrate image delivery without breaking SEO

Do not change every image URL in one release.

The safest migration keeps image URLs or adds permanent redirects. It also keeps image dimensions and alt text unchanged.

Keep the old origin available for at least 7 to 14 days. This gives you time to catch broken assets.

Set up a staged image route

Use this order for WordPress, ecommerce, and custom applications:

Create `images.example.com` and point its DNS record to the new CDN or image service.
Set the service to fetch missing files from the existing origin.
Allow approved widths, formats, and crop presets only. This limits variant growth.
Set an initial edge TTL between 5 and 30 minutes while testing updates.
Move a small page group or 5% to 10% of traffic first. Then inspect errors and cache hits.
Raise TTL after validation. Keep a documented DNS or application rollback setting.

Keep search and layout signals intact

Built-in image delivery is not a priority for internal sites with few images and limited traffic. It may not fit when a specialized image CDN gives your headless app better signed URLs, editing controls, privacy options, or multi-cloud delivery. Avoid a forced migration when those features matter more than one hosting invoice.

Image SEO should keep the signals that search engines and browsers use. Keep descriptive filenames and stable image URLs where possible.

Retain accurate alt text. Include key product, editorial, or portfolio images in an image sitemap when relevant.

You can also include these images in page-level structured data. This can help search engines understand their role.

Responsive markup still matters with an image CDN. Use srcset and sizes, or framework-generated equivalents.

These settings send sensible width requests to the CDN. They stop one oversized asset from serving every screen.

Add explicit width and height attributes or an aspect-ratio rule. This prevents CLS.

For hero images, preload only the likely LCP image. Check that WebP or AVIF delivery preserves crops, MIME types, and crawler cache behavior.

Your questions answered

Is hosting with a built-in CDN enough for images?

Hosting with a built-in CDN is enough when it serves responsive sizes, modern formats, and cacheable image URLs within your traffic limits. Check whether resizing and AVIF conversion are included. Delivery alone will not cut oversized mobile downloads.

What should I do when a CDN breaks images?

Keep the original image origin available and switch traffic back through DNS or an application setting. Check TLS certificates, hotlink protection, signed URLs, MIME types, and cache rules. Do this before purging everything.

Is Kinsta or SiteGround better for image delivery?

Kinsta suits managed WordPress sites that want a Cloudflare-backed CDN and a defined image optimization add-on. SiteGround can suit smaller sites using WordPress tools for WebP. Compare renewal pricing, CDN terms, and resizing needs first.

How much does CDN hosting cost in the United States?

CDN hosting commonly starts between $10 and $40 monthly for small sites. Image-heavy usage can add request and bandwidth charges. Price current traffic and three times that traffic before an annual term.

Can I keep my current image URLs during migration?

You can keep image URLs through an origin-pull or proxy setup behind the same custom domain. Test redirects, browser cache headers, and fallback behavior for at least 7 to 14 days. Retire the old origin only after those tests pass.

Does AVIF always improve Core Web Vitals?

AVIF can cut image bytes, but it does not always improve Core Web Vitals alone. It helps when browsers receive properly sized files without delaying the LCP image. Extra processing time can erase the gain.

Lo esencial:

Choose integrated hosting for stable WordPress sites when image features and limits match actual usage.
Choose a dedicated image CDN when headless assets, user uploads, or transform control matter more than one vendor invoice.
Measure LCP, image bytes, cache-hit ratio, and cost per million requests before and after migration.
Protect SEO and uptime with a custom image domain, staged TTLs, and origin fallback.