TX/RX rate on the status page consistently much higher than actually tested speed

TX/RX rate on the status page consistently much higher than actually tested speed

TX/RX rate on the status page consistently much higher than actually tested speed
TX/RX rate on the status page consistently much higher than actually tested speed
Friday - last edited Yesterday
Model: CPE710  
Hardware Version: V2
Firmware Version: 1.0.2 Build 20230307 Rel. 59163 (5553)

On the status page on my client status page it consistently show TX/RX speeds like this:

TX Rate: 585.0Mbps

RX Rate: 520.0Mbps

 

But when i run the test tool I get speeds like this:

236 Mbps RX  261 Mbps TX

 

The latter corresponding with speeds I actually see using iPerf, internet speed test, etc.

 

Whats the difference?

  0      
  0      
#1
Options
6 Reply
Re:TX/RX rate on the status page consistently much higher than actually tested speed
Monday - last edited Monday

Hi  @wifipete 

 

The difference between the **TX/RX rates** shown on your client status page and the **actual speeds** you measure with tools like iPerf or internet speed tests comes down to what each metric represents:

1. **TX/RX Rates on the Status Page (585 Mbps TX / 520 Mbps RX)**
   - These values represent the **PHY (physical layer) link rate** between your device and the Wi-Fi access point (AP).
   - This is the **maximum theoretical data rate** negotiated based on:
     - Wi-Fi standard (e.g., Wi-Fi 5/6/6E)
     - Signal strength (RSSI)
     - Channel width (e.g., 80 MHz, 160 MHz)
     - Modulation (e.g., 256-QAM, 1024-QAM)
     - MIMO streams (e.g., 2x2, 4x4)


   - **This is not the actual throughput you experience**—it’s just the "advertised" speed of the wireless link.

 

2. **Actual Speeds from iPerf/Speed Tests (~236 Mbps RX / 261 Mbps TX)**
   - These reflect **real-world throughput**, which is always lower than the PHY rate due to:
     - **Wi-Fi overhead**: Protocol headers, acknowledgments (ACKs), retransmissions, and contention for airtime.
     - **Half-duplex nature**: Wi-Fi can't transmit and receive simultaneously at full speed.
     - **Interference**: Other networks, devices, or physical obstacles reducing efficiency.
     - **Device capabilities**: Your client device or AP may have processing limitations.
     - **TCP/IP overhead**: Encryption, packet headers, and other network stack inefficiencies.

 

With today's wireless environmental conditions, your speed measurement results are more than satisfactory.

 

  0  
  0  
#2
Options
Re:TX/RX rate on the status page consistently much higher than actually tested speed
Monday

  @Vincent-TP Thanks for letting me know my speeds are more than adequate lol...

 

Do you know what tests are run from the tests page of the CPE710?  going from 500 in theory to less than half of that in practice seems weird.

  0  
  0  
#3
Options
Re:TX/RX rate on the status page consistently much higher than actually tested speed
Yesterday - last edited Yesterday

Hi  @wifipete 

 

CPE Status Page (e.g., 585 Mbps TX / 520 Mbps RX)

  • This shows the PHY (physical layer) link rate, which is the theoretical maximum speed negotiated between your device and the Wi-Fi access point.
  • It depends on:
    • Wi-Fi standard (e.g., 802.11ac/ax/be)
    • Channel width (e.g., 80 MHz, 160 MHz)
    • MIMO streams (e.g., 2x2, 4x4)
    • Modulation scheme (e.g., 256-QAM, 1024-QAM)

This combination of parameters determines the theoretical maximum PHY rate, which the CPE reads from the Wi-Fi chipset and displays on the status page.

 

Why the significant discrepancy with actual speed tests (iPerf/SpeedTest)? 

Actual measured speeds (e.g., 236 Mbps RX / 261 Mbps TX) are much lower than PHY rates due to:

Factor Impact
Wi-Fi Protocol Overhead ACK frames, RTS/CTS, Beacon frames, etc. consume bandwidth
Half-Duplex Contention Wi-Fi is half-duplex - devices cannot transmit/receive simultaneously
Interference & Retransmissions Signal interference causes packet retransmissions, reducing effective throughput
TCP/IP Overhead Packet headers (TCP/IP, encryption, etc.) consume portion of bandwidth
Multi-Device Sharing Other Wi-Fi devices or neighboring networks occupy channel time
Client Device Limitations Mobile/computer Wi-Fi chipsets may not support maximum rates

Rule of thumb: Actual throughput ≈ 50%-70% of PHY rate (in ideal conditions),

but always be lower in interference-heavy environments (as in your test results showing ~40%).

 

  0  
  0  
#4
Options
Re:TX/RX rate on the status page consistently much higher than actually tested speed
Yesterday

  @Vincent-TP why is the theoretical maximum always changing? you would think in a given environment/setup the theoretical maximum would not change moment to moment?

  0  
  0  
#5
Options
Re:TX/RX rate on the status page consistently much higher than actually tested speed
Yesterday

  @wifipete 

 

Because they are not fixed, especailly the signal strength:

 

There is no given unchangeable wireless environment, and what's more, it's always changing.

Here are the key factors that can dynamically affect wireless environments :

Physical obstacles (walls, metal cabinets, human bodies), Wi-Fi interference (neighboring routers, co-channel contention), non-Wi-Fi interference (microwaves, Bluetooth devices, wireless cameras, radar signals), electronic device interference (low-quality LED lights, AC motors, smart home gadgets), network load fluctuations (multiple connected devices, high-bandwidth applications), weather effects (heavy rain, high humidity), building materials (concrete, metal structures), protocol behaviors (MCS adaptation, DFS channel switching), device variations (smartphone antenna performance, power-saving modes), moving objects (elevators, opening/closing doors), sudden signal sources (drones, temporary hotspots), and background traffic (system updates, cloud sync) can all dynamically alter wireless environments.

  0  
  0  
#6
Options
Re:TX/RX rate on the status page consistently much higher than actually tested speed
Yesterday

  @Vincent-TP These are two fixed Point to Point CPE710 devices, line of sight, about 300ft apart ...  nothing is changing.

  0  
  0  
#7
Options