Web Page Rendering

Below are the step-by-step descriptions of how page get displayed in your browser when you simply enter some URL in address bar:

1. You type an URL into address bar in your preferred browser.
2. The browser Parser the URL to find the Protocol, host, port and path.
3. Its forms a HTTP request.
4. To reach the host, it first needs to translate the human readable host into an IP number and it does this by doing a DNS lookup on the host.
5. Then a Socket needs to be opened from the user’s computer to that IP number on the port specified (most often port 80).
6. When a connection is open, the HTTP request is sent to the host.
7. The host forwards the request to the Server software (most often Apache) configured to listen on the specified port.
8. The server inspects the request (most often only the path) and launches the Server plug-in needed to handle the request (corresponding to the server language you use PHP, Java, .Net, Python).
9.  The plug-in gets access to the full request and starts to prepare a HTTP response.
10.  To construct the response database is (most likely) accessed. A database search is made, based on Parameters in the path (or data) of the request.
11.  Data from the database, together with other information the plug-in decides to add, is combined into a long string of text (probably HTML).
12. The Plug-in combines that data with some Meta data (in the form of HTTP headers) and sends the HTTP response back to the browser.
13.  The browser receives the response and Parse the HTML (which with 95% probability is broken) in the response.
14.  A DOM tree is built out of the broken HTML.
15.  New requests are made to the server for each new resource that is found in the HTML source (typically images, style sheets and Java files). Go back to step 3 and repeat for each resource.
16.  Style sheets are parsed and the rendering information in each gets attached to the matching node in the Dom tree.
17. Java Script is parsed and executed and DOM nodes are moved and style information is updated accordingly.
18.  The browser renders the page on the screen according to the Dom tree and the style information for each node.
19. You see the page on the screen.

And we get annoyed why the response time is very high but now at least I have some documentation to look at, while waiting the remaining fractions of a second before the page renders.