DynaBlogger is designed to optimise the performance of your website out of the box, without additional tools.
In order to deliver pages to the client as quickly as possible, all pages are automatically cached. In short, this means that copies that are ready to use are served instead of having to rebuild the page at each page view. This alone can make a significant difference in perceived responsiveness due to shorter response time when downloading the document.
The cache is automatically invalidated whenever you make changes to either the content or the theme in use with your blog, so that these changes can be effective immediately. The cached (and faster) copy of the page is then rebuild when the page is requested at the next occurrence.
Cache invalidation happens automatically, however you can invalidate the cache at any time by clicking on "Invalidate cache" in the Tools section of the admin area.
Because the cache is rebuilt when pages are requested for the first time following some changes, you may wish to "preload" the entire site in advance, to minimise the likelihood that a visitor may experience a slower page load. You can do this by clicking on "Preload site" in the Tools page.
All static assets both for themes and images attached to articles are served by a global CDN. This ensures that copies of these assets are served to your visitors more quickly from the nearest data centre, whenever possible. This happens automatically and doesn't require any additional configuration.
Additional notes on performance
We are planning to introduce some automatic optimisation for your images in order to reduce file size, which helps with loading times of your pages. However for the time being we recommend that you optimise your images in advance, before uploading them to DynaBlogger.
Number of partials and nesting
Partials are very handy and allow you to reduce duplication in your code and better organise it. You can even nest partials in partials, but a high number of partials involved in building a page can slow down the response time when the page isn't cached, meaning that for a few visitors the page may load more slowly. We encourage the use of partials in your themes but we recommend not to use dozens of them on each page for performance reasons.