Start by naming the slow task. A large file transfer, delayed button response and interrupted call need different observations. A useful comparison changes one condition and keeps the device, network and destination the same.
Work through the checks
- Try the task without the VPN and note what feels slow: starting, transferring, responding or staying connected.
- Pause optional downloads or uploads you control. Do not interrupt someone else’s work on a shared network.
- Connect the VPN and repeat the same task. If you use a speed test, keep the test endpoint and conditions consistent.
- Record at least one normal session rather than selecting only the best reading. Include the approximate time and any other traffic you could not control.
- If the app provides documented location choices, test a single alternative and record it. Location alone does not guarantee a faster result.
Read the result
| What you observe | Next step |
|---|---|
| The task is slow in both tests | Check the base network, destination and device. |
| Only large transfers are slow | Record transfer size, direction and time. |
| Calls or games pause despite fast downloads | Look at latency, timing variation and interruptions. |
Make the comparison useful
For a file, record the same download and its elapsed time. For a call, record audible gaps or disconnects. Comparing a download-speed number with a call’s responsiveness would not answer the same question.
Before changing more settings
No measured Zenshield performance advantage is claimed here. If the comparison consistently favors using the ordinary connection, keep that evidence and ask support about the specific task.
Use the support-request template if you need to send the result. The reference guidance explains the underlying network or platform behavior; exact Zenshield controls depend on the installed app version.