Trivetek — Home network measurements | trivetek.com

Measure, then isolate

Trivetek — Home network measurements | trivetek.com

Trivetek is a new independent home-network guide for everyday users. It helps you convert units, record speed tests and separate Wi-Fi problems from ISP problems. It is not an internet provider or a repair service.

Readings, units and how to use them

This is an independent measurement reference, not an ISP, a speed-test operator or a diagnosis service for a specific line.

12.5MB/s at 100 Mbps before overhead

Six readings and what they answer

Scroll the strip sideways — 6 cards.

Units

Bits versus bytes

One byte contains 8 bits, so 100 Mbps is a theoretical 12.5 MB/s before overhead. A download manager showing 11 MB/s on that line is consistent with ordinary overhead.

Timing

Idle and loaded

Idle latency is measured on a quiet link; loaded latency is measured during a transfer. The gap between them is the queueing signal.

Variation

Jitter

Jitter describes variation in latency rather than the average latency itself, so report it beside the mean, not instead of it.

Loss

Percentage that matters

Packet loss is the share of sent packets that do not arrive. Sustained loss forces retransmissions and reduces effective throughput.

Method

Three connections

The FCC fixed-broadband methodology uses three concurrent TCP connections for download and upload throughput measurements.

Scope

What a test cannot say

A single run cannot separate device, Wi-Fi, router and ISP effects. Only repeated comparisons with one changed variable can.

Six steps from units to isolation

Contents

1000milliseconds in one secondLatency is reported in ms, so 20 ms is 0.02 s of round-trip time.
3concurrent TCP connections in the FCC fixed-broadband methodThroughput is measured over three parallel streams, not a single stream.
~2,000packets per hour in the FCC idle-latency testIdle latency is sampled with a light packet stream rather than a bulk transfer.

Convert Mbps to MB/s before you compare anything

Divide megabits per second by 8 to get megabytes per second, then subtract overhead separately.

Network speed is measured in megabits per second (Mbps), while file sizes and disk transfers are usually shown in megabytes (MB). One byte contains 8 bits, so 100 Mbps corresponds to a theoretical 12.5 MB/s before protocol and retransmission overhead. A browser download that shows 11 MB/s on a 100 Mbps line is consistent with ordinary overhead, not proof of a fault by itself.

To estimate an ideal transfer time, multiply the file size in megabytes by 8, divide by the speed in Mbps, and treat the result as a floor. An ideal 250 MB transfer at 100 Mbps takes 20 seconds by 250 × 8 ÷ 100, before overhead. Real transfers add TCP headers, acknowledgements and retransmissions, so the observed time is longer.

Keep the two conversions separate in your notes: unit conversion explains the gap between the advertised number and the file manager, while overhead explains the gap between the ideal time and the clock. Mixing them produces a false diagnosis of a slow line.

  • Mbps ÷ 8 = MB/s (theoretical, no overhead)
  • MB × 8 ÷ Mbps = ideal seconds
  • Overhead is a separate subtraction, never folded into the unit conversion

Readings, units and how to use them

Readings, units and how to use them
ReadingUnitWhat it answersHow to use the reading
Download throughputMbpsHow fast data arrivesBaseline and repeat runs
Upload throughputMbpsHow fast data leavesBaseline and repeat runs
Idle latencymsRound-trip delay on a quiet linkQuiet-link baseline
Loaded latencymsDelay while a transfer runsChange during a transfer
JittermsHow much latency variesSpread beside the mean
Packet loss%Share of packets that never arrivePercentage over the same run
Ideal 250 MB transfer at 100 MbpssFloor before overhead20 s before overhead
Theoretical rate at 100 MbpsMB/sBit/byte conversion12.5 MB/s before overhead
FCC throughput methodTCP connectionsPublished measurement method3 concurrent connections
FCC idle-latency samplingpackets/hourPublished measurement method~2,000 packets/hour
Readings, units and how to use them

Reading the measurements

Each panel pairs a unit with the question it answers, so the six readings stay distinct.

MbpsLatencyJitterPacket loss
The key terms of this guide, drawn to one scale

Questions visitors actually ask

Why does my download show 11 MB/s when I pay for 100 Mbps?
Because the units differ: 100 Mbps ÷ 8 = 12.5 MB/s theoretical, and overhead brings the observed rate below that. The gap is unit conversion plus protocol overhead, not a shortfall in the line.
Is high latency worse than high jitter?
They hurt differently. High but steady latency is tolerable for many applications; high jitter breaks real-time audio and video even when the average looks acceptable.
How much packet loss is a problem?
Any sustained loss deserves a repeat test. Compare idle and loaded runs on wired and Wi-Fi paths before assigning a cause. Short bursts may appear only during loaded runs.
Can one speed test tell me whether my ISP is at fault?
No. You need a wired baseline repeated across days and times, plus Wi-Fi and loaded comparisons, before an ISP cause is supported. A single run mixes device, Wi-Fi, router and ISP effects.