rndr.me is a tiny http server that eats urls and poops html. It has only one dependency, PhantomJS, which it uses evaluate each incoming url in a headless browser window, and output the html of the resulting DOM.
Single-page apps suffer from poor crawlability, because Google/Bing are less likely to discover content rendered on the client. In this case, use rndr.me to render the
_escape_fragment_urls that these crawlers want, by redirecting from your backend.
Single-page apps suffer from slow startup times, due to multiple round trips between the app and API. In this case, you can use rndr.me to pre-render hot pages, so that they can be inlined as HTML to improve perceived performance.
Of course, this is just one approach for folks looking for way to improve SEO and performance when rendering single-page apps. If you're using Backbone.js and want a more tightly coupled solution, check out @airbnb's rendr. If you're looking for something a bit higher-level that'll run a cluster for you, check out @bfirsh's otter.
In this example shell script, we:
- serve it on port 8000,
- run rndr.me on port 8001, and
- verify the app html as rendered by rndr.me.
Quickstart on Heroku
# Create a place for your renderer to livemkdir my_renderercd my_renderer# Create a git repo with rndr.me and a Procfilegit initgit submodule add git://github.com/jed/rndr.me.gitecho "web: phantomjs rndr.me/server.js" > Procfile# Create a new Heroku app with the PhantomJS buildpackheroku apps:createheroku config:add BUILDPACK_URL=https://github.com/stomita/heroku-buildpack-phantomjs.git# Push your codegit add .git commit -m "first commit"git push heroku master# Scale your appheroku ps:scale web=1
To spin up the server, run the following from the command line:
phantomjs ./server.js <config-path>
config-path is optional, and if omitted will default to the provided config.js file. You may also override any options from the config file using options on the command line:
phantomjs ./server.js --port 8002 --ready_event onRender
The server exposes a single root endpoint at
/. It returns generated html, based on the following parameters:
href: The url to be rendered. This is required, and must be fully qualified.
max_time: The maximum number of milliseconds until render. Any windows not already rendered by the
ready_eventwill be rendered once this elapses. This is optional, and
30000by default (30 seconds).
max_bytes: The maximum number of incoming bytes. Any windows that load more than this value will return an error without rendering. This is optional, and
1048576by default (1 MiB).
load_images: This can be specified to any value to load document images. This is optional, and omitted by default.
ready_event: This is the name of the
windowevent that triggers render. This is optional, and
loadby default. To specify when rendering occurs, such as when the DOM is not ready to be rendered until after
window.onload, trigger a DOM event manually, such as follows (using jQuery in this case):
The following examples assume a single-page app running in production at
http:/myapp.com and rndr.me running as follows:
phantomjs ./server.js --port 8080
Let's render the app with default settings:
curl localhost:8080 -G \--data-urlencode 'href=#!home'
Now let's cap the maximum rendering time at 10 seconds:
curl localhost:8080 -G \--data-urlencode 'href=#!home'-d max_time=10000
We can also cap the maximum incoming bytes at 100KiB:
curl localhost:8080 -G \--data-urlencode 'href=#!home'-d max_time=10000-d max_bytes=102400
Now let's allow images to load, raising the maximum incoming bytes to 500KiB:
curl localhost:8080 -G \--data-urlencode 'href=#!home'-d max_time=10000-d max_bytes=512000-d load_images
Now let's use the custom rendering event
render_ready, triggered on the window of the DOM, using the default fallback maximum time:
curl localhost:8080 -G \--data-urlencode 'href=#!home'-d max_bytes=512000-d load_images-d ready_event=render_ready
(The MIT License)
Copyright (c) 2013 Jed Schmidt <email@example.com>
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.