Hacker News Reader

Comment by yingw787 | Hacker News Reader

Wow, so cool! How does this compare to something like Google Chrome Lighthouse? I think there's a webapp: https://developers.google.com/speed/pagespeed/insights/

Is there any place we can sign up for updates on when the AWS migration is up and running?

View on HN

I wish we'd thought of that! Once we're in AWS we'll be posting research because we've created an internal tool to do large scale performance surveys e.g. comparing hosting providers or performance of sites using certain libs etc. So I'll put that on the blog and HN might pick it up.

FastOrSlow is built using Lighthouse. :) We do actual browser simulations using headless Chrome and lighthouse to get the performance data. We do it programmatically from all the locations, bring the data back and build the report.

I did think of one thing: You can follow us on Twitter at: https://twitter.com/isitfastorslow

With the positive comments here, perhaps the HN mods wouldn't mind if you posted an update yourself once the AWS migration is completed? I know there's rules around that, but I think they are okay with the occasional self-promotion, especially for great, free tools.

We would be more than happy to chat about how we migrated to AWS, the differences, benefits, down-sides, surprises. Will be a fun post. I'll let rbritton know and we'll put it together, and of course you can try the product too if you like. FastOrSlow has a blog, so we'll post it there.

You could also think about throwing someone to the back of the list is their browser hasn't pinged the server in a while.

Thank you for the tool and the details you've shared! Is there any particular reason you opted to run your own instances of Lighthouse rather than use the PageSpeed Insights API provided by Google? API quota limitations, perhaps?

This is hilarious

https://developers.google.com/speed/pagespeed/insights/?url=...

Saved you a click, the result is:

Lighthouse returned error: ERRORED_DOCUMENT_REQUEST. Lighthouse was unable to reliably load the page you requested. Make sure you are testing the correct URL and that the server is properly responding to all requests. (Status code: 429)

Reply on news.ycombinator.com