Blog Details

At SakhtBazar, a B2B marketplace connecting construction suppliers and contractors, the frontend was server-rendered Laravel Blade. It worked — but every page paid the full server-render cost, caching was coarse, and search engines saw a slow site. Migrating to Next.js cut page load times by 80% and tripled organic traffic. Here is what actually mattered.

1. Server-side rendering where it counts

Marketplace listing and product pages live or die by indexing and first paint. Moving them to SSR meant crawlers received complete HTML and users saw content on the first response instead of waiting for client-side hydration of an empty shell.

2. Caching in layers, not hopes

Frontend caching strategies paired with Redis on the backend took repeated work off the critical path: rendered fragments, API responses and session-adjacent data each got an explicit lifetime instead of hitting the database on every request.

3. Components as a performance budget

The migration produced 50+ reusable frontend components. Shared, reviewed components meant fewer one-off heavy widgets, consistent lazy-loading of below-the-fold blocks, and images with explicit dimensions to stop layout shift.

4. Measure Core Web Vitals, not vibes

Largest Contentful Paint, interaction latency and layout shift were tracked before and after each change. The 80% figure is the result of that loop: change, measure, keep what moves the metric.

The takeaway: framework migrations pay off when each step serves rendering, caching or measurement. Next.js was the vehicle — the discipline was the engine.