10 ms·
Fast or Slow
- thanksforfish 6y agoI appreciate that it shows your place in line (I started at 53). This is really polished.
- Wowfunhappy 6y agoCommenting four minutes later: I started at 350! Hacker News bump I guess?
- twicetwice 6y ago3 minutes later, I started at 483… definitely Hacker News bump!
- lalaithion 6y agoAnd I'm in 661, 3 minutes later.
- saagarjha 6y agoI'm in 429th place…wait, that's an error code.
- willcipriano 6y agoOne hour later and 2151 in line ahead of me, talk about exponential growth. https://www.fastorslow.com/app/profile/244179fc-78d2-5cf3-8ceb-b87ae9c9968b https://www.fastorslow.com/app/profile/244179fc-78d2-5cf3-8c...
- geerlingguy 6y agoAnd now just getting 500 errors :(
- deleted 6y ago[deleted]
- mmaunder 6y agoWorking on it. Looks like a queue issue. Adding more workers. All kinds of fun this evening. Edit: From our eng team: "We're moving about 5000 events per second now. Definitely shrinking now, and memory usage is dropping too." Should be good to go now. Sorry, but massive traffic right now.
- deleted 6y ago[deleted]
- mmaunder 6y agoThanks, and we really appreciate your patience. See my comment regarding moving into AWS to improve scalability on demand.
- aaronbwebber 6y agoTip: if your site is going to redirect from the bare domain to something else (e.g. `https://example.com` https://example.com` -> `https://example.com/home/` https://example.com/home/`) make sure you enter the final destination, letting it redirect means that the cost of the redirects will be included in the report, which is unlikely to be what you want.
- yodon 6y agoUnless that redirect is something your users are likely to experience, in which case you shouldn't cheat and provide a URL that delivers a different loading delay than visitors will encounter.
- aaronbwebber 6y agoWell...in many cases all it really tells you is the roundtrip network latency, which may or may not be something you are interested in. In my case it actually was sort of interesting - it definitely suggested that the redirects don't have the correct caching headers, because they clearly weren't being served off the CDN. However, this redirect is a pretty unusual case for us, because most of our traffic is either from SEO or links from notifications we send users. I agree that you should be looking at the experience most users are going to have, but if the first experience for most users is a redirect you should probably do something about that.
- rbritton 6y agoYep. We try to indicate when you're being affected by redirects since `http` -> `https` and `example.com` -> `www.example.com` are common ones. Those can often mean hitting an origin server instead of an edge server first.
- aaronbwebber 6y agoYup! As I noted in a comment above, this is just not a common case for us - usually our inbound traffic is coming from SEO which sends you to the right place. But when I am typing it into a search box, it's real easy to forget. I am going to look into getting those redirects cached though, there's no reason we shouldn't be able to serve them off the edge.
- mike_d 6y agoEdit: I was wrong. But also check out https://webpagetest.org/ https://webpagetest.org/ as an alternative (that you can host internally as well)
- mmaunder 6y agoWe're using Chrome's Lighthouse running in containers with a focus on normalized performance between locations, security and responsiveness. This is built from the ground up by us.
- mike_d 6y agoAh, that make sense then. Most of the Lighthouse recommendations were copied from WPT.
- hoten 6y agoBesides the underlying insinuation (what's wrong with tools copying others if the ideas hit all the right notes?), what recommendations did Lighthouse copy? WPT is mainly a supertool—here's a ton of data, go dig into the waterfall and network requests with some visualizations. I think there's a page for recommendations but to be honest I've never used it nor seen anyone talk about it. With Lighthouse's performance report, we aim to provide specific actionable advice with estimates for how impactful it will be.
- pxtail 6y agoAre you using https://www.sitespeed.io/ https://www.sitespeed.io/ under the hood or is your tool custom-built around lighthouse reports?
- mmaunder 6y agoQuote from the eng team: "Never actually heard of it. We're build around the raw data provided from the built-in Lighthouse audits plus some of our own custom ones"
- mmaunder 6y agoHi all. We're really flattered to be on the home page of hacker news. Thanks!! You caught us by surprise. As you can see we've built in the ability to gracefully handle a lot of traffic but it's not ideal because you need to wait in a queue until we have enough capacity. So I wanted to jump on here and give you an update of a release we're putting out next week. FastOrSlow does actual browser simulations from around 12 locations around the world. When we first architected it, we wanted to provide as many locations as possible including places like South Africa. That meant in some cases we needed actual bare-metal servers. So we built it on bare metal in data centers around the world. We experienced some moderate popularity about a month ago and realized we needed to do a better job of scaling on demand. So we re-evaluated moving on to AWS. Around the same time AWS launched in Cape Town and a few other locations, and so we were able to get the kind of coverage we wanted globally. So we kicked off an AWS migration. We're days away from moving into AWS and using spot instances to ramp up and down fast based on demand. But as I said, you caught us by surprise. So please give FastOrSlow a try today, but know that by around late next week we'll be doing a much better job of handling your requests FAST without having to wait in line. Thanks for your interest and patience. Myself and the lead architect, Ryan, will be here to answer any questions and of course listen to your suggestions. Regards, Mark.
- mmaunder 6y agoWe'll also be expanding to 18 locations globally once the migration completes.
- mmaunder 6y agoWe have a lot of jobs in the queue right now. Just passed 1000 folks waiting. Just wanted to reassure you that your job will finish. Just leave the browser window open, take a break and come back. Even if you close your browser, as long as you come back to the same URL, your report will be there once the job is done.
- oyeluckynavin 6y agoIf someone closes the browser, you could remove the user from the queue to save time for now. Lot of users would be closing the browser and might not come back.
- louwrentius 6y agoThis is build by the company: https://www.wordfence.com https://www.wordfence.com
- code_duck 6y agoI've had some issues like "There is a more recent report available for this URL. Would you like to view it?" but then when I try to, it says "No reports found".
- swyx 6y agoI collect sites like these! Here's my list of Every Web Performance Test Tool: https://www.swyx.io/writing/webperf-tests/ https://www.swyx.io/writing/webperf-tests/ (will be updating with FastorSlow)
- huphtur 6y agoNother one to add to your list perhaps? https://lighthouse-metrics.com/ https://lighthouse-metrics.com/
- swyx 6y agoadded!
- otterley 6y agoWould you mind adding Amazon CloudWatch Synthetics to your list? https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch_Synthetics_Canaries.html https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitori...
- swyx 6y agoadded!
- move-on-by 6y agoSecurity Headers would fit nicely in your ‘improvement recommendations’ section: https://securityheaders.com/ https://securityheaders.com/ Mozilla has a nice one as well: https://observatory.mozilla.org/ https://observatory.mozilla.org/
- swyx 6y agodone, thanks!
- winrid 6y agoNice, my marketing site that's not even on a CDN yet gets over 90 score in all regions. :)
- strikelaserclaw 6y agoIt seems cool but there are like 1k sites before mine, i wonder if you guys can implement a feature to email the report after the report is generated in the mean time (seems like a small feature).
- nodesocket 6y agoPlus, they can collect e-mail addresses they can market and target to. Great idea.
- adtac 6y agoThat is spam.
- polote 6y agoDoes someone mind sharing his own result so that we cant check the tool without waiting 3 hours please ?
- rbritton 6y agoHere's one: https://www.fastorslow.com/app/profile/8b282a3c-db98-5b1a-989f-00e88e253f27 https://www.fastorslow.com/app/profile/8b282a3c-db98-5b1a-98...
- ryanmcdonough 6y agoAnd another https://www.fastorslow.com/app/profile/2bd978bd-f107-5761-8459-d17436c0a0db https://www.fastorslow.com/app/profile/2bd978bd-f107-5761-84...
- omot 6y agoI got a 429 Too Many Requests on my first try... What.
- jonchurch_ 6y agoCan someone post a completed report so we can peek at it while waiting in the queue?
- ryanmcdonough 6y agohttps://www.fastorslow.com/app/profile/2bd978bd-f107-5761-8459-d17436c0a0db https://www.fastorslow.com/app/profile/2bd978bd-f107-5761-84...
- edpichler 6y agoTheir own website is super slow.
- llacb47 6y agoWhy do you suppose that is?
- deleted 6y ago[deleted]
- leonardosts 6y agoI'm getting "429 Too Many Requests"
- geoffbp 6y agoI'm seeing an internal 500 for all pages. Will try again later or tomorrow I guess.
- mmaunder 6y agoFrom our eng team: "We're moving about 5000 events per second now. Definitely shrinking now, and memory usage is dropping too." Should be good to go now. Sorry, but massive traffic right now.
- taf2 6y agoHow does this compare to webpagetest.org?
- ashtonkem 6y agoReminds me of a similar but completely unrelated phrase from the military: “slow is smooth, smooth is fast”
- mmaunder 6y agoShooter IIRC with Wahlberg. Love that old gunsmith in the Georgia forests.
- mcharezinski 6y ago500 error
- mmaunder 6y agoLooks like a queue worker issue. From eng: "We're moving about 5000 events per second now. Definitely shrinking now, and memory usage is dropping too." Should be fixed.
- mmaunder 6y agoQuick update: We were generating 500s for the last 15 mins. Our worker queue got overwhelmed. From the eng team: "We're moving about 5000 events per second now. Definitely shrinking now, and memory usage is dropping too." Should be good to go now.
- skilled 6y agoI don't expect the site to be fully crowded all of the time, but have you thought about adding caching for previously processed sites? Perhaps a choice to see either a previously generated report or create an entirely new one. The reason I ask is that I did a report last night, and checked it on my phone in the early morning. I put my site's address in again from my desktop now, and I see that I am 1,000+ in line. Even though a recent report was made for this site already, I can't seem to access it.
- mmaunder 6y agoThanks. You can access previous reports but you need to save the url. And they are cached. But this is a good idea. Thanks.
- hoten 6y agoHi! I work on Lighthouse and Page Speed Insights (similar service to what you got here). Nice to see another player in this space :) congrats on the HN bump! Wondering if you've had any pain points integrating Lighthouse that you wouldn't mind sharing. Anything more difficult than it should be, or were the docs lacking in some way, etc.
- mattbgates 6y ago504 ERROR The request could not be satisfied. CloudFront attempted to establish a connection with the origin, but either the attempt failed or the origin closed the connection. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. Generated by cloudfront (CloudFront) Request ID: Ba3iKlMjJUrRy2BYUVqVLmm4hcOF70KSJgcfFnU2SUdQFLTIriKq8A==
- truth_seeker 6y agoThank you for creating this. It was AHA moment for me when i looked at "Geography" and "Location" section. Pretty cool stuff.
- mmaunder 6y agoThanks!
- mmaunder 6y agoIntermittent right now but working on it. Should be back in a few mins.
- mmaunder 6y agoWe came back within a few minutes. Posted an earlier update above.
- jerzyt 6y agoYeah, let me know when it actually works. Started at about 1200 in the queue and 4 hours later I'm still number 81, and have been sitting at 81 for the last hour. Sounds interesting, but I think you launched too soon.
- jerzyt 6y agoOh great, someone is down voting me. Another four hours later, and I'm still showing #81 in the queue.
- cinbun8 6y agoYour site eats up a lot of CPU for some reason
- chrismorgan 6y agoThese pages use an awful lot of CPU when they’re active—in Firefox Nightly on Windows, a completed results page was consuming an entire core, which is not usual.