The short answer is "yes". Your application has a purpose and users, so its quality and performance can be evaluated relative to its purpose and its users.
The implied question of how to test it is one that can't be answered without more information. I'd consider these questions:
- How will users interact with the application?
- Will users be trained or not?
- How many users will be using the application at any given time?
- What expectations do users have of the application?
- What external requirements (if any) exist (e.g. is there an expectation that the application will be available at all times without exception?)?
- What level of control will there be over the server side of the application? (If you control the server hosting and users connect via a client, you don't need to specify minimum architecture for the server - or deal with users trying to run the server on underpowered systems)
That's just a starting point. I think you need to consider the requirements or user stories of your application and use those to develop your starting points for testing. If you don't have documented requirements or user stories, it might be worth your time to start there.