⚡ Bolt: Optimize render cycles with data memoization and static hoisting

[RootDeveloperDS]

⚡ Performance Optimization

💡 What:

• Memoized the dynamic filtered projects array in AccordionMatrix.tsx using useMemo.
• Hoisted heavy static category filtering logic (groupedSocialItems) outside the component body in Footer.tsx so it evaluates once on module initialization instead of every render loop.
• Hoisted the currentYear static computation outside the render loop in Footer.tsx.

🎯 Bottleneck:

• Array.prototype.filter operations were needlessly running on every single React render in AccordionMatrix and Footer components. For AccordionMatrix, simply clicking to expand an accordion triggers a state change in the URL parameters that caused re-evaluation of the projects array. For Footer, mapping multiple categories and applying socialItems.filter meant O(N*M) arrays being created every time a tab navigation or theme toggle triggered a root update.

📊 Impact:
Before: AccordionMatrix re-filtered all items whenever an accordion was expanded/collapsed (URL parameter state change). Footer ran filtering for 5 categories against socialItems on every page render.
After: Matrix array filtering only recalculates when the actual dataset or category changes. Footer category filtering is precomputed instantly on module load (zero render cost).

🔬 Verification:

• Build passed: pnpm build (vite v5.4.19 building for production) successful.
• Tests passed: pnpm test (vitest run) successful.
• Lint passed: pnpm lint (eslint) reports no new errors.
• Visuals: Code review marked #Correct# since behavior is structurally identical and safely memoized.

---

PR created automatically by Jules for task 14310919174197101355 started by @RootDeveloperDS

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
devanshsharma-portfolio	Ready	Preview	Aug 6, 2026 3:30am

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fb831800-b545-444c-83b0-a3f33cd064bc

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}