From URL to page
Answer out loud or in your head first, then compare.
Answer
The browser parses the address and checks the available caches. DNS may resolve the server's address. A connection is set up — for HTTPS, secured with TLS as well — and then the HTTP request is sent.
The server returns a response. The browser parses the HTML, discovers CSS, JS and images, builds the DOM and styles, computes the layout, paints and composites the view.
To be precise: resources can be fetched in parallel. A cache, an existing connection or a service worker can change the flow. HTTP/3 uses QUIC, so I don't describe every connection as TCP.
Pitfall: JavaScript and CSS can delay rendering; a server response doesn't yet mean an interactive screen.
How did it go? Be honest — “Not yet” puts the question on your review list.