Something else is going on. 11 simple text fields shouldn't be that slow. Do you have any summary or aggregate calculations (Sum, Count)? Are you pulling data from a related table?
There are other options for getting the exported data. You can do this server-side (most of the hosting services offer server-side scripting; you just have to ask), and, if the resulting spreadsheet isn't too big, you can have the script email to whomever needs it. Another option would be to insert the spreadsheet into a container field in the database after it's created, from which you can later extract it with a client.
But again, something funky is going on with the export. I'd look to that first.
I was pulling one field from a related record, and once I removed that the data exports at a completely acceptable speed. Thank you so much! That really saved me.
Just FYI: This comes down to how FileMaker loads records. Whenever you request data from a record, the entire record has to come down from the server to the client. So if that related table has a bunch of fields, then the entire related record has to come down - even if you only need one field. If there are multiple records involved, then the delay involved can become substantial.
If you only need one field, sometimes it’s worthwhile to use a lookup or script to copy the information from the related table over to the parent table for operations like this. It breaks normalization rules, but sometimes performance takes precedence.
Glad it’s working better.