All of the above. Like anything else online, things take longer to travel the internet then inside a wired LAN.

If you have your queries setup right, internet speed could be an issue (first thing I'd check), then there are a thousand other "little" things that are unlikely, but possible, (like do you have a firewall or anything that is delaying the traffic for some reason, unlikely).

Other people connecting to the same server sending requests (for their SQL servers) can also affect you, the server can only handle so many things going on at one time. I'm not sure if you seen when Richard changed the website from a "public" hosted server to a private server, the website became MUCH more responsive. It's just more expensive.

Thank you! I appreciate your response.

You need to find out which operations take the most time to process and find specific fixes for them -- there is usually no one-size-fits-all solution here.  Usually, complex queries and/or queries with many iterations (inside loops, run frequently, etc.) are the culprits.

Even "fast" Internet speed is nowhere nearly as fast as local hard drive speed.  An SSD hard drive can transfer at about 400 megabytes/sec, which is over ten times the Internet speed most people have (about 50 - 300 megaBITS per sec).  You really have to design your forms, reports, etc. to minimize and optimize data retrievals as much as possible in order to accommodate the *drastic* drop in data transfer speed.

And that's another issue to look into: are your forms, queries, reports, VBA code, everything designed specifically for minimizing and optimizing data transfers?

Pass-through queries don't automatically speed things up.  It is the *amount of data* being transferred and the frequency at which transfers occur.  You can have pass-through queries that aren't efficient in both aspects.  In my video below, my Access app uses no pass-through queries at all.  Yet many of the operations are of acceptable speed:

     https://www.youtube.com/watch?v=IJyKZRRWHnU

So the most important aspect, in my opinion, is minimizing and optimizing data transfer, which is important not just for online access, but local access as well.

Thank you, Kevin Yip, for your input. I am interested in learning more about minimizing and optimizing data transfers. I haven't needed to address this before; it's only now that I'm dealing with data "in the cloud" that the issue has arisen. Where can I learn this technique? Your YouTube video was interesting, but it did not cover the "how-to" aspect I need to know. Does Richard have a video on this topic? Thanks again for your suggestion.

You minimize data transfer by (1) retrieving as few rows as you can, (2) as few columns as you can, and (3) having as few retrievals as you can.  As I said, you need to inspect every single component in your app.  What is the recordsource of your form?  If it's the entire table, how many rows are in the table?  And do you really need to retrieve all those rows for the form?  If your form is continuous, how many rows does it show?  Can you make it a single form that shows only one row?  In your VBA code, how many records does OpenRecordset retrieve, and can you minimize that?  If you have append queries, how many rows are being appended, and can you improve that?  I don't know if Richard has any courses like that, but if he does, these will most certainly be the key points.  Anything and everything in your app that retrieves and uploads records, you need to find out (a) how many records they actually retrieve and upload, and (b) see if you can minimize that.

That is very clearly stated. I understand. Thank you!