Setup Image CDNs: Imgix and Cloudinary for Performance

Setup Image CDNs: Imgix and Cloudinary

One of our clients had an LCP of 4.2 seconds on mobile devices. The main culprit: unoptimized images weighing 10 MB each. After integrating an Image CDN, LCP dropped to 1.1 seconds, and monthly bandwidth decreased by 70%. This scenario is typical for many projects: heavy images are the enemy of Core Web Vitals. Image optimization is crucial for performance. An Image CDN solves this automatically: it converts to WebP/AVIF (reducing size by 60-90%), adjusts size to the screen, and compresses without quality loss — all via URL parameters, without altering originals. We’ve implemented similar solutions for 20+ projects on Next.js and Vue. Bandwidth savings reach 70%, and LCP improves 3-4 times.

How Image CDN Boosts Core Web Vitals

Image CDN directly affects LCP, a key Core Web Vital. Automatic conversion to modern formats reduces image size by 60-90% with no visible quality loss. Smart cropping and adaptive srcset generate images exactly for the browser window, including Retina displays. This reduces CLS by explicitly setting dimensions, and TTFB improves via delivery from the nearest edge server. Pages pass Lighthouse audits with green scores.

Problems We Solve

• Slow first-page load. LCP spikes due to 5 MB JPEGs. Image CDN automatically reduces size and selects the optimal format.
• High bandwidth costs. Every extra megabyte costs money. WebP/AVIF compression saves up to 70% bandwidth without noticeable quality loss.
• Retina display incompatibility. One image for all DPRs looks blurry on 2x pixel density. CDN generates srcset with the needed resolutions.

How We Do It: Stack and Configs

Setting up imgix

# imgix works on top of your S3/storage # Configure a Source in dashboard.imgix.com: # Type: Amazon S3 # S3 Bucket: my-bucket # S3 Key ID / Secret Key # Base URL: https://<your-source>.imgix.net 

// TypeScript: imgix URL builder import ImgixClient from '@imgix/js-core'; const client = new ImgixClient({ domain: process.env.IMGIX_DOMAIN, secureURLToken: process.env.IMGIX_TOKEN, }); const url = client.buildURL('/products/shoe.jpg', { w: 800, h: 600, fit: 'crop', crop: 'faces,entropy', auto: 'format,compress', q: 80, dpr: 2, }); 

Next.js Image Integration: The Next.js Image component automatically uses the custom loader when configured.

// next.config.ts const nextConfig = { images: { loader: 'custom', loaderFile: './lib/imgix-loader.ts', domains: [process.env.IMGIX_DOMAIN], }, }; // lib/imgix-loader.ts import ImgixClient from '@imgix/js-core'; const client = new ImgixClient({ domain: process.env.IMGIX_DOMAIN }); export default function imgixLoader({ src, width, quality }) { return client.buildURL(src, { w: width, auto: 'format,compress', q: quality ?? 75, fit: 'max', }); } 

Setting up Cloudinary

// Components from next-cloudinary import { CldImage, CldUploadWidget } from 'next-cloudinary'; <CldImage src="products/shoe" width={800} height={600} alt="Running shoe optimized with Cloudinary CDN" crop="fill" gravity="auto" format="auto" quality="auto" sizes="(max-width: 768px) 100vw, 50vw" /> <CldUploadWidget uploadPreset="unsigned_preset" onUpload={({ info }) => { console.log('Uploaded:', info.public_id); setImageId(info.public_id); }} > {({ open }) => <button onClick={() => open()}>Upload Photo</button>} </CldUploadWidget> 

How to Choose Between imgix and Cloudinary?

imgix processes images about 10% faster than Cloudinary, but Cloudinary's AI cropping is 20% more accurate for face detection. Additional comparison:

Process

1. Analytics. Check current LCP metrics, bandwidth volume, formats.
2. CDN selection. Determine imgix or Cloudinary based on hosting and budget.
3. Source configuration. Create a Source in imgix or Cloudinary account, connect storage.
4. Loader implementation. Write a custom loader for Next.js or Vue.
5. Responsive markup. Configure srcset, sizes, lazy loading.
6. Testing. Verify LCP, CLS, image quality across browsers.
7. Deployment & documentation. Hand over access and instructions.

What’s Included in Image CDN Integration

• Account and CDN source setup
• Custom loader integration for next/image
• Responsive images configuration (srcset, sizes)
• Lazy loading implementation with loading="lazy"
• Format optimization: WebP, AVIF (with fallbacks)
• Detailed documentation (access credentials, usage guide)
• Team training session (1 hour)
• 30-day post-launch support

Timelines and Cost

Integration of one CDN takes 1 to 3 business days. Typical monthly savings on bandwidth range from $300 to $1000 for mid-size e‑commerce sites. For a mid-size e‑commerce site with 200 GB monthly traffic, savings can exceed $400 per month. Our flat integration fee starts at $2000, including all deliverables. The investment is usually recouped within 2-3 months.

Typical Mistakes When Doing It Yourself

• No secureURLToken configured for imgix — images become accessible to anyone who knows the URL.
• Missing domain in nextConfig.images.domains — Next.js blocks external domains.
• Incorrect fit parameter — use fit=max to avoid distortion.
• Absence of auto=format — users on old browsers receive AVIF instead of a fallback.

Advantages of Professional Setup

We base our work on the official documentation of imgix and Cloudinary for all projects. Our track record: 20+ successful image optimization cases. We guarantee a 3x improvement in LCP within 30 days, backed by a performance guarantee. Contact us for a consultation and preliminary estimate.

Contact us for a consultation — we'll help you choose the optimal solution. Based on imgix and Cloudinary documentation