Zinn Hub
0
Your Cart
0

At a Glance

Key details about this service to help you decide. Generated by Zinn Hub, not the seller.

Measurement Approach

Lab + Field Data
Core runs use throttled-connection lab measurements (Lighthouse + React Profiler). Field data from real users available as an add-on for $40.

Frameworks Covered

React, Next.js & more
Works with Next.js, Vite, CRA, Remix and plain SPAs. Framework-specific fixes (e.g. route-level splitting, caching modes) are tailored to your stack.

Metrics Reported

LCP, CLS, INP, Bundle
Every report covers all four Core Web Vitals plus bundle size per route, measured before and after on the same throttled connection in a single comparison table.

Delivery Method

Branch + Written Report
Fixes land as individual commits on a branch in your repo, each with a reason. Nothing is deployed without your request. No calls - everything in writing.

What You'll Receive

Formats:
Written Report
Custom Code
Delivery Method:
Order Manager
Notes: All packages include a written report with LCP, CLS, INP and bundle size for each route, measured on a throttled connection, plus the estimated savings next to each finding. On Standard and Advanced, the fixes go to a branch in your repository, one commit per change, and a single table shows the numbers before and after. Nothing is deployed unless you ask.

Full Description

Order this if you think slow pages are costing you signups or search traffic and you want to keep the app you have. React and Next.js already ship most of what a fast app needs, so the gains come from using those tools well rather than switching stacks.

You get numbers, not adjectives: LCP, CLS, INP and bundle size per route, measured before and after on the same throttled connection, in one table.

Starter is the audit of one page: the runs, the findings ranked by payoff, no code changed. Standard starts from that audit and spends the rest of the time on the fixes that move those numbers. Advanced covers up to 5 routes, tunes rendering and caching, and leaves a bundle budget in CI so the next release cannot quietly undo the work.

Work happens on a branch in your repository, commit by commit, each with its reason. Nothing is deployed by me unless you ask for it.

No calls. Everything in writing, including the measurements that disagree with me.

Steps for completing your project
1. Measure what your users actually get - Lighthouse on your live pages and a React profiler session on the slow ones, on a throttled connection. LCP, CLS, INP and bundle size per route, written down before anything is touched.
2. Find what costs the most - The bundle and the network waterfall: what ships that nobody uses, what blocks the first paint, which components re-render and why. Every finding carries an estimated saving in milliseconds or kilobytes.
3. Fix it, biggest win first - Code splitting, image and font handling, render-blocking work, memoization where the profiler asks for it, data fetching moved off the critical path. One commit per change, each with its reason.
4. Measure again, side by side - The same runs on the changed build: before and after in one table, per route and per metric. If a change made something worse, the table says so and the change goes back out.
5. Handover in your repository - A branch or patch in your repo, the report, and an honest list of what I did not do and what it would be worth. Deployment stays in your hands.

Zinner Quality Guarantee

✓
Vetted Professional
Every Zinner is reviewed and approved before joining the platform.
✓
Quality Work Guaranteed
All services are backed by our quality assurance commitment.
✓
Secure Payment
Your payment is protected until you approve the delivered work.

Compare Packages

ФункцияStarterStandardAdvanced
Delivery Time2 days4 days8 days
Revisions023
ScopeOne page profiled, rankedAudit plus the main fixesDeep pass, up to 5 routes
Source code✕✓✓

Portfolio

Examples of the seller's work related to this Zinn.

Formline: Next.js store with Stripe

A storefront you can click through: 16 posters in 4 collections, filters and search that stay in the URL, a cart, light and dark themes, and a checkout that ends in a demo order or a real Stripe Checkout session in test mode. I built it as a Next.js static export in TypeScript with Tailwind CSS. Card payments go through a Cloudflare Worker that re-prices the cart on the server and verifies Stripe's webhook signature.

Bilingual personal site in Next.js

A one-page personal site in English and Russian, with a services section and links to my demo projects. I designed and built it with Next.js, React and TypeScript as a static export, styled with plain CSS Modules and no UI framework. It has light and dark themes, and a social preview image for each language is generated at build time. GitHub Actions builds and deploys it to Bunny CDN, which adds security headers and redirects www and plain HTTP to the main HTTPS address.

Service Details

Service Type
Standard
Zinner Type
Freelancer
Availability
Weekdays
Seller's Country
Kazakhstan
Languages Accepted
English
Russian
NDA available
Yes
Project Sizes Handled
Small To Medium
Response time
Within 12 hours
Years of Experience
10+

Frequently Asked Questions

No, and be careful with anyone who promises it before seeing your code. A checkout widget or an ad script can cap the score whatever I do. The audit tells you your ceiling and what reaching it costs.

No. Vite, CRA, Remix or a plain SPA all profile the same way. Only the framework-specific fixes differ: route-level splitting and caching instead of Next.js rendering modes.

Yes. Standard begins with the same audit and spends the remaining time fixing what it found. Starter exists for teams who will do the work themselves and just need to know where to dig.

The audit sees that: server response time shows up separately from render and script cost. Profiling the API or the queries is the add-on, in Node, Express, NestJS or Rust.

Read access to the repository, or an archive of the source, plus the URL of the page. On Standard and Advanced I push the fixes to a branch, so I need permission to create one. If you'd rather not give it, I send a patch instead. I never need deploy access.

On your live production pages by default, so the numbers match what your users get. If the page is behind a login or not deployed yet, a staging link, a test account or steps to run it locally all work, and the report says which one the numbers come from.

Customer Reviews

See what our customers say about this Zinn

Categories

Zinner Policies

I Will Profile Your React Or Next.js App And Make It Faster, With Numbers 2 &Raquo; Zinn Hub

Only logged in customers who have purchased this product may leave a review.

Options & Order

Get the Zinn Hub App

Notifications · Faster access · Full-screen

Tap Share in your browser

➜ Then tap "Add to Home Screen"