Fix #893: Home Page Is a Client Component Rendering Analytics

[rudreshborle]

Pull Request

Description

This pull request addresses the issue of the home page being rendered as a client component, which leads to no SSR/static generation and suboptimal performance. The proposed solution involves moving the <Analytics /> component to app/layout.tsx, making the home page a Server Component, and refactoring any interactive parts into small client sub-components.

---

Related Issue

Fixes #893

---

Type of Change

• Bug Fix
• Refactoring
• Performance Improvement

---

Changes Made

1. Removed the artificial loading state (resolves Issue fix: update CryptoViz metadata and favicon #8 as prerequisite)
2. Moved <Analytics /> to app/layout.tsx
3. Converted the home page from a Client Component to a Server Component
4. Extracted interactive parts into small client sub-components

---

Testing

• Tested locally on various browsers and devices
• No console errors observed
• Existing functionality works as expected with improved performance

---

Screenshots

If applicable, attach screenshots or screen recordings.

---

Checklist

• My code follows the project guidelines.
• I have tested my changes.
• I have updated the documentation if required. (No significant changes to documentation)
• My changes address the related issue.
• This PR focuses on a single issue.

---

Additional Notes

This PR aims to improve time-to-first-byte and LCP metrics by leveraging server-side rendering for the home page and ensuring analytics tracking is consistent across all pages.

[vercel]

@rudreshborle is attempting to deploy a commit to the csxark's projects Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Warning

Review limit reached

@rudreshborle, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 55 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: b064a759-68a4-453f-83b7-87b40bdd0b90

📥 Commits

Reviewing files that changed from the base of the PR and between e4a6af1 and 9499269.

📒 Files selected for processing (9)

• .kairo/cache/graph.json
• .kairo/cache/hashes.json
• api_get.js
• fetch_all_issues.js
• format_line.js
• lib/offline/precacheRoutes.ts
• load_seen.js
• main.js
• public/sw.js

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

🎉 Thank You for Your Contribution

Hello @rudreshborle,

Thank you for submitting a Pull Request to CryptoViz. We appreciate the time and effort you've invested in contributing to the project.

Your Pull Request has been received successfully and will be reviewed by the maintainers as soon as possible.

📋 Pull Request Checklist

• ✅ Linked the related issue
• ✅ No merge conflicts
• ✅ Synced with the latest main branch
• ✅ Build passes successfully
• ✅ All tests pass

Ensuring these requirements are met helps streamline the review process and enables maintainers to review your contribution more efficiently.

❤️ Support CryptoViz

If you find CryptoViz helpful, consider supporting the project by:

• ⭐ Starring the repository
• 🍴 Forking the repository
• 👤 Following Ark on GitHub
• 💼 Connecting on LinkedIn
• 🌐 Visiting the Portfolio

Your support helps increase the project's visibility and encourages continued development. Thank you for being a part of the CryptoViz community!

Thank you once again for contributing to CryptoViz. We appreciate your support and look forward to reviewing your contribution.

[csxark]

Hi @rudreshborle, resolve the merge conflicts