Hacker News Reader

Shameless plug, but if you care about web performance, my startup, https://rasterize.io provides easy frontend performance monitoring. It tells you how fast users load your site, broken down by desktop vs. mobile, and geography. You can view most of the chrome devtools waterfall information, for every (modern) visitor.

View on HN

What's the page load overhead in adding this for each user?

It's an 8kB async-loaded JS script, and then it posts a small (1kB) amount of data back to my servers. Overhead should be tiny, and it's async so it won't block page rendering.

Looking at your source. You are using the timing API to get RUM data. How is your JS different/better than just using Boomerang to get those metrics?

Reply on news.ycombinator.com