Re:Google Seeks to Pacify Consumers with Faster Mobile Pages
by arohner on Wednesday February 24, 2016 @01:23PM
(#11168919)
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.
[ Parent
| on HN ]
Re:Google Seeks to Pacify Consumers with Faster Mobile Pages
by untog on Wednesday February 24, 2016 @02:23PM
(#11169432)
What's the page load overhead in adding this for each user?
Re:Google Seeks to Pacify Consumers with Faster Mobile Pages
by arohner on Wednesday February 24, 2016 @03:21PM
(#11169929)
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.
Re:Google Seeks to Pacify Consumers with Faster Mobile Pages
by billyhoffman on Wednesday February 24, 2016 @04:29PM
(#11170381)
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?