Activity 01
Speed Test Challenge: Measure and Compare
Students use online tools like Speedtest.net to measure bandwidth and throughput on school WiFi and mobile data. They record results in a shared spreadsheet, noting times of day for variations. Groups then graph data to identify patterns in performance.
Differentiate between bandwidth and throughput in the context of network performance.
Facilitation TipDuring the Speed Test Challenge, circulate with a timer to ensure all students complete tests within the same five-minute window so results are comparable.
What to look forPresent students with two scenarios: Scenario A describes a user experiencing slow video buffering with a stated bandwidth of 50 Mbps, and Scenario B describes a user experiencing delayed responses in an online game with a stated bandwidth of 100 Mbps. Ask students to identify which scenario is more likely affected by high latency and which by low throughput, and to justify their answers.
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson→· · ·
Activity 02
Bottleneck Simulation: Shared Resource Model
Divide class into 'devices' sharing a single 'router' (teacher-controlled projector). Simulate uploads by passing notes; introduce delays for latency. Students calculate theoretical vs actual throughput and discuss limiting factors.
Analyze how various factors can limit the effective throughput of a network connection.
Facilitation TipIn the Bottleneck Simulation, assign each group a unique combination of upload and download limits to create varied data points for the whole-class analysis.
What to look forOn an index card, ask students to define bandwidth and throughput in their own words. Then, have them list two real-world factors that can cause throughput to be lower than bandwidth.
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson→· · ·
Activity 03
Scenario Prediction: App Impact Cards
Provide cards describing apps (e.g., Zoom, file download) with bandwidth/latency values. Pairs predict user experience, justify choices, then test predictions with quick simulations or videos. Debrief as a class.
Predict the user experience impact of low bandwidth versus high latency for different applications.
Facilitation TipFor the Scenario Prediction cards, print each scenario on colored paper so students can physically sort them into categories during the activity.
What to look forFacilitate a class discussion using the prompt: 'Imagine you are troubleshooting a slow internet connection for a family member. What steps would you take to determine if the problem is primarily due to low bandwidth, high latency, or packet loss, and how would your suggested solutions differ for each?'
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson→· · ·
Activity 04
Packet Relay Race: Throughput Demo
Students form lines as network paths; front passes 'data packets' (balls) back. Add obstacles for loss or delays. Time relays to compare bandwidth potential against achieved throughput, recording metrics.
Differentiate between bandwidth and throughput in the context of network performance.
Facilitation TipDuring the Packet Relay Race, use a stopwatch visible on the projector so students can track their progress and connect timing to throughput.
What to look forPresent students with two scenarios: Scenario A describes a user experiencing slow video buffering with a stated bandwidth of 50 Mbps, and Scenario B describes a user experiencing delayed responses in an online game with a stated bandwidth of 100 Mbps. Ask students to identify which scenario is more likely affected by high latency and which by low throughput, and to justify their answers.
AnalyzeEvaluateCreateSelf-ManagementSelf-Awareness
Generate Complete Lesson→A few notes on teaching this unit
Teach this topic by starting with real-world frustrations students feel with slow downloads or laggy calls. Use their experiences as a bridge to introduce terms, then immediately test their hypotheses with data. Avoid overloading them with technical details upfront; instead, let problems guide the learning. Research shows that students retain these concepts better when they first observe the gap between expectation and reality, then investigate causes through structured simulations.
Students will confidently distinguish bandwidth from throughput, explain why measured speeds rarely match advertised rates, and predict how network conditions affect different applications. They will use evidence from their own tests and simulations to support their reasoning in discussions and written responses.
Watch Out for These Misconceptions
During Speed Test Challenge, watch for students who assume their measured download speed equals their actual bandwidth.
After students record their speeds, have them compare their results to the plan’s advertised bandwidth. Ask them to calculate the difference and brainstorm in pairs why the measured speed is lower, then share ideas with the class.
During Bottleneck Simulation, watch for students who believe increasing bandwidth alone will always improve performance for all applications.
After the simulation, ask each group to present how their bottleneck affected different tasks (e.g., video calls versus file downloads). Guide the class to identify that latency-sensitive apps suffer more under congestion.
During Scenario Prediction cards, watch for students who attribute slow performance solely to the user’s device specifications.
After sorting scenarios, ask students to add a second card for each scenario explaining whether the issue is device-based, network-based, or app-based, using evidence from their simulations.
Methods used in this brief