Internet Speed Tests

> Meetinghouse Technology > Meetinghouse Networking

Internet connection speeds should be tested periodically to identify current connection speeds and verify that internet service providers (ISPs) are meeting contracted service levels.

Speed Test

There are several online tools that can measure internet connection speeds. For example, speedtest.net can be used to measure the connection ping, upload speed, and download speed of the network.

• Ping measures the latency of the internet connection in milliseconds (ms). It is the measure of the speed of a reply from a network device. Smaller ping results mean the connection is more responsive, which helps tasks like streaming, webcasts, and personal video conferencing.
• Upload Speed measures how fast the connection can send data to others over the internet and is measured in megabits per second (Mbps). The ISP upload speed will typically be lower than the download speed. Upload speed is important for meetinghouse tasks such as sending MLS/LCR data to Church headquarters, streaming webcasts, and participating in personal video conferencing.
• Download Speed measures how fast the connection can receive data from the internet and is measured in megabits per second (Mbps). The ISP download speed will typically be higher than the upload speed. Download speed is important for meetinghouse tasks such as streaming Church media for lessons, receiving webcasts, and participating in personal video conferencing.

There are two methods to perform a throughput test on your network, depending on your access level and preferred workflow. 

Method 1: Quick Throughput Test (Direct Access)   

CNM SPEED TEST Church Network Manager (CNM) provides an alternative method for testing network speeds. This test measures the throughput from the meetinghouse firewall to the Meraki dashboard. While this test differs from the speedtest.net approach, it offers unique advantages and insights.  

Key Differences from the speedtest.net method: Tests from an actual device on the network through the entire network infrastructure. This provides results that are more indicative of what users on the network will experience in real-world scenarios. Requires physical access to a device on the network.  

CNM method: Tests the connection speed from the firewall to the Meraki dashboard. While this doesn't reflect the end-user experience as directly, it provides valuable data about the network's core connectivity. The primary advantage of this method is that it can be performed remotely without requiring physical presence at the meetinghouse.  

How to Run a CNM Speed Test  

1. Log in to Church Network Manager at CNM.churchofjesuschrist.org.  
2. From the property screen, select the building you want to test.  
3. Select the network for the building. 
4. Click the menu icon (three dots) in the upper right corner of the screen.  
5. Select Throughput Test from the menu.  
6. The test will run and display results showing the speed in megabits per second (Mbps).  

This represents the throughput between the firewall and the Meraki dashboard. 

Method 2: Throughput Test via Area Reports 

If you have access to Area Reports, you can run throughput tests directly from network performance data: 

1. Open Area Reports from the main dashboard
2. Locate the device or access point you want to test 
3. In the Throughput column, click the value or test icon 
4. The system will initiate a throughput test for that specific device 
5. Results will populate in the report view 

Understanding Your Results 

Both methods provide: 

• Download speed - Data received from the internet 

• Upload speed - Data sent to the internet 

• Latency/Ping - Response time to servers 

Note: For accurate results, ensure no heavy network activity is occurring during the test (large downloads, video streaming, etc.). 

Actions for Poor Results

There are various reasons why a speed test will report a slow internet connection. The ISP may not be delivering the agreed service level, but it is best to rule out other issues that can affect speed test results before contacting the ISP. The following actions can help ensure that speed tests are accurate:

1. Use a wired LAN connection: Run the speed test from a computer with a wired Ethernet connection (instead of Wi-Fi) to eliminate the chance of wireless interference.
2. Reduce network traffic: Try running the test when no one else is using the network, since other network traffic will slow down performance. You can get a general overview of the current usage by logging into Church Network Manager (CNM.churchofjesuschrist.org). You should also shut down any programs and stop any downloads that are using the internet connection.
3. Reboot the ISP Modem: Just as periodically rebooting computers can fix system issues and slowdowns, rebooting the ISP modem may help resolve internet performance issues. You can reboot or “power cycle” a modem simply by removing the modem power cable, waiting one minute, and then plugging the power cable back in.
4. Run multiple tests: Run a speed test multiple times to get the best understanding of the connection speed. You may want to run tests at different times and on different days to understand whether issues are related to specific times.

If tests continue to report that internet speeds are below the contracted ISP service levels, please coordinate with the facility manager to contact the ISP to troubleshoot the issue. Inform the ISP of the test results and the steps that have already been taken.

Additional Actions

• Review wireless best practices: There are other factors that affect the performance of the meetinghouse internet connections. Please review the Improving Internet Access article.
• Check the firewall: Run a filter check to verify that the firewall is installed and activated correctly. Simply visit filter.ChurchofJesusChrist.org using a computer inside the building. If the page displays an X, the firewall is not filtering content and could be causing a problem.