Actually the static address bar and the refresh button behavior makes it obvious.

What?

Most SPAs use full on routing. You can not distinguish refresh and address bar behavior between a SPA and static pages.

Furthermore, SPAs integrates perfectly with the browsers navigation stack.

Where does this bs come from?

Because less than 1% of actual SPAs use those things. Hell, look at HN's search page in the bottom if you want an example. You can load entire HN by the time it loads up and searches something.

Prefect example of the sufficiently advanced compiler argument.

HN's search is hosted on Algolia, and is not a part of the HN "App".

Hacker news is not a SPA.

Algolia's search is a SPA, but is perfectly utilizes the search so you can refresh a page (besides the error that they don't use page-based search), and is largely indistinguishable from a non-SPA site.

> You can load entire HN

You obviously have not context what so ever on how much content is hosted on HN.

Yes, I am well aware it is separate from HN. That is why I called it HN's search page.

You underestimate how fast modern internet is. With MPA website like HN there is no need to wait for any script to render first.