Latency is the time it takes for data to travel between your server and visitors. Low latency means snappy page loads. High latency means waiting. And waiting. And waiting.
The Latency Checker pings your server from Google Cloud Platform locations around the world, showing you exactly how your site performs globally.
What This Tool Measures
The Latency Checker tests response times from multiple GCP regions:
- North America (multiple US locations)
- South America
- Europe (multiple locations)
- Asia Pacific (multiple locations)
- Australia
For each location, you’ll see:
- Current latency – Most recent test result
- Average latency – Mean of recent tests
- Fastest/Slowest – Range of results
The test measures round-trip time in milliseconds. Lower is better.
Running a Latency Test
One-Time Test
- Go to Speedtest Pro > Latency Testing.
- Click Run Once Test. The test runs immediately.
- View results in the table below. Each region shows its latency.
Continuous Testing
For better data, run continuous tests.
- Click Start Continuous Testing. Tests run automatically every hour.
- Results accumulate over time. More data means more accurate averages.
- Click Stop Testing when you have enough data.
Continuous testing is helpful for:
- Finding performance patterns throughout the day
- Detecting intermittent issues
- Establishing baseline performance
Understanding Latency Results
What’s Good?
| Latency | Rating | User Experience |
|---|---|---|
| Under 100ms | Excellent | Instant feel |
| 100-200ms | Good | Barely noticeable |
| 200-400ms | Okay | Slight delay |
| 400-700ms | Slow | Noticeable waiting |
| Over 700ms | Poor | Frustrating |
Reading the Table
The results table shows:
| Column | What It Shows |
|---|---|
| Region | GCP location name |
| Latency | Most recent ping time |
| Average | Mean of all tests |
| Fastest | Best result recorded |
| Slowest | Worst result recorded |
Large gaps between fastest and slowest suggest inconsistent performance.
The Selected Region
During setup, you chose a GCP region closest to your target audience. This region is highlighted in results.
Pay special attention to this number. It represents the experience your main visitors will have.
What Affects Latency?
Physical Distance
The biggest factor. Data can only travel so fast through cables and routers.
Example: A server in New York will always have higher latency for visitors in Australia than for visitors in Boston.
What you can do: Choose hosting located near your visitors, or use a CDN.
Network Quality
Some routes are faster than others. Premium networks with direct peering beat budget networks with multiple hops.
What you can do: Choose a host with good network infrastructure. Premium hosts often advertise their network quality.
Server Response Time
How fast your server processes the request before sending a response.
What you can do: Optimize WordPress, use caching, upgrade hosting if needed.
Internet Congestion
Traffic on the internet varies. Peak hours can slow things down.
What you can do: Not much. This is why continuous testing matters for averages.
Filtering Results by Time
Use the time range dropdown to focus on specific periods:
- 24 Hours – Most recent day
- 7 Days – Past week
- 30 Days – Past month
- All Time – Everything recorded
Comparing different time ranges helps spot trends or problems.
Interpreting Patterns
All Regions Slow
Your server is the problem. Check:
- Server performance benchmarks
- Hosting resource usage
- Whether caching is working
Specific Region Slow
Distance or routing issue. Options:
- Accept it (if that region isn’t important to you)
- Use a CDN with edge locations in that region
- Consider multi-region hosting
Intermittent Slowdowns
Could be:
- Shared hosting resource contention
- Network issues between hops
- Server under temporary load
Run continuous tests to understand the pattern.
Time-Based Patterns
If latency increases at certain times:
- Traffic spikes on your site
- Scheduled backups or tasks running
- Peak internet usage times
Using Latency Data
Choosing a CDN
A CDN places copies of your content on servers worldwide. Latency data shows which regions need help most.
If latency is bad in:
- Europe – Choose a CDN with European edge servers
- Asia Pacific – Look for CDN presence in Singapore, Tokyo, Sydney
- South America – Fewer CDN options exist, but some cover it
Deciding on Hosting Location
If you’re choosing or moving hosts:
- Run latency tests first to establish a baseline
- Identify your primary audience (check your analytics)
- Choose a host near that audience
- Re-test after migration to verify improvement
Justifying Infrastructure Investments
Latency data helps make the business case for:
- CDN subscriptions
- Better hosting
- Multi-region setups
Show stakeholders the numbers. “Our Australian visitors wait 600ms before anything loads” is more compelling than “I think our site is slow in Australia.”
How Often to Test
| Goal | Frequency |
|---|---|
| Baseline establishment | Continuous for 1 week |
| Regular monitoring | Weekly one-time tests |
| After changes | Immediately, then daily for a week |
| Performance investigation | Continuous until resolved |
Managing Test Data
Deleting Old Results
Over time, you might accumulate lots of test data. To clean up:
- Click Delete All Results (if available)
- Or let old results age out naturally
Why Delete?
- Keeps the database light
- Removes outdated baseline data after hosting changes
- Fresh start after major configuration changes
Tips for Lower Latency
Use a CDN
Biggest impact for global audiences. Options:
- Cloudflare – Free tier available, easy setup
- BunnyCDN – Affordable, global coverage
- KeyCDN – Pay-per-use pricing
Choose Strategic Hosting Location
If 80% of your visitors are in the US, host in the US. If they’re in Europe, host in Europe.
Enable HTTP/2 or HTTP/3
Modern protocols reduce latency through:
- Multiplexing (multiple requests on one connection)
- Header compression
- Server push
Most modern hosts support these. Check with your host if unsure.
Reduce DNS Lookups
Each external resource requires a DNS lookup. Minimize:
- External fonts (self-host if possible)
- Multiple CDN domains
- Unnecessary third-party scripts
Optimize Your Server
Even perfect network conditions don’t help if your server is slow:
- Enable caching
- Use PHP 8.0+
- Enable OPcache
- Optimize database queries