Should I use a loading state, and if so, what kind

I have a really simple doubt on wether I should use a loading state or not, and if so, what kind. My scenario is that I have a menu that loads pages on my SPA when an item is clicked. Right now it is rather fast (.1s with cache and ~.3s when not cached). However I expect this time to rise in production, specially in cases when the users's internet speed is slow. This is my page as is:

Highlighted in orange is the space where the pages are loaded. I wonder if I should use a loading state, which I'm very inclined to base on the heuristic of system status. However, which one? I don't want to implement a complex loading state if not necessary. Luke Wrobleski wrote an article back in 2013 about avoiding spinners and the usage of Skelleton Pages, which are now most everywhere. Bill Chung performed an entire research on user experience comaring spinners and with skelleton pages (see in this article).

I will most certainly use skelletons for the individual components of the page that has data fetching. However, is it too overkill for this idle time between a user clicking a link to a page and it being loaded? If so, what's the best approach? I'm over thinking this too much and maybe a simple spinner would do the trick without impacting the user?