My images load slowly overseas, what could be wrong with my CDN setup?

A slow image load overseas usually points to one of a few CDN misconfigurations or origin delivery issues. The most common problems are:

1) CDN caching isn’t actually happening

If overseas users are still going back to your origin a lot, latency will be high.

Check:

• Cache-Control headers on images
• Whether the CDN respects your origin headers
• Low cache hit ratio in CDN logs/metrics
• Set-Cookie or Vary: * headers preventing caching

Fix:

• Use long-lived cache headers for versioned assets, e.g.:
  • Cache-Control: public, max-age=31536000, immutable
• Avoid cookies on static image responses
• Remove unnecessary Vary headers

2) The CDN is not serving from nearby edge locations

If traffic is landing in faraway PoPs, users overseas may be routed inefficiently.

Check:

• Where requests are actually being served from
• Any geo-routing or DNS routing issues
• Whether the CDN has POP coverage in the regions you care about

Fix:

• Verify CDN edge coverage in target countries
• Enable/adjust geo-routing or anycast settings
• Ensure DNS isn’t forcing users to a specific region

3) DNS resolution is slow or poorly configured

International users often pay a big penalty if DNS is slow.

Check:

• DNS lookup times from overseas locations
• TTL values
• Whether your CDN CNAME chain is too long

Fix:

• Use a fast authoritative DNS provider
• Reduce unnecessary CNAME hops
• Set sensible TTLs

4) TLS handshake latency is high

For overseas clients, handshake round trips can be significant.

Check:

• TLS version and cipher setup
• OCSP stapling
• HTTP/2 or HTTP/3 support
• Whether connections are reused

Fix:

• Enable TLS 1.3
• Make sure HTTP/2 or HTTP/3 is enabled
• Use session resumption
• Ensure certificates are deployed at edge nodes

5) Images are too large or not optimized

Even with a CDN, big files will still be slow on long-distance or poor links.

Check:

• Actual image byte size
• Whether you’re serving oversized dimensions
• Compression format and quality
• Use of modern formats like WebP/AVIF

Fix:

• Resize images to display dimensions
• Serve WebP/AVIF where supported
• Compress appropriately
• Use responsive images (srcset, sizes)

6) Cache-busting or query strings are hurting hit rates

If every request looks unique, the CDN may treat each as a miss.

Check:

• Random query params on image URLs
• Versioning strategy
• CDN cache key configuration

Fix:

• Use file versioning in the path or filename
• Configure CDN to ignore irrelevant query params if appropriate

7) Origin is far away or overloaded

If the CDN misses cache or uses origin fetches often, overseas users may feel origin distance.

Check:

• Origin location relative to your user base
• Origin response times
• Timeouts/retries from edge to origin

Fix:

• Put origin closer to the CDN region or use multi-region origins
• Increase cacheability
• Reduce origin dependency

8) Hotlink protection, auth, or edge logic is slowing delivery

Signed URLs, token validation, WAF rules, or edge functions can add latency.

Check:

• Edge function execution time
• WAF logs
• Signed URL validation overhead
• Redirect chains

Fix:

• Minimize edge computation on static images
• Avoid redirects for asset delivery
• Cache auth decisions if possible

9) No image transformation at the edge

Serving one giant original image worldwide is often inefficient.

Fix:

• Use an image CDN or transformations at the edge
• Auto-format based on client support
• Resize per device viewport

Quick things to inspect right now

Run a request and look at headers like:

• Age
• Cache-Control
• CF-Cache-Status / X-Cache / CDN equivalent
• Via
• Server-Timing
• Content-Length

Also test from multiple regions with:

• WebPageTest
• Pingdom
• GTmetrix
• curl from a server overseas

Most likely culprits

If this is specifically “overseas,” the top suspects are:

1. Low cache hit ratio
2. Large unoptimized images
3. Origin fetches from a distant region
4. DNS/TLS latency
5. CDN routing/POP issues

If you want, I can help you troubleshoot by looking at:

• your image response headers,
• CDN provider,
• origin setup,
• and a sample URL.