Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11To clear a CDN cache in hPanel, open Websites → Dashboard → Performance → CDN for the site and click Flush cache. On Agency hosting, select CDN directly in the sidebar. The flush clears cached copies for the whole website, not just one page, and takes effect within seconds. It clears only the CDN layer; other caches may still serve older content.
Flush the CDN cache in hPanel
- Sign in to hPanel and open Websites.
- Click Dashboard beside the website you want to update.
- Choose Performance → CDN in the sidebar. On Agency hosting, choose CDN directly.
- Click Flush cache.
The action invalidates cached copies for the entire website within seconds. It does not offer a URL-only flush through this procedure.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
CDN A Visual Guide: CDN Fundamentals for Beginners and New Systems Engineers: Practical Knowledge... | $8.00 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
Check whether the CDN served a cached response
In your browser’s developer tools, open Network, select the page or file request, then inspect Response Headers for x-hcdn-cache-status. You can also review CDN Analytics. The status indicates how the CDN handled that response:
- HIT: The response came from CDN cache. Flush the CDN or use Development mode while editing.
- MISS: The request fetched content from the website rather than serving a cached copy. Make another request to see whether the response is cached afterward.
- EXPIRED: The cached copy expired and was fetched again.
- DYNAMIC: The response is not cacheable.
- BYPASS: The CDN cache was skipped, for example while Development mode is enabled.
- REVALIDATED: The cached content was refreshed.
A first request after a flush may show MISS or DYNAMIC. If it shows MISS, repeat the request to check whether a subsequent request becomes a HIT. If the status is DYNAMIC or MISS but the page still looks old, check other cache layers before blaming the CDN.
Use Development mode while making ongoing changes
Development mode tells the CDN to skip its cache and fetch content from the website on each request. It is useful while actively editing, but turn it off when you finish so the CDN can cache content for delivery. It does not disable browser, server, or plugin caching.
Know what the CDN caches
Different behavior applies to static files and HTML. Whether a particular response is cached depends on its content and cache headers.
- Static files: Images, CSS, JavaScript, fonts, and downloads are cached by default for up to two hours, or for the duration specified in the site’s cache headers.
- Optimized images: On web hosting, WebP or resized images are cached by default for up to 30 minutes, subject to the original image’s cache headers.
- HTML on web hosting: HTML is fetched from the hosting server on each request unless the site marks it cacheable; HTML is DYNAMIC by default.
A response with Cache-Control: public and max-age or s-maxage can be cached for the stated duration. Directives such as private, no-store, or no-cache keep a page out of CDN cache. WordPress login cookies and WooCommerce cart or session cookies bypass the cache.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →LiteSpeed Cache can mark public pages cacheable for the plugin’s configured public-cache lifetime. The plugin default is seven days, or max-age=604800. Changing that TTL affects pages cached afterward; flush the CDN as well to apply the new setting to pages already cached.
If the page is still outdated, clear the other cache layers
A CDN flush does not purge your browser, LiteSpeed server cache, or WordPress caching plugin. Work through the layer that may hold the stale copy:
Browser cache
Open the page in a private or incognito window, or hard-refresh it with Ctrl+Shift+R on Windows or Cmd+Shift+R on Mac. If the private window shows the update, the original browser session likely retained an older copy.
LiteSpeed server cache
In the website dashboard, open Cache Manager and purge the cache. This controls the LiteSpeed web server cache, separate from the CDN. Cache Manager can purge the whole site or a specific URL.
WordPress plugin cache
Use the active caching plugin’s own purge control. LiteSpeed Cache purges usually clear CDN pages too, but if the update remains missing, flush the CDN as a separate step. Keep only one WordPress caching plugin active.
No-cache preview
A no-cache preview in hPanel bypasses applicable LiteSpeed, CDN, and server-side cache layers. If the preview shows the update, a cached copy is likely involved.
Another CDN
If the website uses a third-party CDN, clear its cache from that provider’s dashboard. The hPanel CDN procedure above applies specifically to the CDN available through hPanel.
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.
Free tools Windows power users keep installed
One-click scans. No signup required.
