/tags/performance/Recent content in Performance on Gaurav.devHugoen-US© 2026 Gaurav. Built with care and clean code.Fri, 18 Sep 2026 00:00:00 +0000/posts/nextjs-production-checklist/Fri, 18 Sep 2026 00:00:00 +0000/posts/nextjs-production-checklist/<p>A successful <code>next build</code> proves that the application compiles. It does not prove that the product is ready for real users, crawlers, traffic spikes, or a difficult incident.</p> <h2 id="rendering-and-caching">Rendering and caching</h2> <p>Confirm the rendering strategy for every important route. Static content should not become dynamic because a convenience API reads request state. Dynamic pages need explicit cache behaviour, and revalidation should match how quickly the underlying data can change. Test authenticated and anonymous paths separately.</p>/posts/postgresql-performance-basics/Sun, 30 Aug 2026 00:00:00 +0000/posts/postgresql-performance-basics/<p>When a PostgreSQL-backed application slows down, larger infrastructure can hide the symptom while preserving the cause. A better response starts with evidence.</p> <h2 id="find-the-expensive-work">Find the expensive work</h2> <p>Enable and review query statistics, then rank statements by total time—not only average duration. A moderately slow query executed thousands of times may cost more than one dramatic report. Correlate database behaviour with application endpoints, background jobs, and recent releases.</p> <p>Use <code>EXPLAIN (ANALYZE, BUFFERS)</code> on a safe environment with representative data. Look for large row-estimate errors, sequential scans over selective predicates, repeated nested operations, sorting that spills to disk, and far more rows removed than returned.</p>/posts/technical-seo-engineering/Thu, 30 Jul 2026 00:00:00 +0000/posts/technical-seo-engineering/<p>Technical SEO is often reduced to metadata. In practice, it is the work of making valuable content discoverable, understandable, fast, and stable for both people and search systems.</p> <h2 id="make-discovery-intentional">Make discovery intentional</h2> <p>Important pages need crawlable links in a clear information hierarchy. Generate accurate sitemaps, keep robots directives deliberate, and use canonical URLs to express the preferred version of duplicate or parameterised content. Redirect moved pages once, directly, and preserve meaning.</p>/posts/fiber-axum-performance-services/Tue, 30 Jun 2026 00:00:00 +0000/posts/fiber-axum-performance-services/<p>Go and Rust are compelling when a service has demanding latency, throughput, memory, or reliability constraints. Fiber and Axum provide productive HTTP layers for those ecosystems, but choosing between them is a broader decision than comparing router benchmarks.</p> <h2 id="fiber-operational-simplicity-with-go">Fiber: operational simplicity with Go</h2> <p>Fiber offers an Express-inspired API on top of Go’s <code>fasthttp</code> ecosystem. Teams coming from JavaScript can become productive quickly, while Go provides straightforward compilation, deployment, concurrency, and tooling. A single binary with predictable runtime behaviour is valuable for containers, edge nodes, and operationally lean teams.</p>