What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
To confirm Hostinger CDN is working, check that it is enabled in hPanel, then verify the response headers in your browser’s developer tools. For a static image or CSS file, look for x-hcdn-request-id and a repeat-request x-hcdn-cache-status: HIT. Hostinger CDN mainly helps deliver cacheable static files; it does not automatically speed up server-side code, database queries, or every page load.
How to check whether Hostinger CDN is active
A dashboard setting shows that CDN is configured. Response headers show whether a particular request actually passed through Hostinger’s CDN and whether a file came from its cache.
- In hPanel, open Websites → Dashboard → Performance → CDN and confirm the CDN is enabled.
- Open your site in a browser, then open developer tools and select the Network tab.
- Reload the page and select a static asset request, such as an image or CSS file. Inspect its response headers.
- Look for
x-hcdn-request-id. Hostinger says this indicates the request passed through its CDN. - Check
x-hcdn-cache-statuson the static asset. A first request may showMISS; reload and inspect the same file again. A repeatHITis evidence that the file is being served from cache. Hostinger’s verification guidance is in its CDN status guide.
For a fair check, compare the same asset across repeated requests. If possible, test from a location farther from your hosting server: edge delivery is more likely to matter when the visitor is geographically distant from the origin.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →What Hostinger CDN speeds up—and what it does not
Static files and image delivery
Hostinger says its CDN caches and serves static files—including images, CSS, JavaScript, fonts, and downloads—from CDN servers near visitors. Its listed features also include image optimization, compression, TLS 1.3 connection setup, and HTTP/3 for sites using their own domain. The potential benefit is most relevant when these assets are a meaningful part of the page’s loading time. See Hostinger’s CDN feature overview.
HTML and server-side work
Server-generated HTML is fetched from the hosting server on each request by default. Hostinger says HTML can be cached if a site marks it publicly cacheable; requests involving logged-in users or carts are bypassed. A CDN does not itself make plugins, themes, application code, or database queries execute faster. If the HTML response is slow because the origin server is doing work, delivering static images from an edge server may not fix that delay. Hostinger explains caching behavior in its CDN overview and CDN FAQ.
How to interpret the cache-status header
| Header value | What it indicates | What to check |
|---|---|---|
MISS |
The requested file was not served from cache on that request. This can happen on the first request after enabling the CDN or clearing its cache. | Reload and inspect the same static file again; look for a repeat HIT. |
HIT |
The file was served from Hostinger’s cache. | Confirm the request also has x-hcdn-request-id if you are verifying Hostinger CDN routing. |
BYPASS |
The request bypassed the cache; Hostinger identifies Development mode as one possible reason. | Turn off Development mode when you are no longer editing the site, then test again. |
DYNAMIC |
The response was not cached. This is normal for non-cacheable HTML or private, session-specific requests. | Test a static asset separately; do not expect private or dynamic responses to behave like cacheable files. |
Hostinger’s CDN FAQ lists default cache durations of up to two hours for static files and up to 30 minutes for optimized images on web hosting. These are cache durations, not promises about how much faster a site will load. The same FAQ gives LiteSpeed Cache’s stated default public page-cache lifetime as seven days (max-age=604800); that is a separate page-cache setting, not the CDN’s measured speed gain.
What to do if Hostinger CDN does not appear to be working
No Hostinger request header appears
If hPanel says the CDN is enabled but requests do not show x-hcdn-request-id, check whether DNS changes have propagated, whether the domain uses Hostinger nameservers, and whether a proxy such as Cloudflare sits in front. Hostinger says its CDN requires Hostinger-managed nameservers/DNS to route the domain. Its nameserver instructions explain how to change nameservers.
Rank #2
A static file keeps showing MISS
Repeat the request and inspect the same asset. A miss can be expected while the cache is being filled; compare later requests rather than treating the first response as proof of a failure.
Both Hostinger and Cloudflare headers appear
If both x-hcdn-cache-status and cf-cache-status appear, Hostinger identifies this as a double-CDN setup. Hostinger recommends using only one active CDN for a website. Cloudflare uses its own dashboard and nameservers, while Hostinger CDN is managed in hPanel and requires Hostinger nameservers; choose the setup that fits your DNS and existing proxy configuration. Before changing nameservers, account for all DNS records, including email MX records and verification TXT records. See Hostinger’s CDN FAQ and nameserver guide.
Updated content still looks stale
Flush the Hostinger CDN cache, then clear other relevant layers separately, such as your browser cache or a server or plugin cache. A Hostinger CDN flush clears only Hostinger’s cache layer; it does not clear every cache used by your site.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Why an enabled CDN may not improve your page-load results
Measure the same page more than once and inspect both a static asset and the HTML document. A cached image or stylesheet may show a repeat HIT while the HTML still requires origin-server processing. That distinction helps explain why CDN delivery can be working even when a page’s overall loading time changes little.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →- If images, scripts, or stylesheets dominate the delay, edge delivery or image optimization may help those parts.
- If server processing, database work, or render-blocking scripts dominate, CDN activation alone may not improve the result.
- Do not infer a specific Lighthouse or PageSpeed score change from the CDN status. Hostinger does not publish a representative numeric site-speed uplift in its reviewed guidance, and an enabled CDN does not guarantee a particular percentage improvement.
Is Hostinger CDN included with your plan?
Availability and controls depend on the hosting plan and account. Hostinger’s current plan information says CDN is included on eligible hosting plans. Its guide says eligible web-hosting sites began automatic activation in August 2026, with an email notification before the change; it also says there is no separate CDN subscription or per-visit fee. Check your own hPanel and current plan details rather than assuming every site or account has the same eligibility.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
