# Experience from slow hotel connection

**URL:** <https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421>\
**Category:** Feature\
**Created:** [18 Maggio 2016, 3:41am UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421 "2016-05-18T03:41:04Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![charleswalter](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/charleswalter/32/116433_2.png) [@charleswalter](https://meta.discourse.org/u/charleswalter)\
**Post date:** [18 Maggio 2016, 3:41am UTC](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421/1 "2016-05-18T03:41:04Z")

</div>

I’m at a hotel in Costa Rica and many other guests must be using the wifi right now, because the Internet is awfully slow.

I thought it was interesting to see how Discourse behaved on a few instances. First, when tapping on the number of likes a post received, it appeared that there was no response. But indeed 5-6 seconds later popped the faces of who had liked my post.

Perhaps more importantly, I posted a reply, and saw that it posted, and then continued to navigate. But when I refreshed the topic, I noticed my post had not actually made it to the server.

Just wanted to share these experiences. I expect they can be simulated by applying throttling from Chrome developer tools. I don’t expect this to be the norm, but if there are easy things that could be done to let user know to hold on, might be worth considering for future roadmap.

---

_[View the full topic](https://meta.discourse.org/t/experience-from-slow-hotel-connection/44421)._