This may be a novice’s question. I like the look of “one-page” websites where the user can scroll down the page to see the entire website. However, I have roughly 20 screen shots that I want to show on the website in the “features” section.
There will be a lot of users visiting from parts of the world with slow internet connections, so it’s that much more important to have fast loading times.
Here is how I understand it: the loading time needed when a user goes to an initial website is determined by how much data is contained on that initial page. It’s not how much data is contained in the sum of all pages. Is that correct?
If it is correct, then my logic would follow that if I create a list of links on the “features” page like the list seen below, then I can reduce the loading time the user experiences through only showing 1 or 2 images for each feature, and the user needs to click on each feature link below to see the image(s) associated with that feature. So, for example, the user will only see screen shots associated with “Job management” when they click the “Job management” link, thus reducing the user’s initial wait time. Is that correct?
Paperless timesheets
GPS location tracking
Job management
Pictures and notes
Qualification tags
Staff schedules
Forms
Dispatch
Quotes, estimates, invoices
Accept mobile payments
Offline mode
Integrations: QuickBooks,
Salesforce, more
Languages
Custom features