Defining geographic coverage
We select the regions to be tested against your user distribution and market objectives, and refresh coverage periodically.
Managed Services
Location Testing Services
We measure how the user experience changes by geography.
Schedule a meetingLocation Testing Services
Location testing measures how an application behaves when accessed from different geographic locations. Response times, content delivery, localisation and regional restrictions are tested through genuine access from your target markets.
What this service solves
Tests run from the head office network do not reflect every user's experience. Users in distant geographies encounter different latency, different content delivery nodes and in some cases different content altogether.
For organisations with an international user base, those differences show up directly in conversion. We measure the experience separately from each target market and identify the layer the difference comes from.
Our scope
Regional performance measurement
We measure response times and page load metrics separately from each region and report the differences between them.
Content delivery validation
We check that the content delivery network behaves as expected in every region and examine caching behaviour.
Localisation checks
We validate language, currency, date format and regional content rules, and report localisation gaps.
Regional restriction and access testing
We check that geographic restrictions and routing rules work correctly, and identify access barriers.
How do we work?
We plan around your release rhythm, manage the operation and improve it in every cycle.
Planning
We define scope, test levels and success criteria against your release calendar. Environment and test data requirements are resolved before the work begins.
Management
We take on team, tool and environment management. Progress is reported regularly against defined KPIs.
Execution
We run the tests and prioritise the findings. We track closure together with your development teams.
Improvement
At the end of every cycle we review scope, automation rate and escaped defect rate. The priorities for the next cycle are set from that review.
Virgosol
How technology supports the service
We run regional load and performance measurement with Loadmance; geographic distribution of load produces realistic traffic from your target markets. Functional validation runs through AutoRunner against regional configurations.
What you receive
Deliverables
- A target geography coverage plan
- A region-level performance measurement report
- Content delivery and caching validation results
- A localisation findings list
- Regional restriction and routing test results
What changes for the business
- Differences in international user experience become measured
- The effect of content delivery investment is visible region by region
- Localisation gaps are found before release
- New market entries are planned on measurement
Frequently Asked Questions
Which regions should be covered?
Coverage is determined by your current user distribution and market objectives. We prioritise regions with high user concentration and the new markets you plan to enter.
Can this not be done over a VPN?
A VPN does not fully reproduce genuine regional access; routing path and content delivery behaviour can differ. We take measurements over real infrastructure in the target regions.
How do you identify the source of a performance difference?
We separate measurement across the network, content delivery and application layers, so we can report whether the difference comes from infrastructure or from application behaviour.
Does localisation testing include translation review?
We cover format, unit and regional rule validation. Language quality assessment is a separate discipline; if you want it in scope we consider it together during planning.
Let us measure your regional experience together
Complete the form and we will discuss your target markets, your user distribution and your content delivery setup.