Why PageCDN? What problem does it solve?
PageCDN accelerates 3 different types of Content: Public (open-source), Private and Shared, through a single
pagecdn.io that consolidates all the content and does maximum use of single HTTP/2 connection
and content parallelization and saves many DNS lookups. With this approach, PageCDN has the potential to
provide superior performance than any other CDN.
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 these optimizations to their websites.
A fast CDN is really not useful if it has to load 10s of MBs of images and other files for every pageload.
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 upto 90% in some cases).
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
When a compressible file is received at PageCDN, it is compressed with brotli that takes significant time
for the first run, but can greatly reduce file size. So, 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, and saves user's bandwidth.
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 & JS 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.
Content Optimizations offer the most speedup a slow website can get. But thats 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
HTTP/2 & Host Consolidation
Domain Sharding was once a very common approach to parallelize the resource delivery and bypassing browser's
connection limits. 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 to
split large files to many small files
(over HTTP/2 or HTTP/3) for certain optimizations.
If a website loads files from multiple hosts like Public CDNs, Private CDN, Google Fonts, hosted widget, etc,
it makes the worst use of the content parallelization capabilities of HTTP/2 in addition to the extra DNS
lookups that it has to generate and connections it has to make before starting to fetch resources. This
extra work the browser has to do is reflected in
decreased website performance on mobile
PageCDN helps you consolidate all the Public and private content over single host so that browser can
request for it in parallel. PageCDN solves this problem by facilitating fonts, open source libraries and
themes; commercial libraries, widgets and themes; and your private files over a single CDN, and where
possible, avails the caches already created for the Public/Shared resources when they were delivered to your
users while they were visiting other websites. It also facilitates connecting to multiple different origins
(Github, websites, or other CDNs) and caching the content near end-user for best performance.
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.
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 redirects to some other location, PageCDN internally resolves the redirection
and gets the final resource. This can speedup websites facing low performance score due to redirection
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
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
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 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.