Use this page to document real improvements from moving site images onto CDN delivery: cleaner evidence, better credibility, and a stronger conversion story.
Conversion page
This page is written as a practical before-and-after case study that can persuade visitors who are already thinking about site speed.
Evidence over hype
Show screenshots, metrics, and exact implementation changes. Specifics build trust much faster than generic claims.
Perfect for your own properties
You can adapt this page for gregcook.net, guncollectorsclub.com, or any page where moving images off the origin improved results.
Case study structure
Strong case studies answer five questions fast: what was slow, what changed, what improved, how it was measured, and why the change mattered to the business or user experience.
Recommended narrative
- Baseline: describe the original page and where images were served from.
- Problem: note the symptoms such as slower image delivery, heavier origin load, or uneven performance by region.
- Implementation: explain the exact move to CDN URLs, next-gen formats, long cache lifetimes, and responsive sizes.
- Results: show metric changes and page screenshots.
- Takeaway: explain which types of sites can expect similar wins.
Example results table
| Metric | Before | After | Why it matters |
|---|---|---|---|
| Image TTFB | Higher and more variable | Lower and more consistent | Visitors see visual content begin sooner. |
| Origin image traffic | All requests hit origin | Most requests served from cache | Frees your main server for HTML and app work. |
| Largest Contentful Paint | Slower hero image arrival | Faster hero image display | Improves user perception and Core Web Vitals. |
| Repeat visit speed | Inconsistent | More instant feeling | Cache reuse helps page-to-page browsing. |
What to include from your real tests
- PageSpeed or Lighthouse screenshots.
- Before-and-after waterfalls from WebPageTest or DevTools.
- The exact headers or markup changes you made.
- One or two lessons learned, such as not lazy-loading the hero image.
Example implementation summary
1. Converted large photos to WebP.
2. Created 640, 960, and 1280 pixel variants.
3. Updated image URLs to the CDN domain.
4. Set long-lived cache-control for versioned assets.
5. Added width and height attributes in markup.
6. Kept the hero image eager and moved gallery images to lazy loading.Recommended closing section
If your site depends on photography, article thumbnails, product images, or branded visuals, image delivery is often the fastest route to meaningful speed gains. A well-structured case study lets you prove that with your own numbers.
Publish a real before-and-after and link it from your About page, Guides hub, and comparison articles.
Related Guides: