Revise your origin to find errors or misconfigurations that may affect the content delivery speed. Contact your hosting provider or server administrator for help in the case analysis.
1. Measure the content delivery speed from both a CDN-resource and an origin server using:
wget -S testsupport.cdn.com/files/test.jpg --2019-12-10 13:29:17-- http://testsupport.cdn.com/files/test.jpg Resolving testsupport.cdn.com... 188.8.131.52 Connecting to testsupport.cdn.com|184.108.40.206|:80... connected. HTTP request sent, awaiting response... HTTP/1.1 200 OK Server: nginx Date: Tue, 10 Dec 2019 08:29:17 GMT Content-Type: image/jpeg Content-Length: 290 Connection: keep-alive Last-Modified: Fri, 06 Dec 2019 10:12:14 GMT ETag: "5dea297e-122" Set-Cookie: 48c62c809b061c360cc201975b7fa802 Cache: MISS X-ID: fr5-up-gc22 Accept-Ranges: bytes Syntax error in Set-Cookie: 48c62c809b061c360cc201975b7fa802 at position 32. Length: 290 [image/jpeg] Saving to: 'test.jpg' test.jpg 100%[=================================================>\] 290 --.-KB/s in 0s 2019-12-10 13:29:18 (5,38 MB/s) - 'test.jpg' saved [290/290]
2. Compare the delivery speed from CDN and the origin server.
3. If the analysis confirmed issues with content delivery speed from CDN, revise CDN-resource's settings.
1. Make sure that you don’t use a VPN or proxy.
VPN affects the CDN Geobalancing and you may receive content from a not optimal edge with lower speed.
If you revised your CDN resource's settings but are still unsatisfied with the download speed, contact technical Support and provide the following information:
http://iam.gcdn.co/info, copy all information from the page or save a screenshot.
Was this article helpful?
Learn more about our next-gen CDN