Performance: Resolve severe TTI delays by lazy-loading the Prism.js syntax highlighting engine

[pradeep0153]

Description

Google Lighthouse profiling reveals a severe Time to Interactive (TTI) penalty caused by a massive JavaScript bundle size. The platform is currently importing the entire Prism.js (or highlight.js) syntax highlighting library synchronously in the main bundle to style code blocks within repository READMEs. This forces every single visitor to download and parse 150kb+ of heavy JavaScript before the page can become interactive, even if the user's README doesn't contain a single line of code.

Proposed Solution

• Audit the global Webpack/Vite bundler configuration and the <MarkdownRenderer /> component.
• Surgically remove the synchronous import of the syntax highlighting library.
• Implement dynamic, asynchronous imports (e.g., React.lazy() or standard import()).
• The syntax highlighting library should only be fetched from the network if and only if the markdown parser explicitly detects a ``` code block within the README payload.
• This architectural upgrade drastically slashes the initial JavaScript bundle size, massively accelerating the Time to Interactive (TTI) and significantly boosting the Lighthouse performance score for all portfolios.

[github-actions]

Hey @pradeep0153, thanks for opening this issue! 👋

Before anyone starts working on this, please comment below explaining your approach — what you plan to do and how you plan to do it.

A few things to keep in mind:

• ✍️ Write the explanation yourself — don't paste AI-generated text. We want to understand how you think about the problem.
• 📌 Wait to be assigned before you start coding. This avoids two people solving the same thing at once.
• 📋 Read CONTRIBUTING.md if you haven't already.

Once a maintainer reviews your approach and assigns the issue to you, you're good to go. Looking forward to it! 🚀

[mspandey]

pls assign it to me

[Aditya8369]

@PRODHOSH can you please assign it to me?