Note, I've seen: How fast is too fast?, and What to do when loading is TOO fast? so I want to clarify the non-duplicity: I'm not asking about the animations, but more or less about the application in general. There are no animations for this apart from the uncontrollable browser reactions, so there's nothing to be modified on that end.
I've begun building a product that (one day, maybe 20 years from now) I plan to market and sell and attempt to commercialize. This is a web application, I'm trying to keep the details a secret so I'll just note that it's a packable software application, that an end-user could purchase and install.
A key selling point of this application is that I built it to be fast, and I mean really fast. There's a point where loading on a web browser has no delay, as in, the page has reloaded or forwarded before the mouse click is raised. It's fast. I only noticed this being a problem today as I was doing some testing, and I sat here for about 30 seconds wondering if it did what I asked, only to find out that it had been done with that the whole time.
Now being a developer, I've noticed that 98% of the
web applications I use (Stack Exchange included) have a latency (some being very small, 100ms or so), you noticed that something took some time. This is not always a bad thing. The user has the opportunity to see the application transition from one page to the next, and they notice the change. If it's fast enough, the user may not notice, at least in my experience. Usually I wouldn't worry about this, as I would assume that over the internet loading will become noticeable and such, but the problem with this application is that I'm already loading over the internet, and it's still god-awfully fast.
So, to my question: is it necessary to artificially slow down an application so that there is a noticeable latency, even if it's tiny, or is this a non-issue? I'm particularly interested in any research into this that might help influence the decision.