5 ms·

I hope it helps with monetization! It's a potentially useful feature, which can bring in money to you, and it's not too annoying. My only real concern that the

by e1ven 14y ago

I hope it helps with monetization! It's a potentially useful feature, which can bring in money to you, and it's not too annoying. My only real concern that the site seems to have more latency than it did last time I used it - I'm sure sure if it's due to increased load, or waiting for the RTT to Sedo, but it's something to keep in mind. Perhaps you could fill those in with a separate ajax call, so they aren't necessarily blocking the other results while you wait for sedo?

matt1 14y ago
The increased latency is caused by API calls that the app has to make to Sedo for new queries. I've spent a lot of time optimizing it lately, but agree that there's still room for improvement. It comes down to a tradeoff: would you rather get more premium results but have to wait a little while longer or get less results but have them quickly? For now I've taken the middle road, but that may change depending on how it affects usage. Appreciate you bringing it up though and for suggesting alternatives.
- eli 14y ago
  Perhaps you could load fewer premium results beforehand but load the rest via AJAX?
  - matt1 14y ago
    It's actually all done via Ajax that way it doesn't affect the page load time. The search itself is also done on a separate server that way it doesn't tie up any of the app's dynos on Heroku (go go JSONP). I could make an initial API call and get a handful of results, but handling the remainder would be tricky. For example, let's say that the preliminary search returns 12 domains and I immediately display them to the user. Ten seconds later the second Ajax call returns an additional 60 premium domains. How do I display those to folks in a non-intrusive way? I'm open to suggestions :)