Blogger drops Next.js after chasing perfect Lighthouse scores
Original title: Removing Next.js Got My Blog to 100 on Every Lighthouse Category
The author says Next.js 16.1.6 still shipped a client runtime and about 230 KB of unused JavaScript on static pages.
A solo developer describes rebuilding a personal blog to score 100 in every Lighthouse category on pagespeed.web.dev. Caching, a CDN, and Cloudflare Image Transformations raised scores, but Next.js 16.1.6 still included a client runtime, hydration, and an RSC router payload even on static server-component pages. The post argues that next/link and next/image pull that runtime in, and that unused JavaScript measured 230,460 bytes.
- Measurements were taken with pagespeed.web.dev.
- Cloudflare Image Transformations’ free tier covers 5,000 images, the author says.
- Stripping client components did not change the Lighthouse score.
- The site is described as static pages with no interaction.
- Products
- Next.js
- Organizations
- CloudflareVercel
From the original article
6 min read at korindiehacker.bloffy.blogMy blog just scored a perfect 100 on every Lighthouse category. I love blogging. I wanted to build a blog that’s light, fast, free of clutter, able to run multiple blogs, and fully accessible on top of that.
By textlanes33 · korindiehacker.bloffy.blog
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.