Is the route that you’re navigating to a lazy-loaded module? Omar Habash

Based on the fact that you said its the time before initial navigation has taken place, but after a click, it sounds like one of those situations where a lazy-loaded module is starting to get bulky and needs to be broken down further into lazy-loaded sub-modules so that only the absolute minimum required by that particular functionality is loaded on navigation.

You could also use a preloading strategy to load the lazy-loaded module before it’s navigated to, but after all of the eagerly loaded modules are loaded.