Apparently there was a post on Hacker News about Hologram that made it to the front page: Hologram: A full-stack isomorphic Elixir web framework | Hacker News, and a lot of people experienced the same issue as you, somebody even created a bug report: Slow navigation in the documentation · Issue #165 · bartblast/hologram · GitHub
Here are my findings (copied from the GitHub issue):
I identified a bug in Hologram’s patching mechanism which occurs when root element (html) attributes are modified during navigation. This happens in this case because the html element gets a Tailwind overflow-hidden class when the menu opens to prevent scrolling underneath the menu container.
The noticeable lag (~500ms) will remain for a while as this is Hologram 0.2.0 (an alpha release, see: 🎉 Hologram - An Isomorphic Elixir Web Framework is Here!) with some temporary implementations:
- The current bitstring implementation is very inefficient (since templates are essentially long bitstrings, this significantly impacts performance)
- There’s extensive logging for debugging
- Every action triggers a full template re-render
These issues are scheduled to be fixed in upcoming releases.
The Hologram fix has been applied to the website - could you confirm if the menu works correctly now (aside from the noticeable lag)? Navigation to the next page should be fast; only opening/closing the menu without clicking a link should have the noticeable lag.
