As of 13 August 2026, AI can check whether your business broadband speed is good enough.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Do it yourself

   Second choice

   A chat interface, chat-fluent skill, and roughly 15 minutes until you can act on the result.

   How to actually do it

   1. Open a reputable broadband speed-test page on a computer connected by Ethernet where possible, and record the download speed, upload speed, latency, packet loss if shown, date and time.
   2. Run the same test on the affected Wi-Fi device and record whether the result changes, then note which business activities were slow or interrupted.
   3. Open your broadband provider's package details and copy the advertised speeds, any minimum or guaranteed service information, connection type and package name.
   4. Gather the number of people using the connection, the main cloud, voice, video and file-transfer applications, and the times when problems occur.
   5. Paste the gathered information into the prompt and ask the chatbot to assess whether the connection is good enough without inventing thresholds or causes.
   6. Compare the assessment with the original test results and provider information, then repeat a wired test during an affected period before deciding whether to troubleshoot your network or contact the provider.

   Prompt

   Assess whether my business broadband is good enough for the work we do. Do not invent thresholds, test results, provider promises or causes. Separate measured facts from assumptions and say when the evidence is insufficient.
   
   Business context:
   - Number of people using the connection: [number]
   - Main activities, such as video calls, cloud applications, file transfers, voice calls or hosted systems: [activities]
   - Times when the connection feels slow or unreliable: [times]
   - Connection type, such as fibre, full fibre, cable or mobile: [type]
   - Provider and package name: [provider and package]
   - Advertised download and upload speeds: [speeds, if known]
   - Any service guarantee or stated minimum: [details, if known]
   - Whether the issue affects wired devices, Wi-Fi devices or both: [details]
   
   Test results:
   Paste each result with its date and time, whether the device was wired or on Wi-Fi, the measured download speed, upload speed, latency and packet loss if shown: [results]
   
   Give me:
   1. A plain-English conclusion: likely good enough, possibly insufficient, or evidence is insufficient.
   2. The evidence supporting that conclusion.
   3. Any signs that the problem may be Wi-Fi, a device, the local network, the broadband line or the provider.
   4. The missing tests or information needed to distinguish those causes.
   5. Practical next steps in order, including what to test on a wired connection and what evidence to send the provider.
   6. A short list of questions I should ask the provider.
   Do not recommend changing provider or package unless the supplied evidence supports it. Do not treat a single speed test as proof of a persistent fault.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.

3. Hand it to a person

   The distant third

   A person who owns the outcome does this end to end, worth it when the failure is dear.