Fix Next.js UI & Performance
Budget: ₹600 – ₹1,500 INR
My site, ommetoo.in, runs on a Next.js frontend that talks to a Laravel backend and I’m running into two noticeable pain points:
1. Certain page elements simply don’t render or vanish after a route change.
2. Initial and subsequent loads feel sluggish, especially on pages with heavier imagery.
I need someone who can dive straight into the Next.js layer—identify why those components misbehave, trace any state or hydration mishaps, and then trim the fat that’s slowing pages down. If you spot quick server-side tweaks in the Laravel API that directly impact the frontend experience, flag them and we can address them together, but your main deliverable is a smooth, visibly correct, fast-loading UI.
Acceptance is straightforward: every element that should display does so consistently on Chrome, Firefox, and Safari, and key pages reach first interaction in under two seconds on a standard 4G connection (measured with Lighthouse or WebPageTest). Push the fixes to our Git repo, include concise commit messages, and drop a short summary of what you changed and why.
If you’re comfortable profiling React components, optimizing Next.js builds, and understand how Laravel responses might influence the client, I’d love your help.
1. Certain page elements simply don’t render or vanish after a route change.
2. Initial and subsequent loads feel sluggish, especially on pages with heavier imagery.
I need someone who can dive straight into the Next.js layer—identify why those components misbehave, trace any state or hydration mishaps, and then trim the fat that’s slowing pages down. If you spot quick server-side tweaks in the Laravel API that directly impact the frontend experience, flag them and we can address them together, but your main deliverable is a smooth, visibly correct, fast-loading UI.
Acceptance is straightforward: every element that should display does so consistently on Chrome, Firefox, and Safari, and key pages reach first interaction in under two seconds on a standard 4G connection (measured with Lighthouse or WebPageTest). Push the fixes to our Git repo, include concise commit messages, and drop a short summary of what you changed and why.
If you’re comfortable profiling React components, optimizing Next.js builds, and understand how Laravel responses might influence the client, I’d love your help.