React/Next.js Performance Specialist

@kamran2012

Hey, I will audit your React 18/Next 13 frontend, ship bundle optimizations, and get your Lighthouse mobile Performance score above 90 with LCP under 1.8s. My first move will be a webpack bundle analysis paired with React Profiler traces on the dashboard — in my experience, Redux-connected components that subscribe to top-level slices are often the biggest hidden cost. I will normalize your store shape, memoize selectors, and wrap heavy routes with `next/dynamic` so the initial payload only carries what the visitor actually needs. Lighthouse CI gets wired into your pipeline as a gating check from day one. Questions: 1) Are you on Pages Router, App Router, or a mix of both — and is migrating on the table? 2) What is the current bundle size and roughly how many Redux slices are in play? Looking forward to talking through the details. Kamran

@designer69hub

As an experienced Full-Stack Web Developer and a specialist in React.js, I believe my skill set aligns perfectly with your project requirements. Over the course of my 8+ years in this field, I've gained remarkable experience in improving web performance through efficient front-end design, backend optimizations, and utilizing tools like Adobe Photoshop, Illustrator, HTML, CSS and more. Tracking performance using Lighthouse and Web Vitals wired into CI is integral to consistently monitoring performance standards – something you can rely on me to implement efficiently. Working diligently towards targets is a known trait of mine; when the public pages score 90+ for Performance in Lighthouse mobile tests and average LCP drops below 1.8s in production as you desire. My workflow generally entails shared repository access and employing a milestones-based approach that ensures clear deliverables along with clean hand-off notes.

@Br1je5h

Your TTFB and LCP targets are slipping — but the bundle bloat you can see is usually 30% of the problem. The invisible half is Redux triggering cascading re-renders that inflate interaction latency and kill FCP on slower connections. Left unaddressed before the next release, you're shipping degradation into production, not just slow pages. At British Petroleum I led the frontend layer of BioVerse — React 18 + TypeScript + AWS, 10+ engineers, SSR with API Gateway — and wired Lighthouse regressions directly into CI so no PR could merge without passing Core Web Vitals gates. Same pattern applies here. Approach: Week 1: Full bundle audit (webpack-bundle-analyzer / Next build output), React Profiler on Redux-heavy paths, identify the top 5 LCP and FCP offenders Week 2: Code-splitting, dynamic imports, image optimisation pipeline, edge middleware for static caching; Redux state normalisation + memoisation fixes Week 3: Lighthouse 90+ mobile confirmed, LCP < 1.8s in production, CI gate merged, hand-off note delivered Milestone structure: M1 (Day 7): Audit report + prioritised fix list — ₹15,000 M2 (Day 18): All optimisations shipped + Lighthouse 90+ confirmed — ₹30,000 M3 (Day 21): CI integration live + hand-off — ₹15,000 What's your current bundle size on the main marketing page, and have you run a Profiler trace on the Redux store during a typical dashboard load? — Brijesh, Sonraj Labs

@mrresearcher99

Hi there, I’ve reviewed your project and would be happy to help. With 5+ years of experience in ReactJS, I build fast, responsive, and scalable web applications with clean, maintainable code. You’ll get smooth UI, efficient state management, and timely delivery — all tailored to your needs. Let’s connect and get started! Best, Bhargav ReactJS Developer | 5+ Years Experience

@jawadasghar69

First milestone I’d target: Reduce JS payload + eliminate major render bottlenecks on your highest-traffic public pages, aiming for immediate measurable gains in LCP/FCP before deeper refinements. Your stack (React 18 + Next 13 + Redux + Tailwind + mixed rendering strategies) is familiar territory, and the symptoms you described usually point to a combination of oversized client bundles, hydration cost, render churn, and inefficient data-loading boundaries. My workflow is typically: Baseline profiling Optimization phase Regression protection I move quickly once repository access is provided and prefer measurable before/after benchmarks for every optimization committed. Ready to start immediately.

@umekayani01

Hey there, I will start with a full performance audit using profiling tools to identify render bottlenecks, heavy bundles, and inefficient Redux usage. Then I’ll apply targeted fixes like code splitting, dynamic imports, image optimization, caching improvements, and SSR or ISR tuning where needed. Every change will be validated through Lighthouse and React Profiler to ensure real measurable improvement without breaking existing flows. Key point: Measured performance gains through profiling driven optimization, not guesswork Do you want me to prioritize dashboard performance or marketing pages first for fastest impact? Inbox me ASAP Warm regards, Umer Kayani

@ozanbceylan

This is exactly the kind of problem I enjoy solving — and I've been here before. React 18, Next 13, TypeScript, Tailwind, Redux: that's my daily stack. I know where the performance bodies are buried in this combination — unnecessary re-renders from unoptimized Redux selectors, oversized bundles from missing code splitting, TTFB spikes from SSR waterfalls. My approach: I start with a full bundle analysis and React Profiler session before touching any code. No guesswork. Then I work through the highest-impact fixes first — code splitting, dynamic imports, image optimization, Redux normalization — and measure each change against your Web Vitals baseline. Your acceptance criteria are clear and measurable: Lighthouse 90+ on mobile, LCP under 1.8s in production. I'm comfortable being held to those numbers. CI integration for Lighthouse is non-negotiable for me too — regressions are how these wins disappear. Ready to start immediately. What does your current Lighthouse mobile score look like?