CDN Global Acceleration: Choosing Edge Nodes and Cache Strategy for B2B Sites

Three-Layer CDN Cache Strategy and Node Selection for B2B Sites

CDN Global Acceleration: Choosing Edge Nodes and Cache Strategy for B2B Sites

Bottom line first: B2B sites hosted on domestic servers and visited from overseas are slow by nature — CDN isn’t optional. Three core metrics: keep LCP under 2.5 seconds, TTFB under 600 milliseconds, and compress the first-screen LCP image to under 200KB. Cache strategy follows three layers — static assets with a TTL of 7 to 30 days, public HTML cached for 5 minutes to 1 hour, and dynamic content never cached. Under 500GB monthly bandwidth, use pay-as-you-go; only consider a traffic package above 2TB. Don’t pay for global nodes you’ll never use.

1. Why B2B Sites Need CDN Even More

B2B sites and cross-border e-commerce sites have completely different traffic structures: e-commerce sites may get tens of thousands of daily visits, while B2B inquiry sites often get only a few hundred to a few thousand, heavily concentrated in a few target countries. But precisely because traffic is low, many site owners mistakenly think “no visitors means no need to accelerate.” The result: every overseas visitor pulls a full page from the domestic origin server, TTFB easily exceeds 2 seconds, first screen takes over 3 seconds, and the inquiry rate drops by half without anyone noticing.

The value of CDN for B2B sites isn’t just speed. Visitors get static assets from edge nodes, and the origin server is only hit on a cache miss, cutting origin bandwidth and CPU load by an order of magnitude and reducing the risk of being overwhelmed by crawlers and malicious requests. For tech stack selection, see crater’s Four-Piece Overseas Kit. For daily site performance maintenance, see Six monthly maintenance tasks.

Metrics	Typical values without CDN	Expected values with CDN	Measurement tool
TTFB (Time to First Byte)	1500 to 3000ms	200 to 600ms	WebPageTest / Lighthouse
LCP (Largest Contentful Paint)	4 to 8 seconds	1.8 to 2.5 seconds	CrUX / Search Console
Monthly origin outbound traffic	100% all origin pulls	Origin pull rate ≤ 10%	CDN console origin pull stats
Image loading	Single image 1 to 3MB	First-screen image ≤ 200KB	Performance panel
Global reachability	Timeouts in some regions	Global coverage ≥ 95%	Uptime global monitoring

2. Node Selection: Choose by Target Market, Don’t Buy “Global Full Coverage”

CDN vendors’ advertised “1000+ global nodes” mean little for B2B sites — you may only have visitors in 5 to 10 countries. When buying a plan, work backward from your target markets and spend your money on the edge locations where your visitors actually land.

Market priority follows the usual B2B go-global spread: Europe (Frankfurt, London), North America (Los Angeles on the West Coast, Virginia on the East Coast), the Middle East (Dubai), and Southeast Asia (Singapore). If your customers are concentrated in Latin America, confirm separately whether the CDN has POPs in São Paulo and Mexico City — many cheap plans have no Latin America nodes at all. For the quality bar on publishing multilingual content, see Multilingual launch QA checklist.

Target market	Preferred POPs	Latency baseline	Notes
Western Europe	Frankfurt, London	≤ 80ms	GDPR compliance requires confirming nodes are in-region
North America	Los Angeles, Virginia	≤ 100ms	Users in Asia-Pacific get faster routes via the West Coast
Middle East	Dubai, Riyadh	≤ 120ms	Some plans have no Middle East nodes
Southeast Asia	Singapore, Jakarta	≤ 100ms	Singapore has the widest coverage
Latin America	São Paulo, Mexico City	≤ 150ms	Must confirm separately; often missing
Australia & New Zealand	Sydney	≤ 120ms	For small markets, direct origin connection is an option

3. Three-tier caching: what to cache and what never to cache

A bad caching strategy is more dangerous than no caching at all. Caching the whole site seems easy, but you end up caching form submissions, session pages, and admin logins — inquiries vanish silently, login states break, and it takes two or three days of debugging to find out. The right approach is to configure rules in three tiers by content type.

Tier 1, static assets: CSS/JS with hashed filenames, images, and fonts get a TTL of 7 to 30 days; when the filename hash changes, the file refreshes automatically. Tier 2, semi-static: public article pages and product page HTML get a TTL of 5 minutes to 1 hour, so you get cache hits while edits go live worldwide within the hour. Tier 3, dynamic: form POSTs, user sessions, personalized recommendations, and admin pages are never cached, and are explicitly declared with Cache-Control: no-store. For media asset governance, see Image and video asset management, and for handling multilingual numeric tables, see Charts and tables across multiple sites.

Content type	Cache location	Suggested TTL	Cache key notes
Hashed CSS/JS	Edge nodes	7 to 30 days	The filename hash is the version
Static images	Edge nodes	7 to 14 days	Split WebP/AVIF by Accept
Font files	Edge nodes	30 days	Watch out for CORS
Public article HTML	Edge nodes	5 minutes to 1 hour	Bypass cache when cookies are present
Product catalog pages	Edge nodes	15 minutes to 1 hour	Stock changes need active refresh
Forms/sessions/admin	Do not cache	no-store	Exclude via path whitelist

4. Hit rate, origin pulls, and cost control

There’s one number that tells you whether your CDN is doing its job: the cache hit rate. B2B sites are mostly static assets, so aim for a hit rate above 90%; below 80% means your cache rules are misconfigured and a large share of requests are going back to origin. Common causes of a low hit rate: random parameters in HTML inflating the cache key, cookies not being ignored so every user gets a separate cache entry, and uncompressed images being pushed out by new images right after they’re cached.

