---
title: "Comment by Srashti on \"5 React JS Tricks to Improve Site Speed and Efficiency in 2026\" | Hashnode"
description: "Great write-up. As someone still getting my bearings with intermediate React, the distinction you made about not over-using useMemo for cheap computations like"
url: "https://hashnode.com/posts/5-react-js-tricks-to-improve-site-speed-and-efficiency-in-2026/6a293371b1d78068b4e772bd/comment/6a293aeea645a6b0d5d96425"
---

[Discussion](https://hashnode.com/posts/5-react-js-tricks-to-improve-site-speed-and-efficiency-in-2026/6a293371b1d78068b4e772bd)

Comment [5 React JS Tricks to Improve Site Speed and Efficiency in 2026](https://hashnode.com/posts/5-react-js-tricks-to-improve-site-speed-and-efficiency-in-2026/6a293371b1d78068b4e772bd)

[Srashti](https://hashnode.com/@srashtii)

[Jun 10](https://hashnode.com/posts/5-react-js-tricks-to-improve-site-speed-and-efficiency-in-2026/6a293371b1d78068b4e772bd/comment/6a293aeea645a6b0d5d96425)

Great write-up. As someone still getting my bearings with intermediate React, the distinction you made about not over-using useMemo for cheap computations like string concatenation clears up a lot of conflicting advice I’ve seen online.

I do have a practical question regarding state collocation versus using atomic state libraries like Zustand or Jotai. For a beginner trying to build good habits, at what point does a project actually warrant moving away from standard prop-drilling or basic context and introducing a third-party state manager? Is there a specific architectural "tipping point" or metric you look for before making that jump?

Thanks for sharing these insights!
