Skip to content
Module
Module 3 of 6Lesson 2 of 2~13 min

From received code to displayed page

How fast a product feels depends largely on what the browser does once the code arrives. This lesson helps you understand how HTML, CSS and JavaScript become a page, tell client-side, server-side and static rendering apart, and connect these technical choices to the Core Web Vitals that matter to your users.

Take this lesson: your first course is freeSee the full syllabus

Lesson objective

By the end of this lesson, you will be able to explain how the browser turns HTML, CSS and JavaScript into a displayed page, tell apart client-side, server-side and static rendering, and relate these choices to the Core Web Vitals.

Topics covered

  • browser rendering
  • server-side rendering
  • Core Web Vitals
  • HTML CSS JavaScript
  • web performance

Where it fits

What the browser and the server say to each other

What does an HTTP exchange contain, and how does the browser turn the response into a page?

Lessons in this module

  1. Reading a request and its response in the Network tab
  2. From received code to displayed page (this lesson)

What you will learn in this module

This lesson is part of the course Explain how a web product works, from browser to server

  • Describe the steps of a web request, from the typed address to the displayed page (URL, DNS resolution, encrypted connection, HTTP request and response, browser rendering).
  • Read an HTTP exchange in the browser's Network tab (method, URL, status code, headers, cookies, duration) and draw a first diagnosis from it.
  • Explain how responsibilities are split between browser, frontend, backend, API, database and third-party services, and place where a business rule must run.

Related courses