Features & Optimizations

We have designed PageCDN from ground up to remove bottlenecks in the performance of modern websites and to allow business owners with low technical background to easily apply advanced optimizations to make their websites upto 10X faster.

To make websites faster than ever, PageCDN performs several optimizations categorized as:

Content Optimizations

A fast CDN is really not useful if it has to load 10s of MBs of images and other files for every page load. Client's connection speed matters even more than the latency savings that CDNs offer. PageCDN offers many content optimizations that help improve site speed significantly (by up to 500% in some cases) in addition to the reduced latency benefits that PageCDN as a CDN can offer.

Brotli-11 Compression

Brotli is state-of-the-art compression algorithm designed by Google 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 27% compared to common compression implementations.

PageCDN uses Brotli:11 or Brotli compression level 11 that compresses contents much better than common Brotli or Gzip compression level implemented by CDNs and webhosts. When a compressible file is requested for the first time, it is compressed with Brotli:11 that takes significant time for the first run, but can greatly reduce file size. We do the compression only once. This pre-compressed file is re-used for every subsequent request, eliminating the overhead and latency added by on-the-fly compression, saves user's bandwidth and speeds up website by a big margin. Small files are also less likely to be affected by bad network conditions.

URL Based Image Optimization & Resizing

Images make up a big proportion of today's page contents. Optimizing images for the web is really as important as it is to deliver the content fast.

PageCDN optimizes and resizes images on-the-fly, and saves you the hassle of optimizing or resizing images manually or through a 3rd party API and maintain multiple copies of resized and optimized images on your server. With this feature, everything works through URIs and does not require any configuration. You just specify a few hints in the URL of the file to indicate your intention to optimize and/or resize the image (without changing actual file name on the disk) and leave everything on us. More information on this feature is available in docs.

URL Based CSS & JavaScript Minification

Minifying CSS and JS can significantly reduce the time to First Contentful Paint of a webpage on user's screen. PageCDN makes it easy to minify selective CSS or JS files without going through any configuration or big code changes. More information on this feature is available in docs.

Delivery Optimizations

Content Optimizations offer the most speedup a slow website can get. But that's not all. Delivery optimizations help you reduce the time wasted in requests handling and delivery process. For better results, PageCDN allows you to optimize the content delivery process too, and fortunately, PageCDN has a lot to offer.

Global Edge Network

PageCDN creates copies of pre-optimized, compressed and minified content of your website at locations near users. When the same user or any other user in the same region requests the file, PageCDN serves it immediately from its point of presence in that region. This reduces the time the browser has to wait before it starts processing its content to display on the screen. This makes your websites snappier and improves customer experience on your site.

HTTP/2 & Host Consolidation

Domain Sharding is a very common approach to parallelize the resource delivery and to bypass browser's connection limit. However, with HTTP/2 transfers can be parallelized over single connection. HTTP/2 is so important for the performance of a modern website that browser developers even recommend splitting large files to many small files (over HTTP/2 or HTTP/3) for certain client-side optimizations to fully work.

PageCDN takes this even further and uses Host Consolidation technique to leverage HTTP/2's capabilities to parallelize different content from different origins (GitHub, public CDN, your websites, object storage, push storage, etc) over single connection and removes the performance impact of DNS lookups, TCP connections and other overheads for mobile users. With this approach, PageCDN has the potential to significantly speedup your websites. You can read more about host consolidation here.

HSTS Preloaded

PageCDN is always HTTPS and secure even if you try it not to be. PageCDN is on HSTS preload list of all top browsers, which means your files always load over HTTPS whether or not you explicitly ask the browser to do so.

This helps with security and privacy, but also helps with performance. Browsers treat the same file delivered over HTTP and HTTPs as two separate resources and does not reuse the HTTPS cache for HTTP requests and vice versa. Having the resources to load over only single URL prevents cache misses if you incorrectly link to a file on some pages to load over HTTP instead of HTTPS. This also avoids mixed content issue that is commonly found on many websites that migrate to HTTPS from old HTTP. This feature enables full transport security and ensures no resource can slip through to the browser without going through the secure channel.

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.

HTTP/2 Server Push allows to proactively send files to the browser before the browser even asks for them. 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 specify a file that pushes additional files to the browser, and PageCDN does the technical part for you. The entire process is easy, and makes your site fast with very little effort.

Redirects

PageCDN resolves redirects at CDN level so that if the browser asks for a file, PageCDN gets it the file. If the Origin server asks to redirect to some other location, PageCDN internally resolves the redirection and gets the file. This can speedup websites facing low performance score due to redirection chains.

Cache Optimizations

Once a static file has reached the browser, it must be available for reuse to save hosting bills and to save bandwidth cost the user has to bear. PageCDN offers many different ways to improve cache hit ratio for best results.

Immutable Cache

This is relatively new feature of the web, and PageCDN supports it to allow you to set Immutable Cache Control header to tell the browser that a specific file does not change at all. Browser uses this information to optimize future website visits of the same user.

URL Based Cache Invalidation

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 features 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 Cache-Control: Immutable without loosing control over changes, and results in extremely fast load times for your repeat visitors as the entire layout content can be loaded from browser cache.

PageCDN allows you to purge files manually through a User Interface, and also through API. But this is not all. You can use URL based cache invalidation feature that supports slightly changing the URL in case the file changes, without the use of query strings. This allows you to use aggressive cache control with your files without worrying about the file updates because as you make changes, cache-invalidator will help you invalidate existing edge and browser cache and safely deliver new resource to the user.

Similarly, the resources pulled from github support version tags to properly invalidate cache of old version files.

Shared Browser Cache

Public CDN allows many websites to share the same resource. This non-only offers free bandwidth and the option to automatically load the latest versions as they are made available, minifies files if the library itself does not provide minified releases, optimizes or resizes any images on demand provided by the library, but also allows websites to share the HTTP cache of the same resource. This makes it possible to load your website very fast for even first time visitors if some of your website resources are already available in browser cache of another website that the user visited.