Regarding the landing page I think it's still a speed problem, but I'll take a closer look to this.
Thanks again.
Tip: Any operation that's reliant on mouse events should be throttled or debounced -- they are just too noisy. For mapping, I have done debounces as long as two seconds without the delay being obvious. I suspect due to the style of user interaction in combination with the loading animations from the map itself.
Option two: I think for your use case just listening on the single `bounds_changed` event will do what you want. That should trigger for all types of map movement or zooming. For the callback, use a closure which clears and sets a timeout event with the desired debounce time; no need to overcomplicate it. Then it's just tuning the delay until it hits that sweet spot between firing too often and obvious visual delays.
My thoughts about the landing page - It's pretty, but again, the UX is bad. While the screen is loading, I see the slogan drop in (pieces at a time), a second tagline drop in, and then a how it works button. By the time the search has dropped in (this is really your call to action, right? You want people to begin searching, and see it right away), I have already scrolled passed it down the page looking for the search. When I come back up and finally see "Oh, there it is", I've wasted a ton of time looking for it. I recommend that you make this static. The slogan can drop in if you'd like, but this needs to have a permanent place on the landing page.
Upon searching, it took as long as it did to write this paragraph to find any hotels. It returned 11 results, and I'm searching near USC in Los Angeles. Zoomed in a bit further to only encompass 2 hotels, and it took roughly 11 seconds to find them. Anything you can do to speed this up?
It's a neat concept, just hoping to give some constructive criticism.