[FEATURE] Performance Improvements for SEO & Core Web Vitals

[Khushi5155]

📖 Description

Website performance directly affects SEO, user experience, and Core Web Vitals scores.
This issue focuses on auditing and improving performance by reducing bundle size, optimizing loading, and adding preconnect hints for external resources.

---

📌 Parent Issue

Part of #68 – SEO Improvements: Structured Data, Missing Pages & Performance

---

🎯 Scope of Work

1. Audit Core Web Vitals

   • Measure Largest Contentful Paint (LCP)
   • Measure First Input Delay (FID)
   • Measure Cumulative Layout Shift (CLS)
   • Tools: Google PageSpeed Insights, Lighthouse

2. Minimize bundle size

   • Analyze JS/CSS bundles
   • Remove unused dependencies or code
   • Use dynamic imports / code splitting where possible

3. Add preconnect hints

   • Preconnect to frequently used external resources (CDNs, APIs)
   • Example:

     <link rel="preconnect" href="https://fonts.googleapis.com" />
     <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />

4. Additional optimizations

   • Ensure efficient image formats (WebP)
   • Enable caching for static assets
   • Lazy-load non-critical scripts or components

---

✅ Acceptance Criteria

• Core Web Vitals scores meet or improve:
  • LCP < 2.5s
  • FID < 100ms
  • CLS < 0.1
• Bundle size reduced or optimized without breaking functionality
• Preconnect hints added for major external resources
• No console warnings or network errors
• Lighthouse/Pagespeed audit shows improvement

---

🛠️ Implementation Notes

• Use tools like Vite Bundle Analyzer or Webpack Bundle Analyzer for size reduction
• Keep optimizations modular and test each change to prevent regressions
• Ensure preconnect hints are added only for necessary external resources

---

🧪 Testing Checklist

• Run Lighthouse performance audit before and after changes
• Verify Core Web Vitals metrics
• Test page load speed and network requests
• Ensure all site features still work after optimizations
• Check console for errors or warnings

---

🏷️ Labels

frontend, seo, performance, swoc2026, hard

---

🙌 Contribution Notes

• Focus on performance improvements only
• Avoid modifying SEO metadata or structured data (handled in separate issues)
• Document all major changes to scripts, bundles, or network optimizations in the PR

[Anshpujara5]

Hi @tarinagarwal 👋

I’d like to work on [FEATURE] Performance Improvements for SEO & Core Web Vitals (#100).

I’m comfortable working on performance audits and frontend optimizations, and I plan to approach this by:

Proposed approach:

Run baseline audits using Lighthouse and PageSpeed Insights to record current LCP, FID, and CLS.

Analyze JS/CSS bundle sizes using a bundle analyzer and identify opportunities for:

Code splitting / dynamic imports

Removing unused dependencies or dead code

Add preconnect hints for critical external resources (fonts, APIs, CDNs) where applicable.

Optimize loading behavior:

Ensure images use efficient formats (WebP where possible)

Lazy-load non-critical components/scripts

Verify caching for static assets

Re-run audits and document before/after improvements in the PR.

I’ll keep the changes modular and limit the scope strictly to performance (no SEO metadata or structured data changes).

Please let me know if this works—I’d be happy to take this up 😊

[tarinagarwal]

@Anshpujara5 The website is hosted on vercel.. and current speed insights shows a overall good performance.
So its not needed I believe
For SEO part
@Khushi5155 is already working on it.

[tarinagarwal]

@Khushi5155 u can proceed with the SEO part.