A page is more than one request
Your objectiveExplain why a successful document response can coexist with a broken page.
Understand the idea.
HTTP is an exchange of requests and responses. A page may start with an HTML document, then request a stylesheet, scripts and images. Each resource can have a different outcome. A 200 status on the document is evidence about that response, not an automatic verdict on the whole experience.
A worked example.
The document arrives, but the stylesheet returns 404. The reader can see text, but the intended layout is missing. The application may still be reachable even though a resource path is wrong. If a script fails, a control may appear without doing anything.
Try the reasoning.
Open the Network panel in your browser, reload this lesson and identify the document, style.css and site.js. Match each resource to the part of the experience it supports. This observation is read-only.
DNS supplies records associated with the name. A successful answer does not establish application health.
Conceptual illustration. Selecting a step does not send a network request.Carry it into practice.
When reporting a broken page, include the failed resource URL and its status, rather than reporting only that the homepage loaded.
Read the reference: MDN: HTTP overview ↗