-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Description
Is your feature request related to a problem? Please describe.
Problem Description
Eagerly loading all network-related assets can:
- increase initial bundle size
- slow down first contentful paint
- negatively impact performance on low-bandwidth devices
Expected Behavior
- Network-specific assets should be loaded only when needed.
- Initial page load should include only the minimal required assets.
- Switching networks should dynamically load additional resources.
Steps to Reproduce
- Load the Base website with a clean cache.
- Inspect network requests and JS bundle contents.
- Observe that assets/config for multiple networks are loaded upfront.
Describe the solution you'd like
Proposed Solution
- Move network-specific configuration and assets behind dynamic imports.
- Load only the active network’s assets during initial page render.
- Lazily load additional network assets when a user switches networks or navigates to network-specific views.
- Ensure dynamic loading is transparent to existing components.
Acceptance Criteria
- Initial bundle excludes unused network-specific assets.
- Network-specific assets load correctly when required.
- No functional regressions when switching networks.
- Observable improvement in initial load performance (bundle size or timing).
Metadata
Metadata
Assignees
Labels
No labels