Next.js uses Client-Side Navigation to load the pages faster.
The Client-Side Navigation is enabled by the Link component and only between the pages in the same Next.js app.
So, if you add a link using an a tag then the faster pages switch won’t work!
What’s a Client-side navigation?
Client-side navigation is the transition of pages using JavaScript rather than the default transition/navigation by the browser itself.
When you use an a tag to switch between pages, the browser does a full refresh of a page but when you use JavaScript, it won’t does not load the full page.
How to check if the Client-side navigation is working?
Refer to this official gif from Next.js.

- First of all, add a link using Link component so that you can navigate to each page using link from another page.
- Then, as you can see, you can change any CSS property of any element that exists on multiple pages.
- In our case, we are changing the background-color of the html tag itself on both pages!
- Now, simple visit both the pages and see if the background-color is there. If so, then the Client-side navigation is working.
- If not, make sure you have added the Link tag to navigate to both pages.
Prefetch
Next.js also prefetches the code for the linked pages that are added using a Link component when they appear in the browser’s viewport. So, by the time you click on that Link, your code is already loaded and it gets served within seconds.
Code splitting
In Next.js, each page loads what’s necessary and that is achieved by splitting the code. That means, when you load one page, code for other pages is not served, which makes the initial rendering faster.
Code splitting helps create isolated pages so that if one page throws an error, other pages won’t get affected by it.
browsers components import link react router