How the Web Works for Frontend Developers
How the web works describes what happens between typing a URL and seeing a page: the browser resolves a domain through DNS, opens a connection to a server, sends an HTTP request and renders the response. It is the base layer of frontend work, alongside the terminal, DevTools and Git.
Stage: Web Foundations · Part of the Frontend Developer roadmap · Last reviewed 19 November 2026
What to learn in How the Web Works
- Trace an HTTP request from URL entry to rendered page, naming each step
- Read the Network tab in DevTools to find slow or failed requests
- Navigate folders and run commands in a terminal without a mouse
- Create a Git repository, commit changes and push to GitHub
- Tell apart status codes such as 200, 301, 404 and 500
How the Web Works interview questions
What happens when you type a URL into the browser and press Enter?
The browser checks its caches, resolves the domain to an IP address through DNS, opens a TCP connection and usually a TLS session, sends an HTTP request, receives HTML, then parses it, fetches linked CSS, JS and images, and renders the page.
What is the difference between a GET and a POST request?
GET asks the server to return a resource and should not change anything, so it can be cached and bookmarked. POST sends data in the body, such as a form submission, and usually creates or changes something on the server, so browsers do not cache it by default.
Where How the Web Works fits in the Frontend Developer roadmap
How the Web Works belongs to the Web Foundations stage (beginner level), which takes about 4 hours. How the web works, plus the HTML and CSS every interface is built on.
Other units in this stage
Back to the full Frontend Developer roadmap