Event-driven architecture: handling eventual consistency in the UI

our backend team has fully embraced event-driven architecture, and it's working really well for decoupling services and scaling. the frontend, however, is really struggling with eventual consistency. for example, a user places an order, the event goes out, the backend processes it, but by the time the user is redirected to an 'orders' page, the new order might not appear immediately because the read model hasn't updated yet. we're seeing this 1-3 second delay which causes a lot of confusion and support tickets. we've considered things like optimistic UI updates with client-side reconciliation or using websockets for immediate feedback, but both add significant complexity. what are the most effective strategies you've seen for bridging the gap between an asynchronously updated backend and the synchronous expectations of a user interface in a highly distributed system?