[BUG] statistics section is not responsive on mobile (content gets cut)

[gauravk-io]

Description

The statistics section does not render properly on smaller screen sizes. On mobile devices, part of the content is getting cut off.

Steps to Reproduce

1. Go to the landing page on mobile
2. Scroll down to Statistics section
3. The user stats are partially hidden

Expected Behavior

The statistics section should be fully responsive, with all content visible and properly aligned on mobile screens.

Actual Behavior

Some portions of the statistics section are cut off on smaller viewports.

Version

No response

Environment

No response

Additional Context

This appears to be a layout or responsiveness issue (possibly fixed widths, overflow handling, or missing media queries).

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• [BUG] Landing Page: Layout breaks on mobile (no margin for "backed by user" icon, icons disappearing & distorted spacing) #141
• [UI BUG]: landing page footer isn't responsive #269
• Navbar overflows and gets clipped on small screen widths #312
• [BUG]: Get Started button not fully visible in hero section #300
• [BUG] On Medium screens the navbar contents overflow. #196

🔗 Related PRs

#223 - feat: fixed stats count size on small screens [merged]

👤 Suggested Assignees

• Janhvibabani
• santosh-marar
• nsvoriginals
• Bunny099
• deveshru2712

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[gauravk-io]

I’d like to work on this issue.

Proposed plan

• Identify the layout causing overflow in the statistics section
• Replace fixed widths with responsive styles
• Test on common mobile breakpoints

Please assign this issue to me if this approach looks good.