I reach for Next.js

📰 Medium · JavaScript

Learn how to optimize your frontend build time with Next.js and discover the benefits of migrating to a more efficient framework

intermediate Published 16 Jun 2026

Action Steps

Analyze your current build time to identify bottlenecks
Research alternative frameworks to Next.js for potential improvements
Implement optimization techniques for Next.js, such as reducing page optimization time
Consider migrating to a more efficient framework if necessary
Monitor and compare build times before and after optimization

Who Needs to Know This

Frontend developers and software engineers can benefit from this article by learning how to improve their build times and optimize their workflow

Key Insight

💡 Next.js can be a significant contributor to build time, and optimizing or migrating to a more efficient framework can greatly improve performance

Key Takeaways

Learn how to optimize your frontend build time with Next.js and discover the benefits of migrating to a more efficient framework

Full Article

Title: I reach for Next.js

URL Source: https://medium.com/@TheExpertDeveloper/i-reach-for-next-js-31e4c7a2ca20?source=rss------javascript-5

Published Time: 2026-06-16T13:16:00Z

Markdown Content:
[Sitemap](https://medium.com/sitemap/sitemap.xml)

[Open in app](https://play.google.com/store/apps/details?id=com.medium.reader&referrer=utm_source%3DmobileNavBar&source=post_page---top_nav_layout_nav-----------------------------------------)

Sign up

[Sign in](https://medium.com/m/signin?operation=login&redirect=https%3A%2F%2Fmedium.com%2F%40TheExpertDeveloper%2Fi-reach-for-next-js-31e4c7a2ca20&source=post_page---top_nav_layout_nav-----------------------global_nav------------------)

[](https://medium.com/?source=post_page---top_nav_layout_nav-----------------------------------------)

Get app

[Write](https://medium.com/m/signin?operation=register&redirect=https%3A%2F%2Fmedium.com%2Fnew-story&source=---top_nav_layout_nav-----------------------new_post_topnav------------------)

[Search](https://medium.com/search?source=post_page---top_nav_layout_nav-----------------------------------------)

Sign up

[Sign in](https://medium.com/m/signin?operation=login&redirect=https%3A%2F%2Fmedium.com%2F%40TheExpertDeveloper%2Fi-reach-for-next-js-31e4c7a2ca20&source=post_page---top_nav_layout_nav-----------------------global_nav------------------)

![Image 1: Unknown user](https://miro.medium.com/v2/resize:fill:32:32/1*dmbNkD5D-u45r44go_cf0g.png)

# I reach for Next.js by reflex Railway just ripped it out in two PRs and dropped their build from 10 minutes to under 2.

[![Image 2: The Expert Developer](https://miro.medium.com/v2/resize:fill:32:32/1*HdyuUI5hcX8r20-34LzriQ.png)](https://medium.com/@TheExpertDeveloper?source=post_page---byline--31e4c7a2ca20---------------------------------------)

[The Expert Developer](https://medium.com/@TheExpertDeveloper?source=post_page---byline--31e4c7a2ca20---------------------------------------)

4 min read

·

Jun 16, 2026

[](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2F_%2Fvote%2Fp%2F31e4c7a2ca20&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40TheExpertDeveloper%2Fi-reach-for-next-js-31e4c7a2ca20&user=The+Expert+Developer&userId=0c83b5ebecf6&source=---header_actions--31e4c7a2ca20---------------------clap_footer------------------)

--

[](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2F_%2Frepost%2Fp%2F31e4c7a2ca20&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40TheExpertDeveloper%2Fi-reach-for-next-js-31e4c7a2ca20&user=The+Expert+Developer&userId=0c83b5ebecf6&source=---header_actions--31e4c7a2ca20---------------------repost_header------------------)

--

[](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2F_%2Fbookmark%2Fp%2F31e4c7a2ca20&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40TheExpertDeveloper%2Fi-reach-for-next-js-31e4c7a2ca20&source=---header_actions--31e4c7a2ca20---------------------bookmark_footer------------------)

[Listen](https://medium.com/m/signin?actionUrl=https%3A%2F%2Fmedium.com%2Fplans%3Fdimension%3Dpost_audio_button%26postId%3D31e4c7a2ca20&operation=register&redirect=https%3A%2F%2Fmedium.com%2F%40TheExpertDeveloper%2Fi-reach-for-next-js-31e4c7a2ca20&source=---header_actions--31e4c7a2ca20---------------------post_audio_button------------------)

Share

_The numbers aren’t even the interesting part. The interesting part is that I felt caught._

Railway, the deployment company, put up a post this week about moving their entire frontend off Next.js, and I read the whole thing standing up.

Press enter or click to view image in full size

![Image 3](https://miro.medium.com/v2/resize:fit:700/1*0pQVDd3E9GAw9X7FEJCMXw.png)

The numbers first, because they’re the headline. They went from builds taking 10-plus minutes to under two.

Six of those ten minutes, they say, were Next.js by itself, and a big chunk of that was the build just sitting there on the step that reads **_finalizing page optimization,_** wh

Read full article → ← Back to Reads

I reach for Next.js

Key Takeaways

Full Article

Related Videos