CDN Performance Tester

Measure and compare response times from your browser to major CDN (Content Delivery Network) edge servers. This test helps you choose the fastest CDN for your location by fetching small resources from each provider and measuring round-trip time.

CDN Provider	Endpoint	Response Time	Status

What Is a CDN?

A Content Delivery Network (CDN) is a distributed network of servers deployed across multiple geographic locations. CDNs cache and serve web content from the server closest to the end user, dramatically reducing latency and improving page load times. Instead of every request traveling to a single origin server, the CDN serves content from an edge server that may be just a few milliseconds away.

CDNs are essential for modern websites with global audiences. They work alongside your DNS configuration to route users to the nearest edge server. Understanding CDN performance helps you make informed decisions about which provider will give your users the best experience. Test your current website speed with our Speed Test.

Major CDN Providers Compared

Provider	Edge Locations	Free Tier	Best For
Cloudflare	310+ cities	Yes (generous)	All-purpose, DDoS protection
AWS CloudFront	450+ PoPs	1TB/month free	AWS ecosystem integration
Google Cloud CDN	180+ PoPs	No	Google Cloud integration
Fastly	90+ PoPs	Limited	Real-time configuration, edge computing
Akamai	4,000+ servers	No	Enterprise, media streaming
Microsoft Azure CDN	185+ PoPs	Limited	Azure ecosystem integration
jsDelivr	Cloudflare + Fastly	Yes (open source)	Open source libraries, npm packages
Bunny CDN	120+ PoPs	14-day trial	Budget-friendly, great performance

Pro Tip: CDN performance varies significantly by location. A CDN that's fastest in North America might not be fastest in Asia or Europe. Run this test from your target audience's location (or use multiple testing locations) to get accurate results. Also consider that CDN performance depends on your bandwidth, network latency, and IP routing to the nearest edge server.

How CDNs Work

Understanding the CDN delivery process helps you optimize your setup:

DNS resolution — When a user requests your domain, DNS resolves to the nearest CDN edge server IP using anycast or geo-DNS routing.
Edge lookup — The edge server checks if the requested content is cached locally.
Cache hit — If cached, the content is served immediately from the edge (fastest path).
Cache miss — If not cached, the edge fetches content from the origin server, caches it, then serves it to the user.
Subsequent requests — Future requests for the same content are served from cache until the TTL expires.

This is why the first request to a CDN may be slower (cache miss) while subsequent requests are much faster (cache hit). The CDN's edge network acts as a caching proxy between your users and your origin server.

CDN Performance Metrics

Metric	What It Measures	Good	Impact
Latency (RTT)	Round-trip time to edge server	< 50 ms	Direct impact on TTFB and page load
Cache Hit Ratio	% of requests served from cache	> 90%	Reduces origin load and latency
Bandwidth	Throughput from edge to client	High	Faster downloads for large files
Time to First Byte	Time until first byte received	< 100 ms	User-perceived speed
SSL/TLS Handshake	Time for HTTPS negotiation	< 50 ms	Added latency for secure connections

Note: This test measures response time from your browser to CDN endpoints using fetch() in no-cors mode. Results reflect your current network path and may vary based on your ISP, geographic location, and network conditions. For production decisions, run tests at different times and from representative user locations. Verify your own network performance with our Speed Test and check your current IP location.

When to Use a CDN

A CDN is beneficial in these scenarios:

Global audience — Users access your site from multiple countries. CDN reduces latency for distant users.
High traffic — CDN offloads requests from your origin server, preventing overload.
Large static files — Images, videos, CSS, and JavaScript benefit most from CDN caching.
DDoS protection — CDNs like Cloudflare absorb attack traffic across their network.
Performance requirements — When you need consistent sub-100ms TTFB worldwide.
SSL termination — CDNs handle TLS at the edge, reducing server CPU load.

If you're running a website from a home server behind your router with port forwarding, a CDN can dramatically improve performance by caching content at edge locations instead of every request hitting your home connection.

CDN Configuration Best Practices

Maximize CDN performance with these configuration tips:

Set proper cache headers — Use Cache-Control: public, max-age=31536000 for static assets.
Use versioned filenames — Include hash in filenames (e.g., style.a1b2c3.css) for cache busting.
Configure DNS correctly — Point your domain's CNAME to the CDN. Verify with our DNS Lookup.
Enable compression — Ensure Brotli or gzip is enabled on the CDN for text-based assets.
Use HTTP/2 or HTTP/3 — Enable modern protocols for multiplexed connections.
Minimize origin round trips — Configure long cache TTLs and use stale-while-revalidate.

CDN and DNS Integration

CDNs rely heavily on DNS to route users to the correct edge server. There are two main routing approaches:

Routing Method	How It Works	Pros	Cons
Anycast DNS	Same IP advertised from multiple locations; BGP routes to nearest	Fast failover, simple setup	Routing depends on BGP, not always optimal
Geo-DNS	Different IPs returned based on querier's location	Precise control over routing	Depends on DNS resolver location accuracy
Latency-based	Routes to lowest-latency edge based on real-time measurements	Optimal performance	More complex, requires active monitoring

If your CDN is configured via DNS, make sure to set appropriate TTL values. Very low TTLs allow faster failover but increase DNS query volume. Use our DNS Lookup to check your current CDN DNS configuration and TTL values. Also verify DNS over HTTPS settings on your router to ensure DNS queries are secure.

Key Takeaways

CDNs serve content from edge servers closest to the user, reducing latency significantly.
CDN performance varies by location — test from your target audience's geography.
Cache hit ratio above 90% means your CDN is working effectively.
Set proper Cache-Control headers and use versioned filenames for optimal caching.
Cloudflare offers the most generous free tier; AWS CloudFront has the most edge locations.
CDNs also provide DDoS protection and SSL termination as added benefits.

Video: How CDNs Work

Related Tools and Guides

Frequently Asked Questions

What is a CDN and why do I need one?

A CDN (Content Delivery Network) is a distributed network of servers that caches your website content at edge locations worldwide. It reduces latency by serving content from the server closest to each user. You need one if your website has a global audience, serves large files, or needs DDoS protection and high availability.

Which CDN is the fastest?

The fastest CDN depends on your users' locations. Cloudflare and Google generally perform well globally due to their massive networks. AWS CloudFront excels in regions with many AWS availability zones. Run this test from your target audience's location for the most relevant results.

Are free CDNs good enough for production?

Yes, for many use cases. Cloudflare's free tier includes global CDN, DDoS protection, and SSL — sufficient for most small to medium websites. For high-traffic sites needing advanced features like custom edge rules, real-time analytics, or dedicated support, a paid plan is recommended.

How does a CDN affect my DNS setup?

When you set up a CDN, you typically change your domain's DNS records to point to the CDN instead of directly to your origin server. This is usually done via a CNAME record or by using the CDN's nameservers. The CDN then routes requests to the nearest edge server automatically.

Can a CDN make my website slower?

In rare cases, yes. If your content changes frequently and cache TTLs are too long, users may see stale content. If most of your users are near your origin server, the CDN adds an extra hop without benefit. Also, cache misses can be slower than direct origin access due to the extra routing.

How do I test CDN performance accurately?

Run multiple tests from different locations at different times of day. Use tools like this CDN tester alongside our speed test and ping test. Check cache headers to ensure content is being served from edge (look for "cf-cache-status: HIT" for Cloudflare, for example).

About Tommy N.

Tommy is the founder of RouterHax and a network engineer with 10+ years of experience in home and enterprise networking. He specializes in router configuration, WiFi optimization, and network security. When not writing guides, he's testing the latest mesh WiFi systems and helping readers troubleshoot their home networks.