Network Latency – Comparing the Impact on Your WordPress Site
By Brian Jackson, Updated: October 11, 2017
A lot of articles around the web tend to primarily focus on front-end WordPress optimizations and quick ways to speed up your site. Server optimizations such as network latency are sometimes neglected or overlooked. Because of this, we thought it would be interesting to take a deeper look at the importance of network latency and the impact it has on your WordPress site when loading different regions. While a CDN can definitely help decrease network latency, your host server location is still very important, especially if you are serving visitors in a very specific geographical location. Latency matters and we’ll show you a couple reasons why.
What is Network Latency?
Network latency refers to the time and or delay that is involved in the transmission of data over a network. In other words, how long it takes for a packet of data to go from one point to another. Nowadays this is typically measured in milliseconds, however, it could be seconds depending upon the network. The closer to zero the better.
“Latency is the wait time introduced by the signal traveling the geographical distance as well as over the various pieces of communications equipment.” – Whatis.com
In other words, the further the distance the greater the latency, which equates to a longer delay. You can’t beat the speed of light when it comes to data traveling over fiber optic cables. For example, below is a map of the Google Cloud Platform network. They have thousands of miles of cable going underneath the ocean spanning the entire globe. This is one reason why it is one of the fastest networks in the world. And even with this extensive state of the art network, there’s still always going to be latency delays.
There are a couple different factors that contribute to network latency delays, which includes:
- Transmission delay: Different types of mediums, such as wireless or fiber optic connections all introduce some type of delay as they can only push out so many bits. For example, a fiber optic connection will have a lower transmission delay than a T1 line. You must also factor in the size of the packet.
- Propagation delay: This is the time it takes for the packet of data to travel. This could include distance, networking delays, etc.
- Queuing delay: If bandwidth is exceeded there can be queuing delays in which the data has to wait at the host or router. This can be affected by network congestion.
Why Network Latency is Important
The Trainline reduced latency by 0.3 seconds across their funnel and customers spent an extra £8 million (~$11.5 million) a year. – WPO Stats
Latency is especially important when it comes to businesses that serve visitors in a specific geographical location. For example, let’s say you have an e-commerce shop in Sydney, and 90% of your customers are from Australia. Your business would definitely benefit from placing your site on a server in Australia, vs hosting it in Europe or the United States. We’ll go into just how much it impacts your site below.
Comparing Google Cloud Network Latency
Distance is one of the primary reasons for latency delays. However, it is important to remember though that latency is not only affected by distance, but also by the number of hops it makes, routers in between, etc. A few ways to measure network latency include Ping, Traceroute, and MTR. In this example, we are simply going to use ping times and run a few traceroute tests. If you really want to dig into the data, you can run traceroute commands.
So we spun up a few test machines on Google Cloud Platform located in different geographical regions.
- perf1.kinsta.com (located in Iowa, USA)
- perf2.kinsta.com (located in Sydney, Australia)
- perf3.kinsta.com (located in Frankfurt, Germany)
We the utilized KeyCDN’s free Ping Test tool which allows us to test simultaneously from 14 locations. Remember, the lower the ping time the better as this directly correlates with the delay time (in milliseconds) for how long it takes the data to travel across the internet, to its destination address, and then back to you. We also utilized their traceroute tool.
Perf1 (Iowa, USA)
For the test server located in Iowa, USA, the ping times are much lower from locations that are in the United States (16 ms average ping times to Dallas). As you start to go further out to Europe or Singapore you start to experience a lot higher ping time averages (244 ms average ping times to Singapore).
And if we compare the Traceroute, you can see an example 7 additional network hops are needed to simply travel from Iowa, USA to Frankfurt, Germany (compared to 10 hops from Dallas). This is why it is important to remember, that network hops also factor into network latency.
Perf2 (Sydney, Australia)
For the test server located in Sydney, Australia, the ping times are much lower from locations in Australia and Asia-Pacific (1 ms average ping times to Sydney). As you start to go further out to Europe or South America you start to experience a lot higher ping time averages (319 ms average ping times to Sao Paulo).
And if we compare the Traceroute, you can see an example 14 additional network hops are needed to simply travel from Sydney, Australia to Frankfurt, Germany.
Perf3 (Frankfurt, Germany)
For the test server located in Frankfurt, Germany, the ping times are much lower from locations in Europe and even the United States, probably due to a fast backbone connection between the two (7 ms average ping times to Amsterdam). As you start to go further out to Asia-Pacific or South America you start to experience a lot higher ping time averages (308 ms average ping times to Singapore).
And if we compare the Traceroute, you can see an example 11 additional network hops are needed to simply travel from Frankfurt, Germany to Sao Paulo, Brazil.
So as you can see above, the greater the distance directly correlates with higher ping times and additional network hops which make up network latency. This is why you should strategically position your WordPress site to decrease both of these factors.
Comparing Google Cloud Latency Between Regions
Above we are testing Ping times from where the servers are located, in correlation with the ping servers. But what about latency between Google Cloud Platform regions themselves? Geek Flare ran a great test between 9 of the different regions. This can give you a quick overview of the delay that happens due to latency when placed in one region versus another.
Make sure to also check out our article on Google Cloud vs AWS to see differences in network latency.
Comparing Page Load Times
And of course, we leave out the total page load times. In fact, this is where some of the most interesting data is. However, remember that this includes other factors such as TTFB. All three test sites are identical, running a fresh install of WordPress, with the Twenty Seventeen theme installed. We are also utilizing Pingdom, so the times are being measured from their test server locations.
Perf 1 (Iowa, USA)
We ran speed tests from three different test locations with our server located in Iowa, USA, and below are the results.
As we can see above, there is a huge difference between loading a site from within the United States (close to the hosting server) and loading from across the globe.
Perf 2 (Sydney, Australia)
We ran speed tests from three different test locations with our server located in Sydney, Australia, and below are the results.
As we can see above, there is a huge difference between loading a site from within Australia (close to the hosting server) and loading from across the globe.
Perf 3 (Frankfurt, Germany)
We ran speed tests from three different test locations with our server located in Frankfurt, Germany, and below are the results.
As we can see above, there is a huge difference between loading a site from within Europe (close to the hosting server) and loading from across the globe.
If those page load tests don’t convince you, we don’t know what will! For example, the test site in Iowa, USA, took only 368 ms to load from Dallas. But it took 2.14 seconds to load from Sydney, Australia. This is why location matters! And again, you can help decrease the total load times by putting your media assets closer to your visitors with a CDN. But you will always encounter load time and latency from your host server, so choose wisely.
Choosing the Right Location to Host Your WordPress Site
Most WordPress hosting providers typically allow you to choose from different locations to host your site. Here at Kinsta, we have all 12 Google Cloud Platform locations now available. This lets you strategically place your site where you need to ensure low latency and TTFB, along with blazing fast load times. You can also choose a different location for each separate site.
Not sure which one to pick? Here are a few tips below.
Tip 1 – Check Google Analytics
One of the very first things you can do is look at the geographical location of your visitors in Google Analytics. In this example below, you can see that over 90% of the traffic is coming from the United States. So in most cases, you would want to place your WordPress site on a server in the United States. You could filter down the data to cities, but we would typically recommend a central location like Iowa, USA.
Tip 2 – Check E-Commerce Data
If you run an e-commerce store, make sure to also check to see where your customers are coming from. This is of course how you generate revenue, so these are your most important visitors. This should coincide with your traffic above, however, this is not always the case. If you have e-commerce data setup or Goals, you can easily overlay that information on top of the Geo data to make a more informed decision.
Tip 3 – Do a Quick Latency Test
There are a lot of handy free tools out there to measure latency from your current location for different cloud providers. This can help you quickly evaluate which region might be the best choice for your site.
- GCP Ping (measure latency to Google Cloud Platform regions)
- CloudPing.info (measure latency to Amazon Web Services regions)
- Azure Latency Test (measure latency to Azure regions)
You can also utilize CloudHarmony, which is a cloud comparison tool. You can test things such as latency, DNS, uplink, and downlink.
Quick Ways to Reduce Network Latency
To summarize, here a few quick ways to reduce network latency.
- As we showed you above, placing your WordPress site on a server closer to your visitors should be priority number one. This helps reduce ping times and network hops.
- Utilize a content delivery network (CDN) to serve cached assets from POPs around the globe. This helps negate the network latency for visitors who might not be close to your host server.
- Take advantage of the HTTP/2 protocol to minimize the number of round trips, thanks to parallelization. HTTP/2 is enabled on all Kinsta servers. The only requirements is that your site is running over HTTPS.
- Reduce the number of external HTTP requests. Each of these can have their own added latency based on the location of their server. Check out our post on analyzing third-party performance.
- Use a premium DNS provider with fast lookup times.
- Utilize prefetch and prerender to perform tasks behind the scenes while the page loads.
Hopefully now you understand a little more about network latency, why it matters, and how it impacts your WordPress site. To ensure fast load times make sure to choose a server with your host that is closest to your visitors and customers. What are your thoughts? Have you ever experienced slow load times due to a website being placed in the wrong location? Let us know below in the comments.