Slow office Wi-Fi: collect evidence before buying new equipment

Before buying new Wi-Fi equipment, identify who is affected, where the problem occurs and which activity is slow. A useful symptom record helps distinguish a local device issue from a wider network or internet problem.

Describe the symptom precisely

“The internet is slow” can mean a weak wireless connection, one unavailable website, delayed file access or a video call that breaks up. Record what the person is doing and what they observe. Include when it began and whether anything recently changed.

Compare ordinary observations across a few authorised devices and locations. Do not run disruptive tests, change router settings or install unknown utilities simply to produce a number. Start with evidence the team can gather safely.

Use a location and scope record

Observation	What it helps clarify
One device or several	Whether the issue may be device-specific or shared.
One room or many	Whether location or coverage may be relevant.
One application or all activity	Whether the affected service is narrower than the network.
Specific times	Whether load or an external pattern may matter.
Recent change	New equipment, configuration or provider work to investigate.
Wired comparison, if available and authorised	Whether a supported non-wireless route shows a different symptom.

Keep connectivity and capacity separate

A device can show a strong connection while the required service remains slow. Conversely, a problem in one location can occur even when the internet service itself is working. The support team needs enough context to investigate the relevant path.

A speed result is a sample under particular conditions, not a complete diagnosis. Record the device, location, time and test method if a test is part of the agreed assessment. Avoid treating a single result as proof that a supplier or access point is at fault.

Do not weaken security to make a test pass

Turning off a firewall, sharing an administrator password or moving business devices onto an uncontrolled guest network can create new problems. Ask the authorised administrator to review the required communication and supported configuration.

Also identify power or physical-link symptoms. An access point restarting or a damaged cable needs a different investigation from ordinary radio congestion. Keep visible observations in the support request without opening equipment or changing undocumented connections.

Send a concise evidence pack

• Affected users or devices and locations.
• The activity that is slow or failing.
• Start time, frequency and recent changes.
• Any comparison already made safely.
• Business impact and an available contact.

With this information, an assessment can decide whether to inspect configuration, cabling, coverage, equipment capacity or the provider path. A replacement recommendation should follow that evidence rather than precede it.