Header preloads both light and dark theme icons, appearing as unused requests in Network tab

[Bhumikagarggg]

Description

While inspecting the Network tab on meshery.io, I noticed that both light and dark theme header icons (such as meshery-logo-text.png, mode-toggle-icon-moon.png, and mode-toggle-icon-sun.png) are requested during initial page load.
Even when only one theme (light or dark) is active, assets for the other theme are also fetched. This results in multiple icon requests appearing as unused in DevTools, which can be confusing when debugging or reviewing network performance.
The behavior is consistent across page loads and is visible without interacting with the theme toggle.

Expected Behavior

Ideally, only the icons relevant to the currently active theme should be requested on initial page load, or the behavior should be clarified if preloading both themes is intentional for smoother theme switching.

Screenshots

Environment:

• OS: Mac
• Browser: Chrome
• Version:
• Device: Desktop

---

Contributor Guides and Handbook

The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

• 📚 See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
• 🎨 Wireframes and designs for Meshery UI in Figma (open invite)
• 🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

[Bhumikagarggg]

Hello @leecalcote @saurabhraghuvanshii @Rajesh-Nagarajan-11 @kishore08-07
If you found this issue is relvant. I would like to work on this issue.

[Sourya07]

This is intentional behavior. Both light and dark theme icons are preloaded to ensure instant theme switching without flicker.
Although one of the assets may appear as an unused preload in the Network tab, it is expected and does not impact functionality or user experience.

[Bhumikagarggg]

@Sourya07 Thanks for the clarification!
That makes sense for ensuring smooth theme switching without flicker. I raised the issue mainly for clarification since it appears as unused requests in the Network tab.
I’ll wait for a maintainer’s confirmation on whether this behavior is intentional or if any optimization is planned. Appreciate the insight!

[Sravan1011]

is this issue solved