I will fix core web vitals and page speed on your nextjs or react site


About this gig
Slow site, poor Lighthouse score, Search Console complaining about Core Web Vitals. Usually it is images, then fonts, then layout shift, in that order.
Nearly every speed gig here is WordPress plugins and a caching layer. I work on Next.js and React, where the fixes live in the code: image pipelines, font loading strategy, bundle size, hydration, layout shift.
What you get: a before and after report with real numbers, the fixes applied to your codebase, and an explanation of what was wrong so it does not come back six weeks later.
I will tell you upfront what is realistically achievable on your site. Some sites can reach 100. Some cannot, because of a third party script you are not allowed to remove. You get that answer before you order, not after.
Send me your URL and I will take a look.
Respect third-party rights
Please be aware that it is against Fiverr's policies for sellers to include themes, templates, or any other elements that infringe third-party rights or applicable laws in the delivered work. Read more about in our Guide to Responsible Digital Creation.
Get to know Anam Jalal
AI Voice Agent Developer and Nextjs Web Developer
- FromUnited Arab Emirates
- Member sinceSep 2020
- Avg. response time5 hours
Languages
English, Malayalam, Tamil, Hindi
FAQ
Can you guarantee a score of 100?
No, and be wary of anyone who does. Most Next.js sites can reach the green band on all three vitals. A perfect 100 depends on things like third party scripts you may not be allowed to remove. I will tell you the realistic ceiling before you order.
Do you work on WordPress sites?
This gig is for Next.js and React codebases, where the fixes live in the code. WordPress speed work is a different job with different tools, and there are plenty of sellers who specialise in it.
What usually causes a slow score?
Images first, then fonts, then layout shift, then bundle size. In that order, most of the time. I measure before touching anything so we fix the real cause rather than guessing.
Will you break anything?
I work on a branch and hand you a pull request, so you can review every change before it goes live. Nothing gets pushed straight to production.
Do you need access to my repository?
Read access is enough for the audit. For the fixes I need write access on a branch. If you would rather not grant access at all, I can deliver a report with the exact changes for your developer to apply.
What do I get at the end?
A before and after report with real numbers, the fixes applied to your codebase, and a short explanation of what was wrong so your team does not reintroduce it later.
