Static page

Notes on reading the web

This host publishes one reading page. It explains how an ordinary HTML document is structured, why a page stays lighter when it does not fetch remote files, and how a link stays usable. It does not ask for a name, a password, or a message.

What a document contains

A browser reads HTML as a tree of elements. A title in the head names the page. One top heading states the subject. Sections group the paragraphs that belong together. A link is an address plus words that say where it goes.

The HTML Living Standard, maintained by the Web Hypertext Application Technology Working Group, is the document that defines those elements and how a browser parses them. The MDN HTML and CSS references explain the same ideas in shorter articles aimed at people building pages. HTTP, described for the web by MDN and for the protocol by RFC 9110, is how the browser asks for the document and how the server answers.

Keeping a page light

A page is heavier when it waits on extra files: a font from another site, a script, a large image, or a tracker. Each extra request is another chance for the first words to arrive late. A static page can avoid that by using the type already on the device and by putting the style in the document itself.

This page does that. It has no remote font, no analytics script, and no image except the small icon declared for the bookmark. That is a choice about this document, not a measurement of a score and not a promise about any other request this host may answer.

MDN’s performance guide is the place to read how browsers spend time on the network and on rendering, and which numbers are worth collecting when you measure your own page. This document does not publish a timing figure.

Making the page usable

A usable page can be read without a picture of the layout. The heading order matches the outline. Links say what they open. Text stays readable against its background. Keyboard focus is visible, and a skip link jumps past the repeated navigation. Motion is not required: if the reader prefers less motion, this page does not animate the scroll.

The W3C Web Content Accessibility Guidelines 2.2 is the recommendation that states those requirements. The WAI introduction is a shorter starting point from the same organization. MDN’s accessibility guide shows how those ideas land in HTML, including names for controls and focus.

References

Each link opens the document named here. The words under the address say what that document is for.