A web server receives requests for a website and returns responses. The term can mean the server software or the computer running it. A single website visit may also involve DNS, a TLS connection, application code, a database and a CDN.
Follow one page request
- Find the destination: DNS helps the client discover where to connect for the hostname.
- Establish the connection: for HTTPS, the client checks the certificate and negotiates an encrypted connection.
- Send the request: the browser asks for a particular path, such as an article.
- Produce the response: the web server may return a file or pass work to an application, which may query a database.
- Render the page: the browser reads the response and may request additional images, scripts and styles.
MDN’s web-server overview explains the distinction between hardware, HTTP software and static or dynamic content.
Static and dynamic content
A logo file can often be served directly. A WordPress article is normally assembled using application code and stored content, unless a cache supplies a reusable response. The web-server process and the application runtime may be separate services.
This distinction helps with troubleshooting. If a logo loads but every dynamic page fails, investigate the application path rather than assuming the entire machine is offline.
What response codes tell you
- A successful response means the request was handled, but the page still needs a content and behavior check.
- A redirect points the client to another address. An unexpected destination needs investigation.
- A missing-page response can indicate an incorrect link or a removed page.
- A server error indicates a failure along the request’s processing path; its exact cause requires more evidence.
Identify the failing layer
Record the exact URL, time and symptom. Check whether the issue affects every page, only one function or only one network. A DNS error, certificate warning and application error require different fixes.
Use our hosting troubleshooting checklist before changing production configuration. A clear description of which request fails is more useful than a general report that “the server is slow.”