a React app on a fast network can download in as little as 100ms, but then take another 600ms to render... unless it's server-side rendered (then <= 250ms)
Our experiments demonstrate that slowing down the search results page by 100 to 400 milliseconds has a measurable impact on the number of searches per user
- from Google Research blog post "Speed Matters"
Google saw a 20% drop in revenue from an accidentally introduced 500ms delay.
Using XHR/AJAX? We automatically cache and preload AJAX calls so the "initial state" just works. If you have a more complicated setup, you can preload your state by saving to a special variable we serialize into the DOM called
Using React? We include your server-side rendered checksums for best possible client render performance. (version 0.14 and above)
We've tested hundreds of apps and addressed many requirements:
Test Headless-Render-API.com in seconds with our server and let us know if you need a particular feature or guidance.
It's easy, just add middleware or a snippet to your web server that forwards requests to service.prerender.cloud
We've already written and tested integrations with Node.js, nginx, CloudFront via Lambda@Edge, Apache, Golang, Ruby, IIS and can quickly add more. Just email us: firstname.lastname@example.org
?text) TL;DR: it's for demoing the product.
?textquery parameter tells service.headless-render-api.com to change the
text/plainwhich allows you to see the actual generated HTML. If you remove that query parameter, HTML will be returned in the browser, which means the browser will try to load relative paths against service.headless-render-api.com, which won't work. This is only relevant when demoing the product. In production, your server will use middleware to access service.headless-render-api.com and relative paths will be accessed against to your domain.
npm install -g prerendercloud-server prerendercloud-server --help prerendercloud-server ~/path/to/build