Consider the following NFRs:

• Performance:

• What will the application load time be for users?

• How can we handle network latency?

• Security and compliance:

• How can we secure an application from unauthorized access,

• Protect an application from malicious attacks,

• And adhere to local laws and audit requirements?

• Recoverability:

• How can we recover an application from an outage,

• And minimize recovery time in the event of an outage?

• How can we recover lost data?

• Maintainability:

• How can we ensure application monitoring and alerts?

• How can we ensure application support?

• Reliability:

• How can we make sure the application performs consistently,

• And inspect and correct glitches?

• Availability:

• How can we ensure the high availability of an application,

• And make an application fault-tolerant

Scalability:

• How can we meet the increasing demand for resources?

• How can we achieve a good scale for a sudden spike in utilization?

• Usability:

• How can we simplify an application's use,

• Achieve a seamless user experience,

• And make the application accessible to a diverse set of users?

https://www.geeksforgeeks.org/non-functional-requirements-in-software-engineering/