Runtime Page Optimizer (RPO): Performance optimization on the fly

Steve Souders posted about a new tool “Runtime Page Optimizer (RPO)” that runs on a web server applying performance optimizations to pages at runtime, just before the page is sent to the browser. RPO automatically implements many of the best practices from “High Performance Web Sites” book and YSlow. Here’re the performance improvements RPO delivers: minifies, combines and compresses […]

Steve Souders posted about a new tool “Runtime Page Optimizer (RPO)” that runs on a web server applying performance optimizations to pages at runtime, just before the page is sent to the browser. RPO automatically implements many of the best practices from “High Performance Web Sites” book and YSlow. Here’re the performance improvements RPO delivers:

  • minifies, combines and compresses JavaScript files
  • minifies, combines and compresses stylesheets
  • combines images into CSS sprites
  • inlines images inside the stylesheet
  • turns on gzip compression
  • sets far future Expires headers
  • loads scripts asynchronously

RPO reduces the number of HTTP requests as well as reducing the amount of data that is transmitted, resulting in a page that loads faster. In doing this the big question is, how much overhead does this add at runtime? RPO caches the resources it generates (combined scripts, combined stylesheets, sprites). The primary realtime cost is changing the HTML markup. Static pages, after they are massaged, are also cached. Dynamic HTML can be optimized without a significant slowdown, much less than what’s gained by adding these performance benefits.

More infoRPO

Source:→ Ajaxian