Performance Audit
$300
INR 25,000
5-7 days
A measured diagnosis with fixes ranked by impact and effort.
- Core Web Vitals review
- Bundle and image audit
- Rendering diagnosis
- Priority plan
- Review call
Discuss this scope
React and Next.js performance help
Make the product feel faster, more stable, and easier to trust.
For teams with a live site or product that loads slowly, shifts during rendering, ships too much JavaScript, or loses credibility on mobile. Arun measures the real bottlenecks, fixes the highest-impact issues, and shows what improved.
A practical engagement, not a mystery quote
A faster, more stable product without rebuilding everything by default.
Start with a sensible scope, see the likely investment before a call, and receive a written plan before development begins.
- Typical starting point
- $300 / INR 25,000
- Typical delivery
- 5 days-3 weeks
- Best suited for
- Slow or unstable React and Next.js sites where speed is affecting trust or conversion.
Right fit
Built for a business outcome, not a list of screens.
Live React or Next.js products with slow routes, heavy bundles, or unstable layouts.
Marketing sites where loading speed is weakening conversion and search performance.
Teams that need measured improvements without assuming a complete rewrite.
If the project is not a good fit, the recommendation will be a smaller scope, a different specialist, or no build yet.
Transparent starting points
Choose the level that matches the risk you are trying to remove.
These are realistic starting prices, not fixed quotes. The final scope depends on content readiness, integrations, states, timeline, and the quality bar required.
Optimization Sprint
$700
INR 58,000
2 weeks
Hands-on fixes for the most important speed and stability issues.
- High-impact implementation
- Image and bundle work
- Layout stability fixes
- Before and after checks
- Deployment support
Discuss this scope
Frontend Hardening
$1,300+
INR 1,05,000+
3-4 weeks
A broader performance and reliability pass across a larger frontend.
- Cross-route optimization
- Architecture cleanup
- Accessibility fixes
- Monitoring setup
- Handover notes
Discuss this scope
A written scope and milestone plan before work begins
Responsive build, launch checks, and clear handover included
Third-party subscriptions, paid assets, and content production quoted separately
How the work moves
Clear decisions at every step.
You always know what is being decided, what is being built, and what is needed from you next.
Clarify
Measure the live experience and identify the bottlenecks users actually feel.
Design and build
Prioritize fixes by impact, effort, and regression risk, then implement the agreed scope.
Verify and launch
Verify key routes again and document the improvement, trade-offs, and next priorities.
What can be included
The scope is shaped around what moves the project forward.
Core Web Vitals review
Bundle and rendering analysis
Image and font optimization
Layout stability fixes
Route-level performance work
Before-and-after verification
What this should improve
01
A prioritized diagnosis tied to real routes, devices, and user-facing delays.
02
Smaller and better-timed JavaScript, image, font, and data-loading work.
03
Improved layout stability, interaction readiness, and responsive behavior.
04
Clear before-and-after evidence with the remaining technical risks documented.
Relevant work
Project experience and my contribution.
Sound Of Meme
Sound Of Meme - AI Music Generation Platform
I led Sound Of Meme's frontend development from scratch using React, Redux, and Tailwind CSS. I built the music player and AI song-generation interface, established reusable components and hooks, and worked on bundle optimization and the SEO blog architecture. This case study documents that frontend scope and the engineering decisions behind it.
Read case study
HeyClo (CLO AI)
HeyClo / CLO AI - Animated Product Landing Page
I developed HeyClo's animated product landing page with Framer and Lenis, including responsive sections, smooth scrolling, interaction details, and the loading experience. My contribution focused on the public-facing product story and how it behaves across screen sizes. The published landing page is linked from this case study.
Read case study
ChainReach.ai
ChainReach.ai - Creator and Brand Campaign Platform
I built frontend workflows for brands, creators, and administrators on ChainReach.ai: dashboards, campaign creation and acceptance, negotiation screens, AI-assisted campaign generation, and chat. I connected these interfaces to backend APIs using Next.js, TypeScript, and Tailwind CSS. Dashboard access depends on the user's account and role.
Read case studyCommon questions
Useful answers before you spend time on a call.
Do you need to rebuild the whole site?
Usually not. The first step is measurement. Many meaningful gains come from focused work on bundles, images, fonts, rendering, data loading, and layout stability.
Can you guarantee a perfect Lighthouse score?
No responsible performance engagement should guarantee a fixed score before measuring the product. The goal is a faster real experience and measurable improvement on the routes that matter.
Can performance work help SEO?
Performance is one part of technical quality. Faster, stable pages can support user experience and search readiness, but content relevance, crawlability, authority, and intent still matter.
Project brief
Tell me what success needs to look like.
The form is detailed enough to create a useful first response without forcing you through a sales call.
- 1You share the goal, current stage, timing, and budget range.
- 2I review the fit, identify unknowns, and suggest the right scope.
- 3You receive a clear next step before any commitment is expected.