Why ASUS Merlin Speed Tests Are Slow and How to Diagnose Them

What an ASUS Merlin Speed Test Result Shows

An ASUS Merlin speed test measures performance between a client device and a selected test server. The result usually includes download speed, upload speed, and latency. It does not measure the advertised ISP rate in isolation. The path includes the modem or fiber terminal, router processing, Ethernet or Wi-Fi, the selected server, and current network traffic.

A lower result is significant when it remains consistent across several tests, different test servers, and a wired client. A single result on Wi-Fi is less conclusive because radio interference, signal strength, and other connected devices can change the measurement.

Common Causes of Slow ASUS Merlin Speed Tests

Wi-Fi overhead and radio interference

Wi-Fi commonly produces lower speed test results than Ethernet. Distance from the router, walls, neighboring networks, channel congestion, and a busy 2.4 GHz band can reduce throughput. A modern client may also connect with a lower link rate because of signal conditions or compatibility limits.

Router CPU or memory load

ASUS Merlin features such as traffic monitoring, bandwidth analysis, logging, parental controls, and connection tracking consume router resources. When CPU usage or memory pressure rises, the router may process packets less efficiently. This is more visible on fast fiber or cable broadband connections where routing demand is high.

VPN processing and encryption

An active VPN client can reduce download and upload performance because encrypted traffic must be processed by the router and then routed through a remote server. VPN distance, protocol selection, encryption overhead, and provider congestion can also increase latency. A test run through a VPN does not represent the direct ISP path.

Adaptive QoS and bandwidth management

Adaptive QoS, bandwidth limits, and traffic classification can intentionally reserve capacity for selected devices or applications. If the configured bandwidth values are lower than the real connection rate, the speed test may be shaped below the available ISP capacity. Heavy traffic from another device can produce a similar result.

Security inspection and acceleration settings

AiProtection, web history features, intrusion-related checks, and other inspection functions may add processing overhead. Some acceleration features can improve throughput, while certain combinations of monitoring, QoS, and security functions may limit hardware acceleration. The effect depends on router model, firmware version, and connection speed.

Modem, fiber terminal, or Ethernet negotiation

A damaged cable, an older Ethernet cable, or a port negotiating at 100 Mbps can cap a much faster broadband service. The modem or fiber terminal may also have signal, link, or provisioning problems. The router can appear to be the cause because the speed test runs through it, although the restriction is upstream.

Test server selection and network congestion

A distant or overloaded test server can show lower throughput and higher latency. Internet congestion between the ISP and that server may affect one result while other servers perform normally. This is why a result from one location should not be treated as a complete diagnosis of the broadband line.

How to Identify the Actual Limitation

1. Use a wired client: Connect a computer directly to a gigabit-capable LAN port with a known-good Ethernet cable. Confirm that the link speed is 1 Gbps or higher when the service requires it.
2. Pause local traffic: Stop cloud backups, streaming, game downloads, updates, and other high-bandwidth activity before testing.
3. Run several servers: Compare nearby and alternative test servers at different times. Record download, upload, and latency rather than relying on one reading.
4. Compare router paths: Test through the ASUS router, then test directly through the modem or fiber terminal only when the ISP setup supports that connection safely. Use the same client and test service.
5. Check router status: Review CPU, memory, WAN link rate, system logs, VPN status, QoS rules, and traffic monitoring during the test.
6. Test without optional processing: Temporarily disable VPN, QoS, bandwidth monitoring, and intensive inspection features one at a time. Re-enable them after identifying the setting that changes performance.

Optimizing ASUS Merlin for Accurate Speed Tests

Begin with the latest stable ASUS Merlin firmware that supports the router model. Reboot the modem or fiber terminal and router if the WAN link appears unstable, then verify that the router reports the expected WAN connection speed.

For baseline testing, use a wired client, select a nearby test server, and disable any active VPN. If QoS or bandwidth control is enabled, enter realistic measured upload and download values rather than the headline service rate. Incorrect limits can make the router deliberately report a lower result.

For Wi-Fi testing, use the 5 GHz or 6 GHz band when supported, stay near the router, and test with a recent client. Choose a clean channel, avoid unnecessary channel-width changes, and test each band separately. Wi-Fi results should be evaluated against the client link rate and local conditions, not only against the wired result.

When to Contact the ISP

Contact the ISP when a wired test remains consistently slow across multiple servers, the WAN link negotiates below the expected rate, or the direct modem or fiber terminal test shows the same limitation. Provide timestamps, test server names, wired results, and the router or modem status. This information helps distinguish a service-side issue from an ASUS Merlin configuration problem.

If wired performance is normal but Wi-Fi remains slow, the likely issue is local wireless coverage, client capability, interference, or access-point placement. If performance drops only when VPN, QoS, or monitoring features are enabled, adjust that feature or consider whether the router model has enough processing capacity for the required connection speed.

Practical Interpretation of the Results

A small variation between tests is normal because Internet paths and server workloads change. Consistently low results on every wired test point toward the WAN path, router processing, modem, or ISP. Normal wired speed with poor Wi-Fi points toward wireless conditions. Normal direct speed with poor ASUS Merlin results points toward router configuration, resource load, or firmware behavior.

Use speed tests as one part of the diagnosis. Latency under load, packet loss, link negotiation, router CPU usage, and results at different times can reveal problems that a single download number cannot. This approach produces a more reliable assessment of the connection and the router's actual performance.