WEB101 · How the Web Works
About Course
Understand what really happens between typing an address and seeing a page: networks, DNS, HTTP, browsers and servers. You will inspect real traffic with free browser tools and explain it in plain language.
Who it is for
Beginners, career changers and small-business owners who want a solid mental model of the web before writing code.
Prerequisites
No prior programming is required; you only need a modern browser and basic computer skills.
What you will be able to do
- Explain the path of a web request from browser to server and back, naming DNS, TCP, TLS and HTTP.
- Identify the parts of a URL and the purpose of common HTTP methods and status codes.
- Use browser developer tools to inspect requests, responses, headers and load timing.
- Describe the roles of front end, back end, databases and hosting in a small-business website.
Lessons
- Lesson 1 · From address bar to server
- Lesson 2 · HTTP, HTTPS and the conversation between browser and server
- Lesson 3 · Browsers, hosting and the parts of a web application
- Lesson 4 · Lab and assignment
Lab: Trace a page load with DevTools
You will load three real websites with the Network panel open, record the requests, status codes and timings, and look up their DNS records. You will then compare a fast and a slow page and explain the difference in plain language.
Free tools: Chrome or Firefox Developer Tools (Network panel), a public DNS lookup in the browser, and a free text editor
Assessed assignment
Write a two-page explainer titled "What happens when a customer opens our website" for a small business of your choice (for example a bakery or a dental clinic). Include a diagram or numbered sequence of the request path, a table of five requests you captured with method, status code, size and time, and three concrete suggestions to make the page load faster. Write for a non-technical owner and define every technical term you use.
| Criterion | Weight | What excellent work looks like |
|---|---|---|
| Accuracy of the request path | 30% | DNS, connection, TLS, HTTP request and response, and rendering appear in the correct order with correct roles. |
| Evidence from DevTools | 25% | The table uses real captured data, and each value is read and interpreted correctly. |
| Performance suggestions | 25% | Three suggestions are specific, tied to the captured evidence and realistic for a small business. |
| Clarity for a non-technical reader | 20% | Terms are defined, the structure is easy to follow and there is no unexplained jargon. |
Portfolio piece
A plain-language web request explainer with real DevTools evidence that you can show to clients or employers.
Next step
Continue with WEB102 · HTML and CSS Foundations · 4 hours · $28.00
Course Content
WEB101 · How the Web Works (4 h)
-
Lesson 1 · From address bar to server
-
Lesson 2 · HTTP, HTTPS and the conversation between browser and server
-
Lesson 3 · Browsers, hosting and the parts of a web application
-
Lesson 4 · Lab and assignment
-
WEB101 Assessment · How the Web Works