CDN and origin speed comparison
Compare the same static file under consistent test conditions so differences reflect the delivery path rather than the client, location, or object.1
Select a static file
Select one static file that is available through both the CDN URL and the origin URL.
2
Test CDN delivery
From the test client and location, request the file through the CDN:Confirm that the response includes the
Cache: HIT header, which indicates that the file was served from the CDN edge cache.3
Test origin delivery
From the same client and location, request the same file directly from the origin:
4
Repeat and compare
Repeat both tests to reduce the effect of temporary network variation, then compare the transfer results. If CDN delivery remains slower, review the settings below.
CDN resource settings
Confirm that a VPN or proxy is not in use, because either can route traffic through a suboptimal edge and reduce delivery speed. Check the cache hit ratio in the Customer Portal:1
Open CDN
In the Gcore Customer Portal, navigate to CDN.
2
Open Statistics
Expand Reports and select Statistics.
3
Select the cache report
Select Cache hit ratio.
- The large file delivery settings enable Large files delivery optimization, which is incompatible with Fetch compressed, Gzip, and Brotli
- Gzip and Brotli reduce transfer size for compressible content and must be used without Large files delivery optimization in the same resource or rule
Diagnostic information for technical support
If delivery speed is still too low after reviewing settings, contact Gcore Support and include:- The file URL
- The JSON output from
https://gcore.com/.well-known/cdn-debug/json(open the URL and copy the full response) - Results from the Gcore speed test — click Run test, then save the result
wget -Soutput for both the CDN and origin URLs- A HAR file exported while loading the file or page. In browser DevTools, open the Network panel, reload the page, and select Export HAR