The orange nearly killed my eyes. Apart from that, why do you use fake testimonials? I'm assuming that, since in the bottom you have a person, called "Antonina K. Director of Operations, TrustGuard". The lady on the picture is Sarah Parmenter: http://ios-blog.co.uk/featured-posts/sarah-parmenter-web-and...
Hi David, well I should make it clear that it does nothing else behind the scenes other than make an HTTP call to get website data only when you hit click to get the data, that's about the only thing it does. I get wary of other extensions too when I install but I can tell you this app does not track sites you browse if that's your concern (you can inspect it yourself and see).
Your whois lookup is broken for ac.uk domains - for example, all of these requests return the whois data for ac.uk itself, rather than the specified domain:
The fact you have a quote from "Antonina K.
Director of Operations, TrustGuard" with a photo of "Sarah Parmenter, Owner of You Know Who" makes me think you made them up.
I wonder how many testimonials on the web are actually real?
I will start by saying that the site color scheme is pretty sharp for my eyes. I think you'll have a more polished look by having the background be white with a more neutral color palette.
For the extension itself: I like that it doesn't call out for information unless called upon, but if I ask for information about a site, I see no reason for you to have to collect the full URL and POST it to /track. That could lead to unexpected data leakage (as some URLs could be sensitive). You should probably get those API calls over to using HTTPS as well.
Also with every lookup, my console gets the log message "asdf", which is kind of weird. One thing I noticed is that the extension is pretty slow to get information. It appears it calls out for each item individually, and this leads to seven unique calls to your API that could be condensed into one request / response. If an API call fails with a 500 error, the entire stacktrace is dumped to the user. You'll want to disable debugging mode in your Express app to ensure that doesn't happen.
Since these APIs are public, you might want to consider rate limiting by IP, or you might find that your extension isn't the only consumer of them. A free and open WHOIS or Geolocation API that responds with JSON could be abused by other app developers, and having that already around moves the cost from them to you.
It might be an awesome extension, but if it's not related to the company at honeybadger.io, you need to rename the thing.
Even if the similarity was completely inadvertent, it's just going to lead to confusion and legal hassle, and could end up hurting your reputation more than the functionality of the extension will help it.
The most useful/interesting for me is the technology section. As that's not the easiest to get data about. Unfortunately the info that its giving is completely false/random. Checked it on a few websites that I've built or know the stack and the info shown is completely wrong.
www.builtwith.com provides much more information but they do not have a chrome plugin that I'm aware of. Definitely should check it out if your interested in this plugin.
Could you give me an example of a site you did? Although I know it's not 100% accurate, from my experience, they were fairly accurate. I am pulling data from builtwith.com btw.
So you know, your "Leave Feedback" button seems to lead to a survey / feedback form for "Competition Tab," rather than Honeybadger.
Edit: For what it's worth, if the plugin really does what it says it does on the Chrome Webstore page, it sounds really, really useful. Will try later.
> At the mere click of a button, our honeybadger will let you see how much traffic the site gets, how much money they raised, what powers their stack, and much more.