Tengxun Cloud Server CDN Accelerated Test: How Much Speed Increase after Accessing CDN
In the world of the internet, there is a well-known “three-second rule”:
If a website takes more than 3 seconds to load, more than 50% of users will choose to close the tab directly.
. For corporate websites, cross-border e-commerce platforms or content sites, speed is not only a matter of experience, but also a matter of conversion rate, SEO ranking and real money.
Many enterprises have completed
Purchase Tencent Cloud Server
(such as CVM lightweight application server or cloud server) and deploy the website, often find a pain point:
The speed of local testing is very fast, but it is obvious when foreign users or cross-operator access.
. At this time, hanging CDN (Content Delivery Network) on the website has become the unanimous choice of the vast majority of operation and maintenance and webmasters.
In order to find out whether CDN is an "IQ tax" and how much it can speed up the website, we have set up a test environment close to the real business, and made an in-depth measured comparison of the website performance after accessing Tengxunyun CDN.
1. Setting up the test environment and defining metrics
In order to make the test data valuable, we simulated a standard small and medium-sized Web site environment on the cloud:
Source server: a standard CVM instance purchased through tengxun cloud server (configuration: 2-core 4G, Beijing region, 5Mbps fixed bandwidth).
Site Type: A graphic test site based on WordPress, with a home page size of about 4.2MB (including 1 HTML file, 8 CSS/JS scripts, and 15 high-definition picture resources).
Network environment: Concurrent request testing is conducted through dial test nodes distributed across the country (covering the three major operators of China Telecom, China Unicom, and China Mobile, as well as different geographical locations such as Guangzhou, Shanghai, Chengdu, Harbin, and Urumqi).
Acceleration service: Tencent Cloud CDN (Content Delivery Network), configured with basic static file caching rules and Gzip/Brotli intelligent compression.
The test focuses on the following four key metrics that determine user experience:
TTFB (First Byte Arrival Time): The time from the time the user initiates the request to the time the first byte is received from the server, reflecting network latency and server response speed.
DOM Content Loaded(DOM load completion time): The time when the web page framework is completed.
Fully Loaded: Total time taken to load a full page including all images, stylesheets, scripts.
Concurrency tolerance and origin site bandwidth usage: the load of the origin site server when multiple people access at the same time.
Comparison of 2. Measured Data: Extreme Pull-apart Before and After Access to CDN
We are separately at
After directly connecting to the source station (CDN is not opened) and accessing Tengxun cloud CDN and completing cache warm-up
In the two states, the speed measurement tool was used to conduct three rounds of access tests on 50 nodes across the country, and the average data was taken:
1. Nationwide comparison of full-page load times across multiple nodes
Test region/Operator
Not connected
CDN (directly connected to Beijing source station)
After accessing Tengxun Cloud CDN
Speed increase range
Beijing (City Telecom)
1.12 seconds
0.38 seconds
Increase ~ 66%
Shanghai (cross-regional connectivity)
2.85 seconds
0.45 seconds
Increase by ~84%
Guangzhou (Cross Regional Mobile)
3.40 seconds
0.42 seconds
Increase ~ 87%
Chengdu (Southwest Telecom)
4.10 seconds
0.51 seconds
Increase ~ 87.5%
Urumqi (Northwest Cross Network)
6.80 seconds
0.65 seconds
Increase ~ 90.4%
National Average Full Load Time
3.65 seconds
0.48 seconds
Overall speed increase ~ 86.8%
2. Improvement of key performance indicators
Judging from the summary data of the national test nodes, the improvement of various indicators is extremely exaggerated:
Average TTFB (First Byte Time): Dies from 320ms from no access to 28ms. Because the request no longer needs to travel long distances back to the Beijing source station, but is directly responded by the Tencent cloud edge node closest to the user.
Web page full load time: from an average of 3.65 seconds to 0.48 seconds. This means that the site from the "obvious perception of Caton" directly into the "seconds open" era.
Wide outbound traffic of the source station: under 100 concurrent access requests, the bandwidth of the source station is directly full when CDN is not opened (5Mbps bottleneck leads to queuing), while after CDN is opened and the cache hit rate reaches more than 95%, the outbound traffic of the source station is reduced by more than 90%.
3. why CDN can bring such a huge leap in speed?
Judging from the test results, the speed increase of more than 80% is not "black magic", but CDN has solved a series of network bottlenecks from the physical architecture and transmission protocol level:
1. Decoupling of physical distance and network transmission across networks
China has a vast territory, and the cross-network interconnection between the three operators (such as mobile users accessing servers in telecom rooms) is naturally subject to delay and packet loss. If only carried out
Purchase Tencent Cloud Server
, your server physical location is fixed (for example, only in Beijing or Guangzhou).
After accessing the CDN, Tengxun Cloud's thousands of edge nodes distributed across the country act as "pre-warehouses". Users in Guangdong visit your website. Static pictures and style sheets are directly provided by nodes in Guangzhou or Shenzhen. The transmission distance has been shortened from thousands of kilometers to about ten kilometers, and the network delay has naturally dropped from hundreds of milliseconds to single digits.
2. Break through the "single pipe limit" of the exit bandwidth of the source station"
Suppose you are in
Purchase Tencent Cloud Server
The bandwidth of 5Mbps is selected, and its limit download speed is only about 625KB/s. If a web page is 4.2MB in size, it takes about 6.7 seconds for a single user to download it completely! If 10 people visit at the same time, the network is immediately full and there is a serious Caton queue.
The Tencent cloud CDN node has 100 Gbps
level of reserve bandwidth. After images and static files are cached to the CDN node, users download using the ultra-large bandwidth of the CDN edge node, directly breaking through the 5Mbps physical bottleneck of the source station.
3. Intelligent compression and protocol optimization
The default or custom enabled in the Tengxun Cloud CDN console
Gzip / Brotli Smart Compression
, CSS, JS, and HTML codes can be automatically compressed at the edge node and then transmitted to the browser. At the same time, it supports
HTTP/2 and HTTP/3 (QUIC)
protocol, which implements multiplexing and header compression, and further reduces the overhead of TCP handshake.
[End User (Guangzhou Unicom)]
│ 1. Initiate a request nearby (delay <10ms)
▼
┌──────────────────────────────────────────────┐
│ Tengxun Cloud CDN Edge Node (Guangzhou) │
│-Static Resources (Pictures/CSS/JS) Hit Cache-Seconds Return │
└──────────────────────┬───────────────────────┘
2. Only dynamic requests/misses back to the source.
▼
┌──────────────────────────────────────────────┐
Source Station: Tengxun Cloud CVM Server (Beijing)
└──────────────────────────────────────────────┘
4. Squeeze CDN Performance: Tengxun Cloud CDN Speed-up Best Practice Configuration
Many webmasters found that "speed increase is not obvious" after accessing CDN, 90% of the reason is
Configuration not tuned
, resulting in a low cache hit rate and frequent requests running back to the source station (I. e. "back to the source"). In order to achieve the effect of "speeding up by more than 85%" in the test, it is recommended to make the following three core configurations in the Tengxun Cloud CDN console:
1. Fine setting node cache expiration rules
Enter
CDN console-> Domain name management-> Node cache expiration configuration
:
Static files (images, fonts, compressed packages): Set the cache time to 30 days or higher. These files rarely change, and long-term retention in the node can greatly improve the hit rate.
Front-end code (JS, CSS): If the file name has Hash verification (such as main.a8f2c.js), you can also set
30 days cache; if there is no Hash, it can be set to 7 days and combined with browser cache.
Dynamic page (.php,. asp, API interface): Set to not cache (0 seconds). For pure dynamic content, consider turning on Tencent Cloud full-site acceleration ECDN (dynamic and static separation acceleration).
2. Turn on intelligent compression and HTTP/2 / HTTPS optimization
Turn on Gzip / Brotli compression in the performance optimization module. Brotli's compression rate is 15%-25% higher than that of conventional Gzip, which can significantly reduce the transmission volume of code files.
Configure an HTTPS certificate and select the HTTP/2 option. The parallel loading mechanism of HTTP/2 allows dozens of static resources to be transmitted simultaneously in a single TCP connection, avoiding queuing congestion.
3. Turn on "Ignore URL Parameters" to increase the hit rate
Many marketing links or web frameworks will have a shape like this after the URL.
?utm_source=baidu
or
?v=1.0
The suffix. By default, the CDN will determine it as a different file and return it to the origin.
Set meaningless marketing parameters or version numbers
"Ignore URL parameters"
, can greatly improve the cache reuse rate of CDN nodes.
Summary
Back to the original question:
How much can the website speed be improved after accessing CDN?
The measured data gives a very convincing answer: for a standard website with a lot of static resources (images, style sheets, scripts),
Access to Tencent Cloud CDN can reduce the national average loading time by more than 80% and the first byte response time by nearly 90%
.
If you have finished
Purchase Tencent Cloud Server
And deployed business, do not let the server become an island. will
CVM server as a solid "computing power and data source station", with Tencent Cloud CDN node as a "cutting-edge distribution network"
, not only can exchange the extreme experience of "opening in seconds" of the website at a very low cost, but also can completely liberate the CPU and bandwidth pressure of the source server, so that your architecture can really cope with high concurrent traffic.
