Separate Swedish traffic from the wider audience
List the networks and devices your Swedish users actually use. Is the service mainly a local application, or do customers in other markets need the same response time? Use that distinction to choose test locations instead of treating every Nordic visitor as one audience.
Test the regional version of your workload
Run the same page load, API request or file transfer from each intended market. Include a normal busy period and retain the results with the test date. Does Stockholm perform consistently for the whole audience, or does the application need a different delivery strategy?
Decide how distant users receive content
For a Sweden-focused application that also serves visitors elsewhere, separate content delivery from database writes. Static assets may benefit from caching closer to the visitor while account changes still reach the primary application. Check which requests can be cached without exposing private or outdated information.
Keep the recovery site independent of the primary
A second machine is useful only when it covers the failure you are planning for. Ask whether the recovery location shares an operator or upstream dependency with the Stockholm primary. Restore a recent backup there and record the steps needed to direct users to the recovered service.