It can be divided into three stages:
■ [stage] HTTP request: browser parses URL → → and DNS resolution requests the corresponding IP address of the DNS server sends a domain name to establish a TCP / IP connection → send HTTP request packet Request page
The stage mainly on knowledge: DNS name resolution? ? ? Three times or four times TCP handshake waving, HTTP Services, HTTP packets, 304 status code? ? ? , Cookie with the session https://www.cnblogs.com/qqinhappyhappy/p/11845551.html
■ HTTP response phase []: → → response packet client receives a page response from the server (actually a code file, instead we see the page)
■ browser rendering stage []: → browser memory in a stack memory allocation to begin executing code → encounter static resources such as images of JS CSS will create a new thread when referring to load these resources, the main thread continues to execute code → from the top down parsed the HTML DOM tree generated after resources → CSS code is loaded and the like after completion of the DOM tree and generating CSSOM → CSSOM combined to generate the render tree → drawn on the page
See browser rendering process https://www.cnblogs.com/qqinhappyhappy/p/11872670.html
