A structured lesson workspace with readable content, hands-on examples, and a clean path to completion.
Implementation note: Optimize the document by reducing unnecessary work, not by adding hints indiscriminately. Keep the browser behavior observable while you work.
Source-reading note: the exact semantics here come from the HTML element/attribute you chose, not its CSS appearance.
“Treat the markup here as a contract with the browser. The more precisely you express the contract, the less repair work the browser has to invent. In this lesson, the focus is resource hints, lazy loading, dimensions, and source order. That matters because HTML is interpreted by a parser and then exposed to browser features such as navigation, accessibility tooling, form controls, media handling, and script APIs. A correct-looking screenshot can still hide a poor document model.”
Start with the smallest meaningful example. The working snippet demonstrates the core syntax, but the important part is what each piece contributes: the element supplies semantics or behavior, attributes refine that meaning, and surrounding structure gives the browser context. Don't add markup just because a framework or copied example happens to include it.
| Decision | Why it matters |
|---|---|
| Native element | Carries browser semantics and default behavior. |
| Attribute | Refines the element without replacing its meaning. |
| CSS/JS hook | Adds presentation or behavior around the existing structure. |
<img src="thumb.jpg" alt="..." width="400" height="300" loading="lazy">
Now put the same idea under pressure. A realistic failure is: Optimize the document by reducing unnecessary work, not by adding hints indiscriminately. The browser may recover, ignore an invalid combination, or leave the user with a control that appears visually fine but behaves differently than expected. That is why source inspection and keyboard testing belong in the workflow.
<header><h1>Acme Studio</h1><nav><a href="/">Home</a><a href="/work">Work</a></nav></header><main>...</main>
The browser's defaults are part of the behavior you are learning. Prefer native semantics first, then test the exact combination of attributes and content you plan to ship.
You can now explain the browser behavior behind resource hints, lazy loading, dimensions, and source order, build the markup deliberately, and diagnose the most common failure mode instead of guessing.
Engineering judgment: prefer the native HTML behavior described here before reaching for a custom widget.
Finish the lesson once you have worked through the material. This awards ★ 20 XP.