If you are inserting Algolia on your front end via a script, or you are implementing front-end redirects, you may encounter a lag between the time that your original content exists and the Algolia content is returned. This is due to the time it take for that content to load. The workarounds are:
- Minimizing the visual indicators of a change (i.e. making the initial content and the loaded content visually similar so that they don't look different).
- Implementing your site via the backend instead (so that your resources are all fetched before the site loads) - https://www.algolia.com/doc/guides/building-search-ui/going-further/backend-search/js/#why-backend-search.
- Hosting the InstantSearch script the same way as the rest of your website.
- Optimizing your InstantSearch bundle - https://www.algolia.com/doc/guides/building-search-ui/upgrade-guides/js/#optimize-instantsearch-based-on-your-environment.
- Adding a DSN to reduce lag from users in different geographic locations - https://www.algolia.com/doc/guides/scaling/distributed-search-network-dsn/