PageCDN improves your website's performance with state of the art features never offered before by any CDN
Push and Pull CDN
Push CDN works like a server where you manually upload (or push) your files. The files so uploaded are optimized and stored by the CDN. Later on these files are distributed to edge servers for faster delivery. You can then use URLs of those uploaded files on your website. When a browser requests such file, request is received by an Edge servers that looks up the file in cache or storage and sends it back to the browser (reducing the overall delivery time).
Pull CDN automates the file uploading process. It starts with empty storage and cache, but when a file is requested by the browser, it pulls it from your website. The contents so pulled are optimized, stored and cached by the CDN and then distributed to the Edge Servers. The next time when the same file is requested by the browser, it is already available at the Edge Server for faster delivery.
PageCDN accumulates features of Pull and Push CDNs. You can setup a repo to accept manual uploads, or to pull content from your website. Thats not all. You can even setup a repo to pull content from your github repos or even pull from another CDN. PageCDN provides easy to use interface for linking the files in your repos from your web pages.
* Repo is storage for a single website (or origin). You can setup multiple repos with different configurations to accumulate and optimize content from single or multiple websites or origins.
Public, Private & Shared CDN
Public CDN maintains and hosts a public directory of opensource libraries that are used for web development purposes. A Private CDN on the other hand privately collects, maintains and delivers private files of a website. These private files can be user content, website's layout files, or anything else. Shared CDN, on the other hand, allows you to share your CDN hosted content with others for direct linking and use.
PageCDN allows you to create Private and Shared repos, while the Public content is made available for free for everyone's use. You can create Private repos to privately optimize content for your website, or you can create a Shared repo that can be shared with your friends, fellows or clients.
Free Snippets CDN
A snippet is a small block of code, limited to 3 KB in size, that is uploaded for the purpose of sharing and embedding in blog posts and articles. PageCDN offers Snippets CDN so that these snippets can not only be shared and embedded on discussion sites, but also the viewers of these sites can grab snippet's CDN link and directly use at their websites easily without any problem.
Snippets CDN is totally free. You can create unlimited snippets and share with others. PageCDN takes care of the bandwidth costs and accelerated delivery.
Aggressive/Immutable HTTP Caching
Traditionally, if you want to use long lasting HTTP caching, you need to have some cache busting mechanism that helps bypass browser cache and forces a browser to issue request for fresh contents when a file has changed. However, if you do not have such mechanism, PageCDN can do it for you.
PageCDN offers different versioning or cache busting mechanisms to allow you to easily bypass cached files
and to force browsers to issue request for fresh content when a file changes. This makes it possible to use
without loosing control over changes, and results in extremely fast load times for your repeat visitors as
the entire layout files can be loaded from browser cache.
Brotli Level 11 Compression
Brotli is state of the art compression algorithm designed specifically for Internet for serving compressed content over encrypted connections (HTTPS). Although HTTP Compression is around for 20 years, Brotli is a new player in the market that can reduce the content size by another 26% compared to other popular compression algorithms.
When a compressible file is received at PageCDN, it is compressed with brotli that takes significant processing power, but can greatly reduce file size. Compression only occurs once. This pre-compressed file is delivered for every subsequent request, eliminating the overhead and latency added by on-the-fly compression.
Reuse 3rd Party Websites' Browser Cache
Many websites use PageCDN's Public CDN for free and faster content delivery. These files are cached by the browsers for long periods. When the visitor opens the same page or other pages on the same site, the resource is loaded from browser's cache in no time and so the pages load very fast for repeat visitors.
However, the benefits do not end here. You can leverage your website's performance by reusing the same files from PageCDN's Public CDN on your site. This effectively loads your website as fast for new visitors as it should do for the repeat visitors since your website is now in the position to reuse the cached copy of resources already available in the browsers. In other words, this allows websites to share browser cache for their mutual good. Thats why we collect and host as much opensource and commercial projects as we can so that more and more of the layout content is available for reuse by websites that will help with even more cache sharing across websites.
Similarly, you can also create a Shared repo in your account and share with others. Bandwidth cost of creating Shared repo is borne by the creator of the repo.
Easy to Use HTTP/2 Server Push
Traditionally content could be served by a CDN only if it is requested by the browser. With HTTP/2 Server Push, it is now possible to push the content to the browser before the browser requests it. This can dramatically speed up content delivery for websites.
However, using HTTP/2 Server Push can be tricky and difficult as some hosts do not yet support HTTP/2. For this reason, PageCDN allows you to easily configure server push through web interface. You can choose which file triggers server push event, and which files are pushed to the browser. The entire process is easy, and makes your site very fast with almost no extra effort.
Better Security and Cache Hits with HTTPS
Some websites load the same resources inconsistently and alternatively over HTTP and HTTPS on different pages site-wide. Although it may have some security implications, on the surface it looks fine for website performance - but its not. HTTP and HTTPS URLs for the same resource are considered two separate resources by the browser and cached separately. This causes extra cache misses and forces the browser to request a resource from the server even when the same resource is already available in its cache with slightly different URL.
The same practice is followed by many other CDNs too that allow users to choose between HTTP and HTTPS URLs. PageCDN allows only secure HTTPS URLs. This not only increases security, privacy and consistency across your websites, it improves client side cache hit ratio too. Further, this makes Public CDN even powerful as all the sites that rely on the Public CDN are better able to share browser cache with each other.
Using HTTPS secured URLs also allows you to enhance performance of resource delivery through the use of HTTP/2 as all modern browsers support HTTP/2 over only encrypted connection.
Faster Content Delivery with Better HTTP/2 Utilization
As Public and Private CDNs are getting more and more popular, many web developers are starting to adopt them in their web projects in a way that makes it less optimal - and in some cases we observed that the use of CDN was actually making their sites slow.
Many websites load opensource files over multiple Public CDNs (like separate CDNs for jQuery, bootstrap, fontawesome, etc in hope for optimal file delivery) and Private files from private CDNs, and fonts from a separate fonts CDN (like Google Fonts). This not only adds several extra DNS look ups that are blocking in nature, but also require the browser to open several connections to different hosts. Even if these HTTP transactions are done over HTTP/2, it looses the benefits of HTTP/2 multiplexing.
In contrast, if all such files are hosted on the same CDN that supports Public and Private CDN, like PageCDN, not only several redundant DNS lookups can be saved, but also all the files can be multiplexed over single connection for faster loading. This can further be sped up with HTTP/2 Server Push, faster content delivery from edge servers and client side cache sharing.
PageCDN also provides Easy Fonts library that provides all the fonts from Google's Public Github repo, and provides developers with easy to use CSS files and class selectors to load fonts in their websites. This not only makes the fonts easier to use, but also loads them over the same multiplexed connection that is used for other files, making the overall experience better for your customers.