On cost: a B2B site usually uses anywhere from tens of GB to a few hundred GB of bandwidth a month, and pay-as-you-go is the best deal, often running just tens to one or two hundred RMB a month. Don’t lock into an annual traffic package right away. Run pay-as-you-go for a month or two first, see your real bandwidth, then decide whether to switch to a package. For SEO protection during domain migration and CDN cutover, see 301 redirect mapping and SEO preservation.

Monthly bandwidth range	Billing recommendation	Monthly cost range	Note
< 100 GB	Pay-as-you-go	Tens of RMB	Best deal for small sites
100 to 500 GB	Pay-as-you-go or a small traffic package	100 to 300 RMB	Watch for two or three months before deciding
500 GB to 2 TB	Small traffic package	300 to 800 RMB	Hit rate should reach 90%
> 2 TB	Large traffic package / contract pricing	Negotiable	Negotiate a committed monthly price

5. Common CDN configuration pitfalls for B2B sites

Pitfall	Symptom	Troubleshooting and fixes
Caching HTML site-wide	Content changes never go live worldwide	Cache HTML with a short TTL only, or exclude by path
Forms get cached	Inquiries lost or submitted twice	Never cache POST requests; whitelist paths
HTTPS/HTTP3 not enabled	Slow handshakes; TLS dominates TTFB	Enable TLS 1.3 and QUIC/HTTP3
Images not converted	PNGs are too large on iOS	Auto-convert to WebP/AVIF based on Accept
Cache key includes tracking parameters	Low hit rate, origin requests spike	Ignore query parameters like UTM in the cache key
Origin server unprotected	CDN bypassed, origin hit directly	Origin firewall allows only CDN origin IP ranges

The last one is the easiest to overlook: a CDN only blocks visitors at the edge, and your origin can still be reached directly by IP. The right approach is to configure your origin firewall to allow only your CDN provider’s origin IP ranges and deny everything else. Otherwise, anyone who gets your origin IP can bypass the CDN and hit it directly. For how to set up site monitoring and alerts, see Site Monitoring and Alerting Checklist.

FAQ

B2B sites get very little traffic. Is a CDN even worth it?

Yes, and low-traffic sites need one even more. Low traffic usually means your origin’s bandwidth and setup are basic, and every overseas visitor has to cross the Pacific back to the origin, easily pushing TTFB past 2 seconds. A CDN caches static assets at the edge so visitors fetch them nearby, speeding up first paint by 1 to 2 seconds and directly boosting inquiry conversion. Pay-as-you-go often costs just tens of RMB a month, so don’t overthink it.

Cloudflare or an overseas CDN from a major Chinese provider?

For small sites, start with Cloudflare Free/Pro. Node coverage and TLS optimization work out of the box, and setup is simple. Once monthly bandwidth reaches a few hundred GB, or you need strong compliance and dedicated technical support, then compare Alibaba Cloud/Tencent Cloud International and AWS CloudFront. The test: run WebPageTest from three different cities in your target market first, and go with whoever has the lower TTFB. Don’t just look at the node counts vendors advertise.

Should HTML pages be cached? For how long?

For public article and product pages, cache HTML with a short TTL, 5 minutes to 1 hour, balancing hit rate and content freshness. Never cache pages with login state, shopping carts, or personalization. If you need edits to go live worldwide immediately, manually trigger a cache purge rather than waiting for the TTL to expire.

How do I troubleshoot a low cache hit rate?

Check three things in order. First, does the response include Set-Cookie? Requests with cookies use a separate cache key by default, so the hit rate drops. Second, does the URL contain random parameters or UTMs? Different parameters are treated as different resources. Third, do static asset filenames include a hash? Files without a hash keep the same name after an update, so neither the browser nor the CDN refreshes them. Fix all three and the hit rate typically goes from 50% to 90%.

How do I confirm the CDN is actually working?

Two steps. In your browser’s developer tools, open Network and check the response headers: you should see CDN signature headers like CF-Ray/X-Cache with a HIT. Then run a real test from your target market’s network environment with WebPageTest, comparing TTFB and LCP before and after the CDN. Local speed alone tells you nothing; you have to simulate an overseas visitor. Also check the origin bandwidth share in the CDN console: the origin pull rate should fall below 10%.

Will a CDN hurt SEO and AI crawlers?

No. Configured correctly, it helps. Search engines and large model crawlers can read the HTML the CDN returns without issue, and faster responses improve crawl budget. Two things to watch: don’t apply special caching to crawler paths that serves stale content, and enable HTTPS and HTTP/3 across the board. For SEO protection during a migration or CDN switch, see 301 redirect mapping plan.

Final thoughts

Overseas acceleration for a B2B site isn’t about showing off technical tricks. It’s about cutting the time an overseas visitor waits for the first screen from “too slow, I’m leaving” to “worth reading, I’ll submit an inquiry.” A CDN is the highest-ROI move here: a few dozen yuan a month to bring TTFB down from 2 seconds to a few hundred milliseconds.

Three steps to put it into practice. First, pick 3 to 5 core POP nodes based on your target markets; don’t pay for global nodes you’ll never use. Second, set cache rules in three tiers: long TTL for static assets, short TTL for HTML, no caching for dynamic content. Third, review hit rate and origin pull rate once a week; if the hit rate falls below 80%, go back and check your rules. Do these three things and your site’s overseas foundation is solid.

One line worth remembering: B2B inquiries often die in the three seconds a visitor spends waiting for your first screen. That’s the three seconds a CDN buys you.