tencent cloud

Content Delivery Network

Updates and Announcements
Release Notes
Announcements
User Tutorial
Product Introduction
Product Overview
Strengths
Use Cases
Term
Use Limits
CDN Performance Descriptions (Spot-check)
Purchase Guide
CDN Purchase Guide
ECDN Purchase Guide
Getting Started
Configuring CDN from Scratch
Adding Domain Names
CNAME Configuration
Domain Name Ownership Verification
FAQs about Domain Name Connection
Configuration Guide
Domain Management
Domain Name Configurations
Statistical Analysis
Purge and Prefetch
Log Management
EdgeOne
Service Query
Offline Cache
Permission Management
Permission Configuration
Console Permissions
Activate Real-time Logging as Sub-account/Collaborator
Use Cases
Accelerating Resources on COS with CDN
Practical Tutorial
Guide to Using the EdgeOne Tool for Migrating Content Delivery Network (CDN) Related Services
CDN - CVM
CDN - COS
Configuring CNAME via DNSPod
Regularly Storing CDN Logs
API Documentation
History
Introduction
API Category
Content Management APIs
Real-time Log APIs
Service Query APIs
Data Query APIs
Making API Requests
Log Query APIs
StopCdnDomain
Configuration Management APIs
Obsoleted APIs
Other APIs
Data Types
Error Codes
FAQ
Features
Billing
FAQs about Domain Name Connection
Cache Configuration FAQs
Purge and Prefetch
Statistical Analysis
FAQs about HTTPS
Connection
Errors
Troubleshooting Methods
Status Codes and Solutions
Node Cache Inconsistency
Slow Access Speed After CDN Activation
Low Traffic Hit Rate
404 Status Code
Page Display - CORS error
Resource Cache Failure
Service Level Agreement
Glossary

Slow Access Speed After CDN Activation

PDF
Focus Mode
Font Size
Last updated: 2024-12-30 22:04:15

Problem Description

My website is still slow after it’s connected to Tencent Cloud CDN.

Possible Reasons

You have not configured a CNAME record for the connected domain name at a DNS service provider, so the CDN acceleration service for the domain name is not in effect. Please check DNS.
The node cache validity is not configured properly. Please check the node cache validity configuration.
The resource URL is accessed for the first time after CDN activation, and it has not been prefetched before. Please prefetch the URL.
The website architecture has defects. Please optimize the website architecture.

Solutions

Check DNS

This example shows you how to run nslookup to check the DNS record of a CDN acceleration domain name:
Run `nslookup` for the acceleration domain name


If the result domain name is not suffixed with dnsv1.com as shown above, then the CDN acceleration service for your domain name is not in effect. Please check the CNAME record of the domain name at the DNS service provider as instructed in CNAME Configuration.


Check the node cache validity configuration

Log in to the CDN console, select Domain Management on the left sidebar, click Manage on the right of a domain name to enter its configuration page, and switch to the Cache Configuration tab to find the Node Cache Validity Configuration section.


Check the node cache rules of the resource: whether the validity is "0", too short, or is configured as "No Cache". Access requests will be forwarded to the origin server if the request resources are not cached on nodes, in which case the acceleration is not effective. Please configure the cache validity as required by your business.
Check whether the header Cache-Control is set as no-store/no-cache/private for your origin server.
If it is, you need to enable Force Cache for the CDN nodes to cache resources as configured.
If Force Cache is not enabled and the header is configured as so, CDN nodes will not cache resources even the cache validity is configured.
For more configuration rules, please see Node Cache Validity Configuration (New).


Prefetch the URL

It is normal that the speed is slow when accessing a resource for the first time which has not been prefetched before. Please log in to the CDN console, click Purge and Prefetch on the left sidebar, and then submit the URL for prefetch. For more information, please see Prefetch Cache.




Optimize the website architecture

Requests for dynamic resources are always forwarded to the origin server to pull the latest resources, slowing the access speed. If your website has many dynamic resources, we recommend separating them from static resources and using CDN for your static resources only.

Help and Support

Was this page helpful?

Help us improve! Rate your documentation experience in 5 mins.

Feedback