Lets assume I build a new Single page application (SPA) on a Javascript framework such as VueJS and serve it from NodeJS.
A user on a poor connection (say on a mobile in a remote area) will have to download the whole SPA before starting to use it? Unlike a static multi-page site which might be smaller and the user should be able to start working on it much sooner.
Am I missing something? For users on poor connections are SPA's actually that great an idea? Sure high flying city dwellers will be fine but the user experience of someone on a multi-page site would be better on a poor connection?? Are there ways to mitigate that problem with an SPA and say NodeJS? Is it possible to detect the connection and route them appropriately to an alternative version/site?
If this is too open a question, please say and I will remove it but we're looking at a SPA for a rebuild and for backend users who will typically be on a decent connection fine, but I'm worried about front end users who may suffer and not have a great experience.