Improve Internet Speed for End Users: Define Speed, Find the Bottleneck, Prioritize Fixes

How would you make the internet faster for the people who use it? Explain what "faster" should mean, where the delay comes from, what you would change first, and how you would know it worked. ```hint Take "slow" apart Before proposing fixes, break down the separate things that can make a page or video feel slow, and ask which of them dominates for the users you choose. ``` ### Clarifying Questions - Faster for whom: mobile users in emerging markets, households on home broadband, or businesses? - What position am I in: a company that runs network infrastructure, a content or cloud platform, or the maker of a browser or app? That decides which levers I can pull. - Does "faster" mean the connection speed people pay for, or how quickly the pages and apps they use actually respond? ### What a Strong Answer Covers - A precise definition of "faster" that separates bandwidth, latency and perceived load time - A chosen user segment and the bottleneck that dominates for it, with reasoning - Changes across layers, from access networks and content placement to protocols and page weight, prioritized by impact and by what the chosen role controls - Metrics that reflect what real users experience, with guardrails - Trade-offs such as cost, data usage, privacy and dependence on partners ### Follow-up Questions - If your only lever were the software running on users' phones, what would you build? - A protocol upgrade cuts load times in lab tests, but your real-user metrics do not move. How do you investigate? - How would you choose between funding new infrastructure in one country and a software change that helps every country a little?