
Wildcard purge now available to push and pull zones
We are happy to announce that PUSHR's cache purge feature has now been extended to support wildcard purging. With wildcards…
We are happy to announce that PUSHR's cache purge feature has now been extended to support wildcard purging. With wildcards…
One of the things about PUSHR that we pride with is that we don't blindly follow the trends just to…
We've been receiving some criticism for some time regarding our website being slow which, let's be honest, is not a great self-advertising for a CDN service. PUSHR CDN does not advertise website acceleration at all among the services that we offer as that is not our specialty, and our website was not accelerated by our CDN. Since a redesign was due, we've decided to host the new website directly on our CDN network and see where this goes in terms of speed, especially compared to other CDN services that claim to specialise in website acceleration.
One of the main ways for a content delivery network to accelerate a piece of content is to cache it on an edge server in close proximity to the visitor. Once cached (usually after the first request) the content is served to all visitors at high speed, without the need to contact the origin, which may be physically located in a distant country or even on another continent. This greatly accelerates the rate at which visitors can fetch a copy of your content and it also allows you to scale seamlessly since all the load from the origin is shifted to the CDN.