What happens after I type a URL and press Enter?

It feels instant.
But behind the scenes, your browser performs many steps before you see a webpage.

Understanding this flow makes HTML, CSS, and JavaScript much easier to grasp.

What a Browser Actually Is (Beyond “It Opens Websites”)

A browser is not just something that “opens websites.”

It is a complex software system that:

• Fetches files from servers

• Understands HTML and CSS

• Runs JavaScript

• Calculates layouts

• Draws pixels on your screen

In simple terms:

👉 A browser converts code into something humans can see and interact with.

Main Parts of a Browser (High-Level Overview)

Think of a browser as a team of departments working together.

Main components:

• User Interface

• Browser Engine

• Rendering Engine

• Networking

• JavaScript Engine

Each part has a specific job.

You don’t need to memorize them — just understand the flow.

User Interface: Address Bar, Tabs, Buttons

This is the part you interact with:

• Address bar

• Back/forward buttons

• Tabs

• Refresh button

It’s like the dashboard of a car.

You control the browser from here, but the real work happens underneath.

Browser Engine vs Rendering Engine (Simple Distinction)

These two often confuse beginners.

Let’s simplify:

Browser Engine

Acts as the manager.
It connects the UI with the rendering engine.

Rendering Engine

This is the artist.
It reads HTML and CSS and turns them into visible content.

Examples (just names, no deep dive):

• Chromium (used by Chrome)

• Gecko (used by Firefox)

You don’t need to know their internals — just their roles.

Networking: How a Browser Fetches HTML, CSS, JS

When you press Enter:

1. Browser asks DNS for the IP address.

2. It creates a connection (usually using TCP).

3. It sends an HTTP request.

4. The server responds with files like:

   • HTML

   • CSS

   • JavaScript

   • Images

This is called fetching resources.

The browser doesn’t just download one file — it may fetch many.

HTML Parsing and DOM Creation

Once the browser receives HTML, it doesn’t display it immediately.

It first parses it.

Parsing means:
Breaking text into structured meaning.

Example:

<h1>Hello</h1>

The browser understands:

• This is a heading

• It contains the text “Hello”

It then builds something called the DOM (Document Object Model).

Think of the DOM as a tree structure.

Example structure:

html
 └── body
      └── h1
           └── "Hello"

The DOM represents the structure of your webpage.

CSS Parsing and CSSOM Creation

Next, the browser processes CSS.

It parses CSS rules like:

h1 {
  color: red;
}

And creates something called the CSSOM (CSS Object Model).

If the DOM is the structure of the house,
the CSSOM is the styling instructions.

It answers:

• What color?

• What size?

• What spacing?

How DOM and CSSOM Come Together

The browser combines:

• DOM (structure)

• CSSOM (styles)

Together they form the Render Tree.

The Render Tree contains:

• Only visible elements

• Their styles

This is what the browser actually uses to draw the page.

Layout (Reflow), Painting, and Display

Now the browser knows:

• What elements exist

• What they look like

Next steps:

1️⃣ Layout (Reflow)

The browser calculates:

• Where each element should appear

• How much space it takes

Example:

• This div is 300px wide

• That text is below it

2️⃣ Painting

The browser fills in:

• Colors

• Borders

• Text

• Shadows

It turns structure into visual pixels.

3️⃣ Display

Finally, pixels are shown on your screen.

That’s when you see the webpage.

Very Basic Idea of Parsing (Simple Math Example)

Parsing isn’t just for HTML.

Take a math expression:

2 + 3 × 5

Your brain doesn’t just read numbers randomly.

It understands structure:

• Multiply first

• Then add

The browser does something similar with HTML and CSS.

It converts text into a structured tree so it knows what everything means.

Full Flow: From URL to Pixels

Here’s the complete journey:

1. You type a URL

2. DNS finds the IP

3. Browser sends HTTP request

4. Server sends HTML

5. Browser parses HTML → DOM

6. Browser parses CSS → CSSOM

7. DOM + CSSOM → Render Tree

8. Layout calculation

9. Paint

10. Pixels appear on screen

All of this happens in milliseconds.

Final Thoughts

A browser is not magic.

It is a system of components working together:

• Networking fetches files

• Parsing builds structure

• DOM represents content

• CSSOM represents styles

• Layout calculates positions

• Painting draws pixels

• You don’t need to memorize everything at once.

  Just remember the flow:

  👉 URL → HTML → DOM → CSSOM → Render Tree → Layout → Paint → Screen