next-router-bottleneck

To diagnose Next.js App Router slow routing and high TTFB, this Skill automates performance analysis using Bash, Read, and Grep to collect metrics and identify FCP, LCP, and CLS bottlenecks. It targets Next.js 16 App Router scenarios to pinpoint slow page transitions and server actions blocking.

Next.js hydration delays are analyzed by scanning performance metrics to reveal routing delays and server actions blockers. This Skill automates the diagnosis process, enforcing thresholds to identify hydration issues and guide targeted optimizations for the App Router.

Yes, you can identify server actions blocking in a Next.js 16 project. The Skill automates bottleneck diagnosis to scan metrics, revealing server actions blockers and providing concrete fixes for slow routing and long TTFB.

You get targeted optimization guidance for Next.js FCP and LCP bottlenecks by running this Skill with your local project or production logs. It produces a diagnostic report with concrete fixes for hydration delays and long TTFB.

You need a local Next.js project or production logs to diagnose router performance bottlenecks. The Skill uses these inputs to collect metrics via Bash, Read, and Grep, enforcing thresholds to deliver a repeatable diagnostic workflow.