DynaBlogger is designed to optimize the performance of your website out of the box, without additional tools or services.


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 from scratch with each page view. This alone can make a significant difference in perceived responsiveness due to shorter "time to first byte" (TTFB) 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 seen immediately. The cached (and faster) copy of the page is then rebuilt when the page is viewed the next time, automatically.

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 soon after a change to the theme or some content is made. You can do this by clicking on "Preload site" in the Tools page.


All static assets for themes as well as images attached to articles are served by a global content delivery network (CDN). This ensures that copies of these assets are served to your visitors more quickly from the nearest data center, whenever possible. This happens automatically and doesn't require any additional configuration from your part.

Additional notes on performance

Image size

Whenever you upload an image, some optimizations are performed automatically in order to reduce file size (such as limiting the resolution to 3840x3840 pixels), which helps with loading times of your pages. 

Number of partials and nesting

Partials are very handy and allow you to reduce duplication in your code and better organize it. You can even nest partials in other 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 one visitor the page may load more slowly after some changes are made. We encourage the use of partials in your themes but we recommend not to use too many of them on each page for performance reasons.