Kadira - Performance Monitoring for Meteor (you should try this)

Introducing Fast Render

Meteor is supercool when it comes to productivity and building real-time web apps very quickly. But one of the common issues with Meteor is page load time: you have to wait until a WebSocket connection is made and data comes from the server. This is a crucial issue for many apps, especially forums, blogs and public-facing web apps.

Server Side Rendering (SSR) is the solution for this issue. It will render the initial page on the server, it works well with Search Engines, and it does not require PhantomJS (which is how Meteor currently supports Search Engines). However, SSR is not expected to be comes with Meteor 1.0. (But you can expect it sometimes later).

Meet Fast Render

Fast Render is not an SSR, but it is very similar and performs the same functionality very efficiently.

What Fast Render does is pretty simple. It sends the data required to render your first page with the initial HTML loaded from Meteor, so the page is rendered just after the JavaScript is loaded to the client. No more waiting!

However, Fast Render does not help much with SEO and does not change how Meteor deals with SEO.


Let’s try a demo to see what Fast Render can do. I have added Fast Render support to Telescope so you can see the difference below.

For more information on the comparison, see the video below.

Simple Integration

Fast Render does all the hard work for you. All you have to do is specify which data and subscriptions need to send to the client with the HTML. You can do that with a simple API. See the example below:

First add Fast Render to your Meteor app

meteor add meteorhacks:fast-render

// for older Meteor versions (< 0.9) 
mrt add fast-render

Fast Render has been deeply integrated with Iron Router. With just a few steps, you can power your existing Meteor App with Fast Render. Here’s all you have to do:

  1. If you are extending from RouteController, extend it from FastRender.RouteController
  2. If you are directly using routes, use fastRender:true as shown here.
  3. Then bring your route definitions to a place that can be seen by both the client and the server.
  4. Make sure, waitOn() does not contains any client specific code. If you have such, guard them with Meteor.isClient

Fast Render supports more IronRouter integration methods, as well as the ability to integrate without IronRouter. Please refer to the documentation for more information.

Try it Out

Don’t take my word for it. Try it out with your app: I bet you’ll love it. I’d also love to hear your thoughts about Fast Render and this is the first project comes with the new MeteorHacks.

Sign Up with this Newsletter to get FastRender specific updates once they’ve been released