Begin with the audience
Identify where the people using the application connect from. A city close to one audience may be far from another. Compare actual routes from representative networks when you have a real deployment to measure.
Include dependencies
The application may call a database, API, authentication provider or storage service in another region. A nearby web server that waits for a distant dependency can still feel slow. Map the complete request path before moving only one component.
Plan data and recovery
Location can matter for contracts, data handling and recovery arrangements. A city name alone does not establish compliance or an independent failure boundary. Document where live data and backup copies are stored and who can access them.
Test a realistic workload
Measure the application action people use, not only a ping. Compare response time, failure behaviour and throughput where relevant. Use more than one time period and record the test method. Select a location that fits your audience, dependencies and operational requirements together.