What is a content delivery network (CDN) and how do I integrate it with Connect Quest hosting?
A CDN (Content Delivery Network) is a distributed network of servers that caches your website's static content at 200-300 locations worldwide. When a visitor in Delhi requests your Mumbai-hosted website, the CDN serves cached images/CSS/JS from Delhi instead, reducing load time from 200ms to 15ms. Connect Quest hosting integrates with Cloudflare, Bunny CDN, AWS CloudFront, and any other CDN provider.
DETAILED EXPLANATION:
What CDN caches vs what it does not:
CDN caches (accelerates):
- Images (.jpg, .png, .gif, .webp)
- CSS and JavaScript files
- Fonts (.woff, .woff2)
- PDF and other documents
- Static HTML pages (if configured)
- Video files (with streaming CDN)
CDN does NOT cache (dynamic content, by default):
- Logged-in user pages (shows wrong cart to wrong user)
- Checkout and payment pages
- Admin dashboards
- Search results
- API responses with user-specific data
CDN for India - provider comparison:
Cloudflare: Free tier excellent. 200+ PoPs globally including India. Best for most sites.
Bunny CDN: Rs 4-8/GB egress. Cheaper than Cloudflare Pro for high volume. India PoPs.
AWS CloudFront: Rs 17-21/GB egress. Expensive but full AWS integration.
Fastly: Enterprise grade, expensive. Not recommended for most Indian businesses.
WHEN TO USE:
- Any website with users beyond the host server's city
- Image-heavy sites (product catalogs, photography)
- Sites experiencing slow global load times
- High-traffic sites to reduce origin server load
STEP-BY-STEP - Cloudflare CDN setup with Connect Quest hosting:
1. Sign up free at cloudflare.com
2. Add your site:
Enter your domain name -> Cloudflare scans existing DNS records
Review imported records -> confirm they look correct
3. Update nameservers at your domain registrar:
In Connect Quest domain manager (connectquest.co.in):
Change nameservers from current to:
NS1: aiden.ns.cloudflare.com
NS2: vera.ns.cloudflare.com
Wait 24-48 hours for propagation
4. Configure SSL/TLS mode:
Cloudflare Dashboard > SSL/TLS > Overview
Mode: Full (Strict) - REQUIRED if your origin has SSL
(NOT Flexible - that leaves origin-to-Cloudflare unencrypted)
5. Optimize caching settings:
Dashboard > Caching > Configuration:
Caching Level: Standard
Browser Cache TTL: 4 hours
Edge Cache TTL: 1 week
Dashboard > Speed > Optimization:
Enable: Auto Minify (JavaScript, CSS, HTML)
Enable: Brotli compression
Enable: HTTP/2 Push
Enable: Rocket Loader (deferred JavaScript loading)
6. Add Page Rules for granular control:
Rule 1: *.yourdomain.com/wp-admin/* -> Cache Level: Bypass
Rule 2: *.yourdomain.com/checkout/* -> Cache Level: Bypass
Rule 3: *.yourdomain.com/account/* -> Cache Level: Bypass
7. WordPress plugin for automatic cache purging:
Install: Cloudflare WordPress Plugin
Enter: Zone ID and API Token from Cloudflare dashboard
Enables: Automatic cache purge when you publish/update posts
REAL EXAMPLES:
Before Cloudflare (Connect Quest Mumbai server):
User in Delhi: DNS lookup 20ms + TCP connect 40ms + TTFB 180ms + HTML load 200ms = 440ms
Images loading from Mumbai: 50ms each x 20 images = 1000ms additional
After Cloudflare (edge served from Delhi PoP):
User in Delhi: DNS 5ms + TCP connect 8ms + TTFB 15ms (cached HTML) = 28ms
Images from Cloudflare Delhi PoP: 12ms each x 20 images = 240ms
Total improvement: 440ms -> 28ms for initial HTML (15x faster)
Image improvement: 1000ms -> 240ms (4x faster)
Cloudflare cache hit rate (good WordPress site):
Cached requests: 78%
Uncached (dynamic): 22%
Origin server sees only 22% of total traffic
FLOW:
User request -> Cloudflare nearest PoP:
-> Cache HIT (static file): Serve in <20ms, origin never contacted
-> Cache MISS (new content): Fetch from Connect Quest origin, cache it, serve
-> Dynamic page (admin, checkout): Pass through to Connect Quest origin
KEY POINTS:
- Cloudflare free tier provides CDN + DDoS protection + SSL - use it on every site
- Cache bypass rules essential for checkout, cart, logged-in pages
- Cloudflare Analytics shows cache hit rate (aim for 70%+)
- Connect Quest origin server can be set to only accept requests from Cloudflare IPs (security)
COMMON MISTAKES:
- Setting SSL mode to Flexible (insecure, shows false padlock with unencrypted origin connection)
- Not bypassing cart and checkout pages (users see wrong order total or each other's carts)
- Forgetting to purge cache after site changes (visitors see old version for days)
QUICK FIX:
Old website showing after update: Cloudflare Dashboard > Caching > Purge Cache > Purge Everything
For automated purge on WordPress publish: Install Cloudflare WordPress Plugin
DIFFICULTY: Beginner
RELATED: Web Hosting, WordPress Performance, DDoS Protection, Connect Quest Hosting
DETAILED EXPLANATION:
What CDN caches vs what it does not:
CDN caches (accelerates):
- Images (.jpg, .png, .gif, .webp)
- CSS and JavaScript files
- Fonts (.woff, .woff2)
- PDF and other documents
- Static HTML pages (if configured)
- Video files (with streaming CDN)
CDN does NOT cache (dynamic content, by default):
- Logged-in user pages (shows wrong cart to wrong user)
- Checkout and payment pages
- Admin dashboards
- Search results
- API responses with user-specific data
CDN for India - provider comparison:
Cloudflare: Free tier excellent. 200+ PoPs globally including India. Best for most sites.
Bunny CDN: Rs 4-8/GB egress. Cheaper than Cloudflare Pro for high volume. India PoPs.
AWS CloudFront: Rs 17-21/GB egress. Expensive but full AWS integration.
Fastly: Enterprise grade, expensive. Not recommended for most Indian businesses.
WHEN TO USE:
- Any website with users beyond the host server's city
- Image-heavy sites (product catalogs, photography)
- Sites experiencing slow global load times
- High-traffic sites to reduce origin server load
STEP-BY-STEP - Cloudflare CDN setup with Connect Quest hosting:
1. Sign up free at cloudflare.com
2. Add your site:
Enter your domain name -> Cloudflare scans existing DNS records
Review imported records -> confirm they look correct
3. Update nameservers at your domain registrar:
In Connect Quest domain manager (connectquest.co.in):
Change nameservers from current to:
NS1: aiden.ns.cloudflare.com
NS2: vera.ns.cloudflare.com
Wait 24-48 hours for propagation
4. Configure SSL/TLS mode:
Cloudflare Dashboard > SSL/TLS > Overview
Mode: Full (Strict) - REQUIRED if your origin has SSL
(NOT Flexible - that leaves origin-to-Cloudflare unencrypted)
5. Optimize caching settings:
Dashboard > Caching > Configuration:
Caching Level: Standard
Browser Cache TTL: 4 hours
Edge Cache TTL: 1 week
Dashboard > Speed > Optimization:
Enable: Auto Minify (JavaScript, CSS, HTML)
Enable: Brotli compression
Enable: HTTP/2 Push
Enable: Rocket Loader (deferred JavaScript loading)
6. Add Page Rules for granular control:
Rule 1: *.yourdomain.com/wp-admin/* -> Cache Level: Bypass
Rule 2: *.yourdomain.com/checkout/* -> Cache Level: Bypass
Rule 3: *.yourdomain.com/account/* -> Cache Level: Bypass
7. WordPress plugin for automatic cache purging:
Install: Cloudflare WordPress Plugin
Enter: Zone ID and API Token from Cloudflare dashboard
Enables: Automatic cache purge when you publish/update posts
REAL EXAMPLES:
Before Cloudflare (Connect Quest Mumbai server):
User in Delhi: DNS lookup 20ms + TCP connect 40ms + TTFB 180ms + HTML load 200ms = 440ms
Images loading from Mumbai: 50ms each x 20 images = 1000ms additional
After Cloudflare (edge served from Delhi PoP):
User in Delhi: DNS 5ms + TCP connect 8ms + TTFB 15ms (cached HTML) = 28ms
Images from Cloudflare Delhi PoP: 12ms each x 20 images = 240ms
Total improvement: 440ms -> 28ms for initial HTML (15x faster)
Image improvement: 1000ms -> 240ms (4x faster)
Cloudflare cache hit rate (good WordPress site):
Cached requests: 78%
Uncached (dynamic): 22%
Origin server sees only 22% of total traffic
FLOW:
User request -> Cloudflare nearest PoP:
-> Cache HIT (static file): Serve in <20ms, origin never contacted
-> Cache MISS (new content): Fetch from Connect Quest origin, cache it, serve
-> Dynamic page (admin, checkout): Pass through to Connect Quest origin
KEY POINTS:
- Cloudflare free tier provides CDN + DDoS protection + SSL - use it on every site
- Cache bypass rules essential for checkout, cart, logged-in pages
- Cloudflare Analytics shows cache hit rate (aim for 70%+)
- Connect Quest origin server can be set to only accept requests from Cloudflare IPs (security)
COMMON MISTAKES:
- Setting SSL mode to Flexible (insecure, shows false padlock with unencrypted origin connection)
- Not bypassing cart and checkout pages (users see wrong order total or each other's carts)
- Forgetting to purge cache after site changes (visitors see old version for days)
QUICK FIX:
Old website showing after update: Cloudflare Dashboard > Caching > Purge Cache > Purge Everything
For automated purge on WordPress publish: Install Cloudflare WordPress Plugin
DIFFICULTY: Beginner
RELATED: Web Hosting, WordPress Performance, DDoS Protection, Connect Quest Hosting