Boost Next.js Site 9page Speed 95+
Budget: $250 – $750 USD
My website
Localxlist.net
Recently developed
I have also 10 small task i need to sopve the small taskes. I will share on the chat
My 10-page Next.js site currently hovers in the low-50s on Google PageSpeed Insights, and I need it consistently hitting 95 % or better. You’ll have full access to the repo and staging environment so you can tackle code-level and server-level bottlenecks without disrupting production traffic.
Because I’m gauging success exclusively in Google PageSpeed Insights, every change must translate into measurable gains there—no theoretical tweaks that don’t move the needle. Feel free to use any optimisation technique that fits Next.js (image optimisation, dynamic import, lazy loading, cache headers, critical CSS extraction, Webpack tweaks, etc.). Just keep the framework upgrade paths clean and avoid hacks that will break on the next version.
Deliverables I need before sign-off:
• A concise before/after report from Google PageSpeed Insights (mobile and desktop) for each of the ten pages.
• A pull request or patch set with well-commented code changes.
• A short hand-off note explaining what was changed and how to maintain these performance levels.
If you’ve pushed a Next.js project past the 95 % mark before, that’s exactly the experience I’m after. Let’s do this.
Localxlist.net
Recently developed
I have also 10 small task i need to sopve the small taskes. I will share on the chat
My 10-page Next.js site currently hovers in the low-50s on Google PageSpeed Insights, and I need it consistently hitting 95 % or better. You’ll have full access to the repo and staging environment so you can tackle code-level and server-level bottlenecks without disrupting production traffic.
Because I’m gauging success exclusively in Google PageSpeed Insights, every change must translate into measurable gains there—no theoretical tweaks that don’t move the needle. Feel free to use any optimisation technique that fits Next.js (image optimisation, dynamic import, lazy loading, cache headers, critical CSS extraction, Webpack tweaks, etc.). Just keep the framework upgrade paths clean and avoid hacks that will break on the next version.
Deliverables I need before sign-off:
• A concise before/after report from Google PageSpeed Insights (mobile and desktop) for each of the ten pages.
• A pull request or patch set with well-commented code changes.
• A short hand-off note explaining what was changed and how to maintain these performance levels.
If you’ve pushed a Next.js project past the 95 % mark before, that’s exactly the experience I’m after. Let’s do this.
Related categories:
PHP
JavaScript
CSS
HTML
React.js
Web Development
Google PageSpeed Insights
Next.js