The browser

Its job in the system

The browser is an application at the edge of the network. A web address identifies a resource and how to request it. The browser combines networking with document processing, security checks, and rendering. The internet transports the information, while the browser gives that information its visible and interactive form.

How it works

After navigating to a page, the browser may need to resolve a host name, establish a connection, and request the main document. Previously cached information or an existing connection can shorten this sequence. The initial document can refer to other resources such as style sheets, images, and scripts, producing further requests that may overlap in time.

The browser interprets the document structure and styles, calculates layout, and paints pixels. Scripts can change the page or request more information. This means a slow experience is not always a slow network: the device can spend time processing downloaded material. Equally, a page can become partly visible before every resource has arrived.

What it connects to

The browser relies on the device’s network stack and access connection. DNS supplies naming information, transport protocols carry data between endpoints, TLS protects a connection, and HTTP defines the request and response exchange. These are cooperating layers and services, not boxes every packet visits in one fixed sequence.

Different places, different designs

Browsers and websites differ in how they load resources. A static article, a video player, and an application that continually updates data put different demands on the network and device. A browser cache may avoid a download, while a site may contact several service providers during a single visit.